SDLC Models

Different SDLC Models
Waterfall model
A1:It is a Traditional Model, In this Requirements are Freezed in Each and every phase of SDLC
A2: This is the simplest of all the models in SDLC.In this process the phases are organized in a linear and sequential order
What are the advantages & disadvantages of waterfall model
A: Easy to Understand and Coding, identifies deliverables and milestones, works well on mature products and weak teams Disadvantages: Requirements be completely
specified before the rest of the development.
What is Pro-type model
A: The basic idea behind this model is that instead of freezing the requirements before any design or coding, a prototype is built to understand the requirements.
What are the advantages & disadvantages of Pro-type model
A: Development and testing efforts are reduced, reduces risk of incorrect user requirements
Disadvantages:
Development costs may become large
Difficult to estimate the deliverables
What is spiral model
A: The key idea behind this model is to identify and solve the sub-program with the highest risk on each iteration and develop the software in an experimental way.
Each cycle follows a waterfall model by determining objectives, defining constraints; Generating alternatives, identifying and resolving risks, developing next level product and planning next cycle
What are the advantages & disadvantages of spiral model
Adv: it incorporates the advantages of the waterfall and prototype models, it reflects the iterative nature of software development on projects with unclear requirements
What it iterative model
A: It combines the advantages of both waterfall model and Prototype model. In this product should be developed in increments, each increment adding some functional capability to the system until the full system is implemented
What are the advantages & disadvantages of iterative model
Adv: Specifications are handy for the developers and therefore have control of the system
This model is most suitable for the product development.
Explain RAD model
A: It is an incremental software development process that emphasizes a very short development cycle; it is a high-speed adoption of the waterfall model, where the result of each cycle is fully functional