2. -The Fountain model is a logical improvement to the
Waterfall model. The steps are still there, in the same
sequence, however at any step there can be a fallback
Moving through a number of steps and falling back one
is far more to an or more steps, performed repeatedly,
earlier step.[1]
-The fountain model recognizes that although some
activities can't start before others -- such as you need a
design before you can start coding -- there's a
considerable overlap of activities throughout the
development cycle.[4,5]
3. - User requirements analysis
- User requirements specifications
- Software requirements specifications
- Systems/broad design, logical design
- Program/detailed design, physical design
- Implementation/coding
- Program testing: units
- Program testing: system
- Program use
- Software maintenance
4. -More flexible than the Waterfall model
- Not having to freeze the requirements too
soon
- Many more interactions between design and
requirements
- Able to start the coding earlier
5. - Some phases cannot begin before others [3]
-Some phases are poorly delineated [3]
-Doesn’t Reflect Object Orientation [6]
-Unable To Commit Deliverables [6]
7. 1-CS 551 , Assignment, OO Software Lifecycle Models, Due(10/30/2000), By Hemant Gore
2-CS 230 Introduction to Software Engineering, K.Goseva 2006
3-CSE2305 - Object-Oriented Software Engineering, Topic 13: The Software Development
Process,
http://www.csse.monash.edu.au/~jonmc/CSE2305/Topics/07.13.SWEng1/html/text.ht
ml#fountain_model
4-Glexiangmhaya, a variety of inspiring topics that relates to innovations which promotes
appreciative view to life, Identifying and discussing at least 3 systems development
models, http://feedyoursoulmindheart.blogspot.com/2010/01/identifying-and-
discussing-at-least-3.html
5-Computerworld, QuickStudy: System Development Life Cycle,
http://www.computerworld.com/s/article/71151/System_Development_Life_Cycle
6-Software Development Life Cycle by David Aung on Aug 06, 2009,
http://www.slideshare.net/yangontar/software-development-1824695