Principle Of Waterfall Methodology

Decent Essays
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

  • Decent Essays

    Tartan Case Study

    • 969 Words
    • 4 Pages

    In the Elaboration Phase, we finished gathering our requirements and specifications. We also clear all design feasibility questions and metrics would be used to measure our system. At this phase, the software project is ready to go. The goal of Construction Phase is to complete the implementation and release an Alpha version product. Finally, we fix all the issues and integrate all the components in Transition Phase.…

    • 969 Words
    • 4 Pages
    Decent Essays
  • Decent Essays

    Generally Unit testing is performed by developers or its peers. Sometimes independent software testers are used to do Unit testing. Unit testing is also referred as component testing. Before integrating the modules, the unit or piece of code is identified as a component and complete testing was carried out to ensure expected output. I.e., for any function or procedure a proper output is expected when an input was given.…

    • 1409 Words
    • 6 Pages
    Decent Essays
  • Decent Essays

    Again If the project doesn’t pass this milestone it may be cancelled or Inception Phase re started. Construction Phase is next, a manufacturing process where all components and features are developed, integrated into the system and tested thoroughly. Costs and schedules are important and are managed diligently at this phase. The ultimate outcome, a software product that is useable for the client/end user. Initial Operational Capability Milestone is reached at this point, this is a major milestone.…

    • 1559 Words
    • 7 Pages
    Decent Essays
  • Decent Essays

    TEST SPECIFICATION Testing is an important part of software development life cycle. It is performed to ensure quality of the developed system. Testing includes a set of investigative activities that can be planned in advance and conducted systematically, to assure the stakeholder that system ful lls all the requirements gathered during requirement gathering phase. Software testing is one of the key elements in software projects that is often referred to as veri cation and validation. Veri cation refers to the set of activities that ensure that software correctly implements speci ed functionality.…

    • 1596 Words
    • 7 Pages
    Decent Essays
  • Decent Essays

    As a software development team progresses through the five phases of the waterfall method it is not uncommon to find a firm that will assign each phase to a different department within the company. The firm will choose a department that is specialized to handle the task at hand for each phase of the project. For example, the finance department may handle the analysis phase to document a complete and comprehensive description of the software that is necessary to make their jobs easier. After the analysis step is complete the project can move to an IT department to implement the design and analysis phases. When using a waterfall method it is common for a firm to involve a numerous number of resources to handle different tasks.…

    • 1560 Words
    • 7 Pages
    Decent Essays
  • Decent Essays

    SOFTWARE REQUIREMENT SPECIFICATION Software development life cycle(SDLC) consists various phases: requirement gath- ering and analysis, design, implementation or coding phase, testing, deployment and maintenance. In this section, we specify the software requirements of the proposed EFFM system. This phase is critical to the success of the project. Requirement analy- sis is an art and science. In requirement gathering and ananlysis, customer expectations need to be eshed out in great detail and documented.…

    • 1824 Words
    • 8 Pages
    Decent Essays
  • Decent Essays

    1.1 Testing: Software testing is a phase in the software development that is used to provide stakeholders of the projects with information about the quality of the product or service that has been tested. Software Testing is also used to provide the objective and independent view of the system and that view allow to realize and understand the risks that could be faced at the implementation of the software. Multiple test techniques are included in the process of executing a program or application that has to be implemented with the intention of finding software bugs and errors. Testing is the process of finding, detecting, or discovering errors. Testing plays a important role in assuring that we have achieved the required set of quality and…

    • 842 Words
    • 4 Pages
    Decent Essays
  • Decent Essays

    In order accomplish this, the system is broken down into different pieces to analyze the project 's goails, gathering what needs to be created and including users so that definite requirements can be made. Designing – The purpose of this phase is to create a design that meets the agreed upon requirements. This is the point where it moves from the “what” part of the analysis to the “how”. Implementation and deployment – It is after complete understanding of the requirements and specifications of the system. Requirements in this stage make use of the hardware and the code being developed, as these determine the success of this stage.…

    • 819 Words
    • 4 Pages
    Decent Essays
  • Decent Essays

    I understood that management goals and objectives set the tone of projects. Thus, I defined project goals and objectives from management point of view. I tried to find and document all possible constraints and assumptions relating to the project. From that instance, I figured out and as well documented how the project will be monitored and controlled and how progress and performance reporting will be communicated. During the IT project management plan development process, all the project scope of work is defined and denoted in a work breakdown structure format.…

    • 842 Words
    • 4 Pages
    Decent Essays
  • Decent Essays

    Scope of whole project contains completion all the documentation details. Completion of project will take place when the software and hardware are completely designed and fully tested. MILESTONE LIST The chart given below shows the milestone of this project. It shows the description and the dates of the milestones that should be completed on the given date. If any delay takes place then which can affect the milestone list then project manager will be informed immediately.…

    • 1488 Words
    • 6 Pages
    Decent Essays