Name:Husnain Haider

Section:S
Roll no:70067977
Subject:OOSE
Assignment No:6
………………………………………………………………………………
Question 1:
Describe the waterfall model for software development and list three of its
advantage for software development.
Ans:
Waterfall Model is a sequential model that divides software development into
pre-defined phases. Each phase must be completed before the next phase can
begin with no overlap between the phases. Each phase is designed for performing
specific activity during the SDLC phase. It was introduced in 1970 by Winston
Royce.

In The Waterfall approach, the entire process of software

development is split into separate phases. In this Waterfall model, typically, the
result of 1 phase acts because the input for subsequent phase sequentially.

The Sequence of Water fall model are:

➢ Requirement Analysis
➢ System Design
➢ Implementation
➢ System Testing
 ➢ System Deployment
➢ System Maintenance

Different phases of Waterfall model that works on software

development are:

Requirement Gathering Stage:

During this phase, detailed requirements of the software system to be developed
are gathered from client

Design Stage:
Plan the programming language like java,jsf and php.
database like Oracle, MySQL, etc.

Implement Stage:
After design stage, it is implement stage that is nothing but coding the software to
Their requirements.

Test stage:
In this phase, you test the software to verify that it is built as per the
specifications given by the client.
Deployment Stage:
Deploy the application in the respective environment.

Maintenance Stage:
Once your system is ready to use you may later require change the code as per
customer request.

Waterfall model uses in SDLC:

Waterfall model can be used when

➢ Project is short.
➢ Requirement is clear.
➢ Environment is stable.
➢ Resources are available and trained.

Advantages according to Software Developmet:

• It is easy to manage due to the rigidity of the model each phase has
specific deliverables and a review process.
 • Waterfall model works well for smaller projects where requirements are
clearly defined and very well understood.

• In this model phases are processed and completed one at a time. Phases do
not overlap.

Q2:What is V Model? Write down the example to understand the V Model.

Ans:

V model:
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.

V model Design:

Under the V-Model, the corresponding testing phase of the development phase is
planned in parallel. So there are Verification phases on one side of the V and
Validation phases on the other side. The Coding Phase joins the two sides of the
V-Model.
V Model – Verification Phase:
Requirement Analysis:

This phase contains detailed communication with the customer to

understand their requirements and expectations. This stage is known as
Requirement Gathering.

System Design:
This phase contains the system design and the complete hardware and
communication setup for developing product.

Architecture Design:
System design is broken down further into modules taking up different
functionalities. The data transfer and communication between the internal
modules and with the outside world is clearly understood.

Module Design:
In this phase the system breaks down into small modules. The detailed design of
modules is specified, also known as Low-Level Design (LLD).

V Model – Validation Phase:

Unit Testing:
Unit Test Plans are developed during module design phase. These Unit Test Plans
are executed to eliminate bugs at code or unit level.
Integration Testing:
After completion of unit testing Integration testing is performed. In integration
testing, the modules are integrated and the system is tested. Integration testing is
performed on the Architecture design phase. This test verifies the communication
of modules among themselves.

System Testing:
System testing test the complete application with its functionality, inter
dependency, and communication.It tests the functional and non-functional
requirements of the developed application.

Acceptance Testing:
UAT is performed in a user environment that resembles the production
environment. UAT verifies that the delivered system meets users requirement
and system is ready for use in real world.

V –Model Applications to use:

The following pointers are some of the most suitable scenarios to use the V-
Model application.
• Requirements are well defined clearly documented and fixed.
• Product definition is stable.
• Technology is not dynamic and is well understood by the project team.
• There are no ambiguous or undefined requirements.

Advantages of V model:
 1. It is a highly-disciplined model, and the steps are completed at once.
2. Works well for small projects where the requirements are very well
understood.
3. Easy to understand and use.

Example of V –model that I understand:

The example of the V-Model in the automotive industry.
The coarse view of the model might give the impression that the testing activities
first start only after the control design activities but activities in the opposing
sides of the V actually serve as a base for one another. What is more each of the
steps is typically performed several times. So, during the Control Design phase the
developer can also design functions and perform initial validation procedures.
Similarly during 'Function Prototyping' several tests can be run off-line or in an
actual vehicle or test bed. During the 'Automatic Production Code Generation the
prototyped functions are converted into code and deployed in the ECU. Testing
and calibration tasks can be run through each one of the other phases.

Question 3:
list down the comparison between water fall model and V model.

Ans:

Comparison between water fall model and V model.

Waterfall model V model

The waterfall model is relatively The V model is a model in which
Linear sequential design approach to extension of phases happens in
Develop software projects. sequential manner in V shape.

Waterfall model is continuous The V model is Simultaneous process

process

Waterfall model is less used now-a- V-model is widely used in software

days in software engineering. engineering.

Guarantee of success through Guarantee of success through V-

Waterfall model is low. model is high.

In waterfall model testing activities In V-model testing activities start

start With the first stage.
After the development activities are
over.

Software made using Waterfall Software made using V-model, the

model, the number of defects are number of defects are greater in
less in comparison of software made comparison of software made using
using V-model. Waterfall model.