Principle Of Waterfall Methodology

1815 Words 8 Pages
Waterfall Methodology

Waterfall model was developed as a solution to Ad-hoc development methodologies.

• A staged development model
• Stages will be completed one after the other.
• Subsequent stage can be started once the previous one is completed only.
Waterfall model follow software development process in a linear sequential.
• This model phases are do not overlap.
Principle of Waterfall Methodology
The waterfall model describes 6 phases.

I. Requirement gathering.
All the required functions and requirements are identified in this stage. Those are the things that end users except from the system. Finally a document is created named requirement specification document. After that we can decide time, deadlines, possibility,
…show more content…
This is used for large, expensive, and complicated projects.. This is more emphasis placed on risk analysis. We called as Spirals because each phases are iteration.
Principle of Spiral Methodology
The spiral model is describe 4 phases. 1. Planning phase
In this stage we do requirement study and gathering them. Therefore identify System requirement, Subsystem requirement, unit requirement and finalize list of all requirement are done in this step.
2. Risk Analysis phase
All the requirements will study and identify the risk points in the phase. After analyzing the risk points, then it will be finalized to manage. After Complete these document all of risk and plan to eliminate it.
3. Development/Engineering phase
This phase software is developed, it will ready for testing. Testing is the main thing in this step. All codes are testing. After test.
Everything will do according to test case and test plan.
4. Evolution phase
The developed software gives to the end users to evaluate. After that customer is provide their feedback and approval for this. Finally complete features implemented document.

Strengths of Spiral
…show more content…
Multiple Models
It is used to identify the usage of multiple models in developing software. Because each model describes single requirement of the developing software
4. Rapid Feedback
Having a strong relationship with the customer to get the requirements what they need. This will helpful to add function and develop each interfaces. System will be designed according to the requirements that are gathered in this step.
5. Assume Simplicity
This phase tell if we use simplest solution it is the best solution. Don’t try overbuilding the software. Keep your model as simple as possible.
6. Embrace Change
This phase tell if change the project’s environment as effort progress approach will reflect this reality as soon as possible.
7. Travel Light
This phase tell development team want to create develop and maintain detailed requirement document, detailed collection of analysis models, detailed collection of architectural models detailed collection of design models and updating document instead of writing source codes.
8. Incremental changes
Developers don’t need every single detail of the project. . Developer can instead small model perhaps high-level model. After that change it incremental

Related Documents