Browse Prior Art Database

Function Verification Test Process Model Disclosure Number: IPCOM000124914D
Original Publication Date: 2005-May-12
Included in the Prior Art Database: 2005-May-12
Document File: 2 page(s) / 95K

Publishing Venue



Complex software has two major problems; code stability and code quality. Code stability can be gauged by test case pass/fail rate. Code quality can only be gauged by analyzing the quality of the tests that are written to exercise the code. Addressing code stability without considering code quality will not improve the overall product quality. We need to address both, together. Product quality has to be checked at every testing phase but since FVT (Functional Verification Test) is the first-step that any product takes outside the development machine, it plays a more critical role in defining product quality. The majority of code stability and quality issues can be resolved by adopting and following a strict FVT process. Using such a process will help us predict code stability at any point in time and focus on testing the product from a quality perspective. This article defines a FVT Process Model that can add tremendous product quality value. The model is suitable for products that are fairly complex and struggling to improve code quality.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 2

Function Verification Test Process Model

In most product shops, regression is considered the end point of the Function Verification Test (FVT) phase. This is true but, regression cannot add-value by itself to product quality if we don't do a good job in the FVT phase. Research has shown that once a defect exits the FVT stage, the chances of finding it before product GA is very slim. Needless to say, the cost per defect also grows exponentially from FVT to GA phase.

The data below shows Cost per Phase. Notice that the majority of defects are exposed in the FVT stage. If we don't find them then, we will most likely not find them during the later test phases.

<Ref> "Building an Automation Business Case", Steven Bell, IBM internal presentation, August 2002
following is an FVT Process Model that can add tremendous product quality value. The model is suitable for products that are fairly complex and need to improve code quality.

Flowchart of FVT Process Model -


[This page contains 1 picture or other non-text object]

Page 2 of 2

Functional V erification T est Phase E nter

C reate FV T Test Plan

Test Plan Review

R ead/Follow T est C ase C reation Standards

T est case R eview : M ap test cases to plan

D evelop Test cases

C heck Test C overage bandw idth using IB M R ational PureCoverage tool?

T est case E xecution Phase

Test passes on all supported platform s?

O pen defect?

Functional Verification Test Phase E xit


[This page contains 1 picture or other non-text obj...