Theme: Guitar
Challenge: none
Thursday, January 28, 2016
Name Card – Empathize
I am making a name card for
Radhika.
My name card will have my information.
TV show
Sport
Food
Music
Color
Hobbies
Drink
Subject
Vacation
Flavor Ice Cream
Pizza topping
College
Season
Where were you born
Sports team
TV show
Sport
Color
Food
Music
Radhika.
My name card will have my information.
TV show
Sport
Food
Music
Color
Hobbies
Drink
Subject
Vacation
Flavor Ice Cream
Pizza topping
College
Season
Where were you born
Sports team
TV show
Sport
Color
Food
Music
SDLC and Design Thinking Process
Software Development Life Cycle
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 developer 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.
System 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.
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 developer 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.
System 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.
Empathize: Work to fully understand the experience of the user for whom you are designing. Do this through observation, interaction, and immersing yourself in their experiences.
Define: Process and synthesize the findings from your empathy work in order to form a user point of view that you will address with your design.
Ideate: Explore a wide variety of possible solutions through generating a large quantity of diverse possible solutions, allowing you to step beyond the obvious and explore a range of ideas.
Prototype: Transform your ideas into a physical form so that you can experience and interact with them and, in the process, learn and develop more empathy.
Test: Try out high-resolution products and use observations and feedback to refine prototypes, learn more about the user, and refine your original point of view.
Friday, January 22, 2016
Analysis – empathize on behalf of the user
Ways to empathize with the user and think on their behalf.
- Ask your friends and figure out what kind of product they would like the most
- Research other products similar to yours and make yours better
Thursday, January 21, 2016
Subscribe to:
Posts (Atom)