Verification Strategies
The
Verification Strategies, persons / teams involved in the testing, and the
deliverable of that phase of testing is briefed below:
|
Verification
Strategy
|
Performed By
|
Explanation
|
Deliverable
|
|
Requirements
Reviews
|
Users,
Developers, Test Engineers.
|
Requirement
Review’s help in base lining desired requirements to build a system.
|
Reviewed
and approved statement of requirements.
|
|
Design
Reviews
|
Designers,
Test Engineers
|
Design
Reviews help in validating if the design meets the requirements and build an
effective system.
|
System
Design Document, Hardware Design Document.
|
|
Code
Walkthroughs
|
Developers,
Subject Specialists, Test Engineers.
|
Code
Walkthroughs help in analyzing the coding techniques and if the code is
meeting the coding standards
|
Software
ready for initial testing by the developer.
|
|
Code
Inspections
|
Developers,
Subject Specialists, Test Engineers.
|
Formal
analysis of the program source code to find defects as defined by meeting
system design specification.
|
Software
ready for testing by the testing team.
|
1 Review’s
The focus of Review is on
a work product (e.g. Requirements document, Code etc.). After the work product
is developed, the Project Leader calls for a Review. The work product is
distributed to the personnel who involves in the review. The main audience for
the review should be the Project Manager, Project Leader and the Producer of
the work product.
There are three general
classes of reviews:
A)
Informal or Peer Review
B)
Semiformal or Walk-Through
C)
Format or Inspections
i) Peer Review
is generally a one-to-one meeting between the author of a work product and a
peer, initiated as a request for import regarding a particular artifact or
problem. There is no agenda, and results are not formally reported. These
reviews occur on an as needed basis throughout each phase of a project.
ii) Walkthroughs: The author of the
material being reviewed facilitates walk-Through. The participants are led
through the material in one of two formats; the presentation is made without
interruptions and comments are made at the end, or comments are made
throughout. In either case, the issues raised are captured and published in a
report distributed to the participants. Possible solutions for uncovered
defects are not discussed during the review.
iii) Inspections: A knowledgeable
individual called a moderator, who is not a member of the team or the author of
the product under review, facilitates inspections. A recorder who records the
defects found and actions assigned assists the moderator. The meeting is
planned in advance and material is distributed to all the participants and the
participants are expected to attend the meeting well prepared. The issues
raised during the meeting are documented and circulated among the members
present and the management.
Validation Strategies
The Validation Strategies,
persons / teams involved in the testing, and the deliverable of that phase of
testing is briefed below:
|
Validation Strategy
|
Performed By
|
Explanation
|
Deliverable
|
|
Unit
Testing.
|
Developers
/ Test Engineers.
|
Testing
of single program, modules, or unit of code.
|
Software
unit ready for testing with other system component.
|
|
Integration
Testing.
|
Test
Engineers.
|
Testing
of integrated programs, modules, or units of code.
|
Portions
of the system ready for testing with other portions of the system.
|
|
System
Testing.
|
Test
Engineers.
|
Testing
of entire computer system. This kind of testing usually includes functional
and structural testing.
|
Tested
computer system, based on what was specified to be developed.
|
|
Production
Environment Testing.
|
Developers,
Test Engineers.
|
Testing
of the whole computer system before rolling out to the UAT.
|
Stable
application.
|
|
User
Acceptance Testing.
|
Users.
|
Testing
of computer system to make sure it will work in the system regardless of what
the system requirements indicate.
|
Tested
and accepted system based on the user needs.
|
|
Installation
Testing.
|
Test
Engineers.
|
Testing
of the Computer System during the Installation at the user place.
|
Successfully
installed application.
|
|
Beta
Testing
|
Users.
|
Testing
of the application after the installation at the client place.
|
Successfully
installed and running application.
|
Are u looking for home based part/full time job ? click below link
No comments:
Post a Comment