Software Development Life Cycle and the Design Thinking Process

Software Development Life Cycle and the Design Thinking Process:

• System Analysis, Requirements 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
• The steps are:
1. Gathering facts
1. 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
1. 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
1. Solutions to the shortcomings in step two are found and any specific user proposals are used to prepare the specifications
• Systems Designs
• Describes desired features and operations in detail, including screen layouts, rules, guidelines, process (data flow and entity relation) diagrams, pseudocode, and any other documentation
• Development
• The real code is written here.
• Integration and Testing
• Brings all the modules (pies) 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 feedback.

Below, there is a picture of the Design Thinking Process, which a lot of designers use to fabricate their product.

1. Empathize
1. 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.
2. Define:
1. 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
3. Ideate:
1. 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
4. Prototype:
1. 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
5. Test:
1. Try out high-resolution products and use observation and feedback to refine prototypes, learn more about the user, and refine your original point of view