Introduction to Software Development Life Cycle: Phases & Models
- 1. ESDS Software Solution Pvt. Ltd. The Digital Transformation Catalyst https://www.esds.co.in
- 2. Section BreakSection Break https://www.esds.co.in To Introduction to Software Development Life Cycle: Phases & Models
- 3. SDLC stands for Software Development Life Cycle. It is a process that gives a complete idea about developing, designing, and maintaining a software project by ensuring that all the functionalities along with user requirements, objectives, and end goals are addressed. With SDLC, the software project’s quality and the overall software development process get enhanced. https://www.esds.co.in
- 4. Benefits of SDLC 1. Address the goals and problems to implement the project with the highest precision and accuracy 2. SDLC does not allow the project members to proceed ahead before completion & approval of the prior stages 3. Installation in the project executed with SDLC has necessary checks to be tested with precision before entering the installation stage 4. With a well-defined SDLC in place, project members can continue the software development process without incurring any complications 5. SDLC offers optimal control with minimum problems, allowing the project members to run the project smoothly https://www.esds.co.in
- 5. Requirement Gathering and Analysis Design Development Phase Testing Deployment and Maintenance Stages of SDLC https://www.esds.co.in
- 6. Stage 1 Requirement Gathering & Analysis Phase In an SDLC, this is the first and most crucial phase for a software project’s success. In this phase, communication takes place between stakeholders, end-users, and project teams, as both functional and non- functional requirements are gathered from customers. https://www.esds.co.in
- 7. The Requirement Gathering & Analysis Phase of SDLC involves the following 1. Analysis of functionality and financial feasibility 2. Identifying and capturing requirements of stakeholders through customer interactions like interviews, surveys, etc. 3. Clearly defining and documenting customer requirements in an SRS (Software Resource Specification Document) comprising of all product requirements that need to be developed 4. Creating project prototypes to show the end-user how the project will look https://www.esds.co.in
- 8. Stage 2 Design Phase In the design phase of an SDLC, the architectural design is proposed for the project based on the SRS Document requirements. 1. Separation of hardware and software system requirements 2. Designing the system architecture based on gathered requirements 3. Creating Unified Modelling Language (UML) diagrams like- use cases, class diagrams, sequence diagrams, and activity diagrams The Designing Phase of SDLC involves the following https://www.esds.co.in
- 9. Stage 3 Development Phase In the entire SDLC, the development phase is considered to be the longest one. In this phase, the actual project is developed and built. 1. Actual code is written 2. Demonstration of accomplished work presented before a Business Analyst for further modification of work 3. Unit testing is performed, i.e., verifying the code based on requirements The Development Phase of SDLC involves the following https://www.esds.co.in
- 10. Stage 4 Testing Phase Almost all stages of SDLC involves the testing strategy. However, SDLC’s testing phase refers to checking, reporting, and fixing the system for any bug/defect. In this phase, the on-going system or project is migrated to a test environment where different testing forms are performed. This testing continues until the project has achieved the quality standards, as mentioned in the SRS document during the requirement gathering phase. The Testing Phase involves the following- 1. Testing the system as a whole 2. Performing different types of test in the system 3. Reporting and fixing all forms of bugs & defects https://www.esds.co.in
- 11. Stage 4 Deployment & Maintenance Phase In this SDLC phase, once the system testing has been done, it is ready to be launched. The system may be initially released for limited users by testing it in a real business environment for UAT or User Acceptance Testing. 1. The system is ready for delivery 2. The system is installed and used 3. Errors are rectified that might have been previously missed 4. Enhancing the system inside a data center The Deployment & Maintenance Phase involves the following- https://www.esds.co.in
- 12. https://www.esds.co.in Various SDLC models are defined and designed to follow the software development process. These models are also known as Software Development Process Models. Each of these models follows a series of steps for ensuring the complete success of a project. SDLC Models
- 13. Some of the most popular SDLC models used for software development include Iterative- Incremental Model Spiral Model Rapid Action Development (RAD) Model Waterfall Model Agile Model https://www.esds.co.in
- 14. Waterfall Model This model is the most commonly used SDLC model. In this model, each phase starts only after the previous step has been completed. This is a linear model having no feedback loops. https://www.esds.co.in
- 16. Strengths of the Waterfall Model Works well when the project Quality is important Easy to Understand and Use Achievements are well-defined Defines requirements stability Weaknesses of the Waterfall Model Testing begins only after the development phase is complete It cannot match reality well Difficult to make changes Software delivered towards the end of the project only https://www.esds.co.in
- 17. Iterative- Incremental Model In this model, in the initial stages, a partial implementation of the complete system is constructed such that it will be present in a deliverable form. Increased functionalities are added and for any defects, they are fixed with the working product delivered at the end. This process is repeated until the product development cycle gets completed. These repetitions of processes are known as iterations. With each iteration, a product increment gets delivered. https://www.esds.co.in
- 19. Strengths of the Iterative- Incremental Model Changes in requirements can be easily adjusted The initial delivery of the product is faster Prioritized requirements can be initially developed Lower initial delivery costs Weaknesses of the Iterative- Incremental Model Clear module interfaces are required There are requirements for effective iterations planning Efficient design is required for including the required functionalities An early definition of a complete, as well as fully functional system, is needed for allowing increments definition https://www.esds.co.in
- 20. Spiral Model The spiral model combines risk analysis along with RAD prototyping to the Waterfall model. Each of the cycles has the same steps as in the case of the Waterfall model. https://www.esds.co.in
- 22. Strengths of the Spiral Model Critical & high-risk functionalities are initially developed Users are involved in all lifecycle stages Users can have a look at their system early due to rapid prototyping tools An early indication of the risks can be provided, without incurring much cost Weaknesses of the Spiral Model Time spent on addressing risks can be large for smaller & low-risk involved projects The spiral may go on indefinitely The spiral model can be complex to understand for new members It may be hard to set the objectives, verifiable milestones for indicating preparedness to go ahead with the next iteration https://www.esds.co.in
- 23. Agile Model The agile model is the combination of the iterative-incremental model that depends on process adaptability along with customer satisfaction through the delivery of software products. In this model, the project is broken down into smaller time frames for delivering certain features during a release. https://www.esds.co.in
- 25. Strengths of the Agile Model Functionalities can be developed quickly and demonstrated to customers Regular communication takes place between customers and developers Easy to accommodate changing requirements Weaknesses of the Agile Model Teams need to have the desired experience levels for adhering method rules Not ideal for handling complex dependencies https://www.esds.co.in
- 26. Rapid Application Development (RAD) Model The RAD SDLC model is based on prototyping and iterative development, with no involvement of a defined planning structure. In this model, different function modules are parallelly developed as prototypes and then integrated to speed up product delivery. https://www.esds.co.in
- 27. Rapid Application Development (RAD) Model https://www.esds.co.in
- 28. Strengths of RAD Model Customer’s continuous involvement ensures minimal risks of not achieving customer satisfaction Reduced cycle time and enhanced productivity with minimal team members Easy to accommodate any user changes Weaknesses of RAD Model Heavily dependent on technically strong members for identifying business requirements Hard to use and implement with legacy systems https://www.esds.co.in