Explain V model in depth?

Question Posted / guest

2 Answers
7559 Views
Tech Mahindra, I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

Explain V model in depth?..

Answer / chabs

V-model is also known as Verification and Validation model
where the development and the testing team works parallely.
The CRS/BRS is sent to both developing and testing teams.
Where the developers/designers develop HLD, LLD then do
coding while the testers review and develop Acceptance test
cases and test plans, Integration test plans & cases,
functional test plans & cases.(in each stage i.e.,
CRS,SRS,HLD,LLD will be reviewed by the test engineers and
new document will be constructed if in case of any changes)

After white box testing is done at the developers side, the
product or the software is sent to the testing.

Now, this product is tested using the test plans and cases
(i.e.,they do Functional testing, Integration testing,
Acceptance testing) previously developed by the test
engineers(In the first phase they only develop test plans
and cases).
Finally, after doing the Acceptance testing the product is
moved to the production.

Advantage of this model is that each phase is tested
(i.e., defects in the customer requirements or any of the
documents is found out at the first phase)
so defects are rectified at an early stage.

Is This Answer Correct ?

6 Yes

0 No

Explain V model in depth?..

Answer / ashish

The V-model is a graphical representation of the systems
development lifecycle. It summarizes the main steps to be
taken in conjunction with the corresponding deliverables
within computerized system validation framework.

The VEE is a process that represents the sequence of steps
in a project life cycle development. It describes the
activities and results that have to be produced during
product development. The left side of the VEE represents
the decomposition of requirements, and creation of system
specifications. The right side of the V represents
integration of parts and their verification

A concept of operations that describes user needs and the
operating environment, thorough and testable system
requirements, detailed design, implementation, rigorous
acceptance testing of the implemented system to ensure it
meets the stated requirements (system verification),
measuring its effectiveness in addressing goals (system
validation), on-going operation and maintenance, system
upgrades over time, and eventual retirement

Is This Answer Correct ?

3 Yes

2 No

Post New Answer