Skip to main content

Name Card - Mission Reflection

1) What and why did you do each step in design thinking process?
  • Each step of this process is necessary because they all build on top of each other. In Empathize, I asked the user for the requirements which I need to fulfill in my name card. I also had my partner tell me what were the most important parts so I remember to incorporate those (Digging Deeper). In Define, I established a common theme which was relevant to all of the digging deeper topics and I made a list of challenges that I might encounter. This is so I know what to do if any difficulties do come up. Ideate is when I created my first hard copy. I drew a simple sketch that had the digging deeper topics and I took feedback so that I can fix those problems for my final project. In this step I also started to brainstorm solutions. As I completed each step including my final prototype, I asked for more feedback so my name card would be completely to the users satisfaction.
2) What did you learn?
  •  I learned that each step of the design thinking process relies on previous steps. In addition, I got to know what my customer likes so in the future, I would have a better idea on what to do.
3) How did you contribute towards disruptive innovation for your name card project?
  • Instead of drawing on a simple piece of paper, I made my name card 3D by cutting out a music note and hanging what I like on their. I also used cotton balls to make clouds, because I enjoy cloudy weather. My project consists of many materials which makes it unique and apart from others.

Comments

Post a Comment

Popular posts from this blog

Software Approach, Top Down Design

One way of coding is to simply have a rough idea of what you want to do and then start typing away to produce one huge source file. This is a very bad idea. The resulting code is likely to have many issues with it that include: Poorly documented code, so very hard to maintain and update 'Spaghetti Code' - which means a tangled mess of jumps and loops all over the code, very hard for someone to understand. Even by the originial coder a few days later! Duplication of code, so wasting memory and running speed Very hard to develop by more than one person as there is only one file Very hard to debug - the file either works of it doesn't
Post a Comment
Read more

Fundamentals of Computer Architecture

Our computer always responds to electricity We choose binary number system (our power button) Of/On (2 states) 0: bit 1: bit Combination of 8 bits: byte  ex. Mega byte Byte: Unit of memory Every symbol on the keyboard: character  A; a to Z; z; all numbers...etc. Each character is represented by a combination of bits (1 byte) ex. 01000100 Based on code, alphabet shows up Compiler Translates the entire source code into binary Takes in code Points out errors When it is correct, it converts the source code into machine language/binary code/binary language/object code  Interpreter   Translates line by line Easier to find mistake in some situations (Has same features as compiler) Source Code (Java, C++) ---> Compiler/Interpreter ---> Object Code (binary: 01001111)  "My source code is not compiling/interpreting"  ______________________________________________________________ Systems programs that helps us to...
Post a Comment
Read more

Points to Consider for Presentation

Some points I would consider to keep my audience engaged during the Presentation. Concise slides  Bullet points Topics which concern a general audience Ask questions to the audience Sound interested and excited Start with simple ideas Introduce unique fun facts Appropriate font size for audience Add some humor Powerful images Articulate, project, and vary tone while speaking Add personal stories Audience will connect and believe in you Know information  Don't read off slides
Post a Comment
Read more