Pros and Cons of deploying an Independent V and V Contractor-IV and V
An independent V&V contractor may sometimes be used to insure independent objectivity and evaluation for the customer.
The use of a different organization, other than the software development group, for software V&V is called independent verification and validation (IV&V).
Following three types of independence are usually required:
1) Technical Independence:
It requires that members of the IV&V team (organization or group) may not be personnel involved in the development of the software. This team must have some knowledge about the system design or some engineering background enabling them to understand the system. The IV&V team must not be influenced by the development team when the IV&V team is learning about the system requirements, proposed solutions for building the system and problems encountered. Technical independence is crucial in
the team’s ability to detect the subtle software requirements, software design and coding errors that escape detection by development testing and SQA reviews.
The technical IV&V team may need to share tools from the computer support environment (e.g. compilers, assemblers, utilities) but should execute qualification tests on these tools to ensure that the common tools themselves do not mask errors in the software being analyzed and tested. The IV&V team uses or develops its own set of test and analysis tools separate from the developer’s tools whenever possible.
2) Managerial Independence:
It means that the responsibility for IV&V belongs to an organization outside the contractor and program organizations that develop the software. Specific project requirements & statutory regulations will dictate the assurance objectives, the independent verification and validation teams take the decision independently on the areas of the software system for analyzing & testing, techniques for doing IV&V, scheduling different tasks & other technical issues needing consideration. It is the responsibility of IV&V team to timely circulate all the findings the development team as well as the systems management for necessary action thereafter.
3) Financial Independence:
It means that control of the IV&V budget is retained in an organization outside the contractor and program organization that develop the software. Such an independence takes care of undue diversion of various funds, other unfavorable financial influences which are liable to cause undue delay or even stopping of IV&V and testing activities.