The document discusses and compares several software development life cycle (SDLC) models: - Waterfall model works well for small projects with clear requirements but is risky for complex projects with changes. - Spiral model is better suited to unclear or complex requirements and allows for frequent changes and releases. However, it can be costly and risk analysis requires expertise. - Agile model uses iterative development in short cycles to provide working software quickly and adapt to changes. It facilitates flexibility but lacks documentation. - Big Bang model has little planning and is flexible but carries very high risk and uncertainty if requirements are unclear.

1. 5

3. 3

7. Requirements are very well known, clear
and fixed.
Product definition is stable.
Technology is understood.
The project is short.

8. 1) This model is simple and easy to
understand and use.
2) Waterfall model works well for smaller
projects where requirements are very well
understood.
3) Phases are processed and completed one
at a time.

9. 1) Once an application is in the testing stage,
it is very difficult to go back and change
something.
2) High amounts of risk and uncertainty.
3) Not a good model for complex and object-
oriented projects.

12. When requirements are unclear and
complex.
When releases are required to be frequent.
When changes may require at any time.
The project is large.

13. 1) Requirements can be captured more
accurately.
2) Additional Functionality can be added at a
later date.
3) High amount of risk analysis hence,
avoidance of Risk is enhanced.

14. 1) Can be a costly model to use.
2) Risk analysis requires highly specific
expertise.
3) Spiral may continue indefinitely.

16. Agile SDLC model is a combination of
iterative and incremental process models
with focus on process adaptability and
customer satisfaction by rapid delivery of
working software product. Agile Methods
break the product into small incremental
builds. These builds are provided in
iterations. Each iteration typically lasts
from about one to three weeks. Every
iteration involves cross functional teams
working simultaneously on various
areas.

18. 1) Is a very realistic approach to software
development.
2) Easy to manage.
3) Gives flexibility to developers.
4) Good model for environments that change
steadily.

19. 1) Not suitable for handling complex
dependencies.
2) More risk of sustainability, maintainability
and extensibility.
3) Transfer of technology to new team
members may be quite challenging due to
lack of documentation.

21. The Big Bang model is an SDLC model
where we do not follow any specific
process. The development just starts
with the required money and efforts as
the input, and the output is the software
developed which may or may not be as
per customer requirement. This Big Bang
Model does not follow a
process/procedure and there is a very
little planning required. Even the
customer is not sure about what exactly
he wants and the requirements are
implemented on the fly without much
analysis.

23. 1) This is a very simple model
2) Little or no planning required
3) Easy to manage
4) Very few resources required
5) Gives flexibility to developers
6) It is a good learning aid for new comers or
students.

24. 1) Very High risk and uncertainty.
2) Not a good model for complex and object-
oriented projects.
3) Poor model for long and ongoing projects.
4) Can turn out to be very expensive if
requirements are misunderstood.