The
V-Concept of Testing - The
various steps involved in V-concept are listed
below:

Step
4: Test Software Design
This step tests both external and internal design
primarily through verification techniques. The
testers are concerned that the design will achieve
the objectives of the requirements, as well as
the design being effective and efficient on the
designated hardware.

Step 5: Program (Build)
Phase Testing
The method chosen to build the software from the
internal design document will determine the type
and extensiveness of tests needed. As the construction
becomes more automated, less testing will be required
during this phase. However, if software is constructed
using the waterfall process, it is subject to
error and should be verified. Experience has shown
that it is significantly cheaper to identify defects
during the construction phase, than through dynamic
testing during the test execution step.

Step 6: Execute and Record
Results
This involves the testing of code in a dynamic
state. The approach, methods, and tools specified
in the test plan will be used to validate that
the executable code in fact meets the stated software
requirements, and the structural specifications
of the design.

Step 7: Acceptance Test
Acceptance testing enables users to evaluate the
applicability and usability of the software in
performing their day-to-day job functions. This
tests what the user believes the software should
perform, as opposed to what the documented requirements
state the software should perform.

Step
8: Report Test Results
Test reporting is a continuous process. It may
be both oral and written. It is important that
defects and concerns be reported to the appropriate
parties as early as possible, so that corrections
can be made at the lowest possible cost.

Step 9: The Software Installation
Once the test team has confirmed that the software
is ready for production use, the ability to execute
that software in a production environment should
be tested. This tests the interface to operating
software, related software, and operating procedures.

Step 10: Test Software Changes
While this is shown as Step 10, in the context
of performing maintenance after the software is
implemented, the concept is also applicable to
changes throughout the implementation process.
Whenever requirements change, the test plan must
change, and the impact of that change on software
systems must be tested and evaluated.

Step 11: Evaluate Test Effectiveness
Testing improvement can best be achieved by evaluating
the effectiveness of testing at the end of each
software test assignment. While this assessment
is primarily performed by the testers, it should
involve the developers, users of the software,
and quality assurance professionals if the function
exists in the IT organization.