Laup

WATERFALL MODEL
The Waterfall Modeling is an early stage in the SDLC process. In fact, it was the first model to be
widely used in the software industry
WATERFALL MODEL
Requirements analysis
The Waterfall methodology depends on the belief that all project requirements can be
gathered and understood upfront. The project manager does their best to get a detailed
understanding of the project sponsor’s requirements. Written requirements, usually contained
in a single document, are used to describe each stage of the project, including the costs,
assumptions, risks, dependencies, success metrics, and timelines for completion.
Design
Here, software developers design a technical solution to the problems set out by the product
requirements, including scenarios, layouts, and data models. First, a higher-level or logical
design is created that describes the purpose and scope of the project, the general traffic flow of
each component, and the integration points. Once this is complete, it is transformed into a
physical design using specific hardware and software technologies.
Implementation
Once the design is complete, technical implementation starts. This might be the shortest phase
of the Waterfall process because painstaking research and design have already been done. In
this phase, programmers code applications based on project requirements and specifications,
with some testing and implementation taking place as well. If significant changes are required
during this stage, this may mean going back to the design phase.
Verificate
Before a product can be released to customers, testing needs to be done to ensure the product
has no errors and all of the requirements have been completed, ensuring a good user
experience with the software. The testing team will turn to the design documents, personas,
and user case scenarios supplied by the product manager to create their test cases.
Deployment Maintenance
Once the software has been deployed in the market or released to customers, the maintenance
phase begins. As defects are found and change requests come in from users, a team will be
assigned to take care of updates and release new versions of the software.
ADVANTAGES
Economic, simple, easy to follow, easy to keep up, reduce costing time.
DISADVANTAGES
Project scope changes are not allowed, Do not allow to change the requirements of the project,
No working product until the project is near completion, It is not easy to handle unexpected
risks
Description of V model
Concepts
The V-Model (or V-model) is a highly disciplined SDLC (Software Development Life Cycle) model
in which there is a testing phase that runs parallel to each phase of development. The V-model
is an extension of the Waterfall model, where testing is performed on each phase in parallel
with development in a sequential manner. It is also known as the Validation Model or
Verification Model.
Pictures of Models
Model analysis
The V-model is an SDLC model where execution of processes happens in a sequential manner in
a V-shape. It is also known as Verification and Validation model.
The V-Model is an extension of the waterfall model and is based on the association of a testing
phase for each corresponding development stage. This means that for every single phase in the
development cycle, there is a directly associated testing phase. This is a highly-disciplined
model and the next phase starts only after completion of the previous phase.
Advantages
• Simple and easy to use.

• Testing activities like planning, test design take place before code is written. This saves a
lot of time. Therefore, there is a higher chance of success compared to the waterfall
model.
• Actively track bugs - these are bugs found at an early stage.

• Good application in small projects, easy to understand requirements.
Disadvantages
• Very rigid not flexible.

• The software is developed in the implementation phase so no early prototypes of the
software have been released.
• If any changes occur during the development phase, the test document along with the
requirements document must be updated again.
The Iterative development model

Concepts
Iterative development is a software development method that divides the development of a
large application into smaller pieces. Each section, called an "iteration," represents the entire
development process and contains the planning, design, development, and testing steps. Unlike
the Waterfall model, the iterative process adds features one at a time, providing an active
product at the end of each iteration, and increasing functionality from cycle to cycle.
Pictures of Models
Model analysis
The iterative life cycle model comprises repeating the below-mentioned four stages as a
sequence. These are:
• Requirements Phase: In the requirements phase of software development, the system-

related information is gathered and analyzed. The collected requirements are then
planned accordingly for developing the system.
• Design Phase: In the Design phase, the software solution is prepared to meet the
necessities for the design. The system design may be a new one or an extension of a
previous build.
• Implementation and Test: In the implementation and test phase, the system is
developed by coding and building the user interface and modules, which are then
incorporated and tested.
• Review Phase: The review phase is where the software is estimated and checked per the
current requirement. Then, further needs are reviewed discussed and reviewed to
propose an update in the next iteration.
Advantages
• Some working functionality can be developed quickly and early in the life cycle.
• Results are obtained early and periodically.
• Parallel development can be planned.
• Progress can be measured.
• Less costly to change the requirements.
• Testing and debugging during smaller iteration is easy.
• Easier to manage risk.
• It supports changing requirements.
• Initial Operating time is less.
• During the life cycle, software is produced early which facilitates customer evaluation
and feedback.
Disadvantages
• It’s need more resources.

• More management attention is needed.
• Determining the increment may require defining the entire system.
• Not suitable for smaller projects.
• More management complexity.
• Skilled resources are required for risk analysis.
Incremental Model
Concept
An incremental model is an approach to software development in which requirements
are broken down into many distinct modules of the software development cycle. In this model,
each module goes through the requirements, design, implementation, and testing phases. Each
subsequent version of the module adds features to the previous iteration. Continue the process
until a full system is reached.
Model Figure
Model analysis
• Requirements Analysis: In the first step of the incremental model, the product analyst
determines the requirements. For incremental software development, this phase plays a
vital function.
• Design & Development: During this phase of the SDLC Incremental model, the design of
the system functionality and the development process has been effectively
accomplished.
• Testing: In the incremental approach, the testing step examines the performance of
each current feature and the extra functionality. During the testing phase, multiple
approaches are employed to test the behavior of each task.
• Deployment: The deployment phase permits the coding phase of the system to evolve.
It incorporates final design coding in the design and development phase and functional
testing in the testing phase. Upon completion of this phase, the number of active
products is supplemented and upgraded to the final system product.
Advantages:
• Errors are straightforward to spot.

• Easier to test and troubleshoot
• More adaptable.
• Simple to manage risk because it is handled in iteration.
• The client gains key functionality early.
Disadvantages:
• This model demands precise planning and design.

• Problems in one unit must be repaired in all units, which takes a long time.
• High overall cost.
• Well-defined modular interfaces are needed.

Laup

Uploaded by

Copyright:

Available Formats

Laup

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Laup

Uploaded by

Copyright:

Available Formats

WATERFALL MODEL

• Simple and easy to use.

• Actively track bugs - these are bugs found at an early stage.

• Very rigid not flexible.

The Iterative development model

• Requirements Phase: In the requirements phase of software development, the system-

• It’s need more resources.

• Errors are straightforward to spot.

• This model demands precise planning and design.

You might also like