Verification and Validation of Software (V&V)

V&V in the life cycle of software development

The verification and validation is an important part of the software development part but when it comes to the cycle development a perspective is given to the two words due to the similarity but this terms as V&V are independent actions, and even part of a cycle.

Verification can sometimes mean building the right software, and for the right causes. And even the correctness of the building process. If it satisfies the requirements that can be previously defined on the preceding phase. This is a matter for the acceptance and what the client asks.

Validation is more about building que software right. Correctness of the product is when the valuation of the software at the end is ensuring that is free from failures and compiles with its requirements. To ensure that the clients and the needs and specifications are correct.

International standards for V&V of Software

Most of the time verification ensures that the system compiles with an organization’s standards and process. The software engineering standards known as IEEE STD 610 defines verification as a test of a system to prove that ir meets all its specified requirements at a particular stage of its development . The key part of verification definition is that at a particular stage of its development and before even coding begins on any application a set of specification have been previously defined.

The verification of development make reference to the application check that can can ensure being developed to adhere to these specifications. This checklists or tasks can sometimes be something like reading the specification comparing them against the code logic to make sure all is lined up. This kind of testing make sure and kelps to change the identification and resolution of any additional bug left.

Planning V&V

Being aware of the explicitly stated and agreed of the functional and on functional requirements may be termed as quality for the software product offered to the final customer and their designation.

Planning comes to take place in the initial part of a software project phase and should address the methods and techniques to be used in each phase. The description of each product should be defines in order to provide a basis for objectively identified a satisfactory and complete planning of the phase. The quality of the software management processes must be directed in how is the software products will go, good? or what they do, satisfy customer requirements. Provide value to the costumers and quality that it needs to meet the requirements. In the standard IEEEE12207.0-96 the processes are defined as:

  • Quality assurance the process
  • Verification process
  • Validation process
  • Review process
  • Audit process

Administration of a V&V Plan

Software quality Assurance processes give a confort and assurance that the product and the software processes in the software life cycle conform to their specified requirements by planning enacting and performing a set of activities ro provide adequate confidence that the quality is being build into the software. SQA pursue the quality of maintain throughout the development and maintenance of the product by the execution of a variety of activities at each stage which can result in early identification of problems, and even face to an inevitable complex activity.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Create a website or blog at

Up ↑

Create your website with
Get started
<span>%d</span> bloggers like this: