Please enable JavaScript.
Coggle requires JavaScript to display documents.
A Comparative Study of Different Software Development Life Cycle Models in…
A Comparative Study of Different Software Development Life Cycle Models in Different Scenarios
Information
SDLC models are very important for developing the software in a systematic manner such that it will be delivered within the time deadline and should also have proper quality
One life cycle model theoretically may suite particular conditions and at the same time other model may also look fitting into the requirements but one should consider trade-off while deciding which model to choose (Roger Pressman)
Software projects go through the phases of requirements gathering, business analysis, system design, implementation, and quality assurance testing
Models
WATERFALL MODEL
Proposed by Royce in 1970
A linear sequential software development life cycle
Phases
Requirements
Design
Implementation
Testing
Deployment and maintanence
Various phases followed in such a manner that the phase once over is not repeated again and the development does not move to next phase until and unless the previous phase is completely completed. Hence it is not very much useful when the project requirements are dynamic in nature
RAD MODEL
Requirements are well understood and project scope is constrained
Very short time periods
INCREMENTAL MODEL
V-SHAPED SDLC MODEL
A variant of the Waterfall that emphasizes the verification and validation of the product, testing of the product is planned in
parallel with a corresponding phase of development
SPIRAL MODEL
Starts with a small set of requirements and goes through each development phase
In response to the weaknesses and failures of the Waterfall SDLC Model, many new models were developed that add some form of iteration to the software development process
Based on lesson learned from the initial iteration, the development team adds functionality for additional requirements in ever-increasing “spirals” until the application is ready for the Installation and Maintenance phase
Phases
Common phases
Deciding a plan for a solution (Designing)
Coding the planned solution
Testing the actual program
Deployment & maintenance of the product
Understanding the problem (through requirements gathering
Some activities are performed after the main development is complete. There is often an installation phase, which is concerned with actually installing the system on the client’s computer systems and then testing it
Comparison
Goals
Objective
Problem
Results / Contribution