What is the "Fountain Development Model"?

Question

This is mentioned on the System Development Life Cycle page on Wikipedia :

To cope with this, several system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, assembly and patching, rapid prototyping, incremental synchronization and stabilization.

I found a few things on Google, but I felt they were vague and they just didn't click on me. Perhaps the explanation from someone here may be clearer.

Answer 1

A waterfall is a model that provides control and avoids parallelism; Before starting a task, you must fulfill each requirement for the task. The fountain says that a new task can be launched before all requirements are met, because not all requirements are necessary at the beginning of the task.

Think about it: Super Mario Game,

Waterfall: first design everything, then do the hardware (Hardware Team), then create some sprites, then encode the engine, then create a cover, then music and finish.

Fountain: while the hardware team does its work, the artwork begins the conceptual work, and the coding begins with prototyping the already existing hw. When the artists and hw end, the coders integrate them into their code and continue "until the end of the game ...

Answer 2

The fountain . Stand in a circle and drop some patterns and keywords in the air to see where they land. Take only those that land inside the circle. Repeat until canceled.

Waterfall Screw everyone into the boat, then scream "Geronimo!" crossing the Niagra Falls. Take the broken pieces, then rinse and repeat. Make sure he has well documented which part of the boat each person should be on, what they should hold on to, how to shout loudly and exactly where they should land. See Form 3684-B for additional instructions.

Spiral : select one member of the team and ask everyone else to spin them in a circle until dizziness begins.

Build and fix : just drop it against the wall to see which sticks. If something falls, add some masking tape. Used chewing gum may also work. Any part that does not remain stuck, just throw it away.

Rapid prototyping . Do what the client asked. Repeat until you find out what they want.

Incremental : only create the parts you want, and only when you want to do it. An alternative version is only to create parts that they scream louder, and only when they really stand at your table, waiting for him.

Synchronization and stabilization . Like a spiral, except that one person at a time rotates an unlucky team member. When their rotation is complete, stop the rotation for a moment.

Answer 3

As I understand it, they essentially contain the same steps, but the fountain approach is much more iterative, with less focus on the initial design and much more on analysis.

You basically make your way. See what should happen and improve it. See what is going to happen. Improve it.

This is more flexible, but at the cost of project stability. The waterfall is much better for large projects.