Namecard - Mission Reflection

Recap-ing the Process:

1. Empathize

• In this step we figured out someone had a problem and needed a product made. We discovered their criteria and started to think about a product we could make.
• Why this is important: For this step, we needed to find out what we needed to make. This step is arguably one of the most important for this is when we figure out what we need to do.

2. Define

• In this step we defined the problems, theme, and dug deeper for what the user really wanted.
• Why this is important: In this step we problem solve and brainstorm so that when we get into ideate, we know the problems that we will face, and how we can avoid them.

3. Ideate 

• In ideate we made a rough sketch of the product we were going to make. Then with this product we took feedback from the user and other potential users.
• Why this is important: The feedback is very important for it narrows down what we need to know about the user and how that correlates to the product.

4. Prototype/Test

• This step we simply made the prototype. Then we took some feedback from the user, but not too much.
• Why this is important: Finally this is the prototype. It is why we did all the other steps. The feedback we receive is meager and tests out our product. 

How I will improve my product if put to the task again:

Firstly I maybe try to add some background color. Then I will probably color in the wings/darken them.

Namecard - Prototype/Test

Here is my prototype/test

and the back

Feedback:

• Make more color
• make something more than just the soccer ball

so I added wings :)

Software Development Life Cycle

Software Development Life Cycle

• Systems analysis requirement gathering: Defines project goals into defined functions and operation with the objective in mind, It is the process of gathering user requirements diagnosing problems and recommending improvements to the future system. 

                      A series of steps followed by the Analyst are:

1.  Gathering Facts: End user requirements are obtained through documentation, client interviews, observation, and questionnaires - asking what the user is currently doing and if there are any specific improvements they want or prefer.

2.  Scrutiny of the existing system: Identify pros and cons of the current system in-place, so as to carry forward the pros and avoid the cons in the new system.

3. Analyzing the proposed system: Solutions to the shortcomings in step two are found and any specific user proposals are used to prepare the specifications. 

• Systems design:Describes desired features and operations in detail including screen layouts, rules, guidelines, process (data flow and entity relation) diagrams, pseudocode and other documentation. 
• Development: The real code is written here.
• Integration and testing: Brings all the modules (pieces) together into a special testing environment, then checks for errors, bugs and interoperability.
• Maintenance: During the maintenance stage of the SDLC, the system is assessed to ensure it does not become obsolete.. This is also where updates are made to the initial software. It involves continuous evaluation of the system in terms of its performance and completing the change requests based on the feedback.  

Namecard - Ideate

Problems I could run into: 

• Not Having enough space
• Not interesting enough
• The namecard isn't capturing the attention of the user
• Not keeping them hooked 

Digging Deeper

• Point out what Anish wants to learn about me
• make it creative and keeping the user hooked

Theme

• My favorite sports team 
• Manchester United

Feedback 

• More color
• Put a few more things

Rough Sketch

Namecard - Define

Namecard Define - 

Problems I could run into: 

• Not Having enough space
• Not interesting enough
• The namecard isn't capturing the attention of the user
• Not keeping them hooked 

Digging Deeper

• Point out what Anish wants to learn about me
• make it creative and keeping the user hooked

Theme

• My favorite sports team 
• Manchester United

Name Card - Empathize

Empathize Questions from Anish

What is your favorite Color?
a. blue

What is your favorite Sport?
a. Soccer

Where did you go this summer?
a. Europe

What is my favorite hobby?
a. Playing soccer or video games

Favorite type of laptop?
a. Mac

Favorite beverage?
a. Rootbeer

Favorite grocery store?
a. Whole foods

Favorite vacation spot?
a. Hawaii

Favorite font?
a. black ops one

Favorite video game?
a. Overwatch

Favorite value in a friend?
a. Friendship

Favorite sports team?
a. Manchester United

What I want to be when I grow up?
a. Businessman

Software Development Life Cycle - Design Thinking Process

SDLC

Analyze
Design
Code
Test
Maintenance

Design Thinking Process

Empathize - The beginning of Design Thinking, one must empathize with the users, and find a common problem. They must empathize with the user and find the requirements that the user wants.

Define - One must define the problem and continue to take in feedback to use when starting to Ideate. Also you should find what

Ideate - One must come up with ideas of what they want to prototype. After they have come up with these some rough sketches, they must confirm with the users, and take in feedback on what they should improve before starting their first prototype.

Prototype - Based upon the ideas and rough sketches from the ideate, one must come up with a product based on all the steps before.

Test - One must put their product under the most rigorous conditions, and knead out all of the problems one runs into in the prototype.

Design Thinking Steps