2. DEFINITION OF REVIEW
A review is a systematic examination of a document by one or more
people with the main aim of finding and removing errors early in
the software development life cycle. Reviews are used to verify
documents such as requirements, system designs, code, test plans
and test cases.
4. DEFINITION OF TECHNICAL REVIEW…
A software technical review is a form of peer review in which "a team of qualified
personnel ... examines the suitability of the software product for its intended use and
identifies discrepancies from specifications and standards. Technical reviews may
also provide recommendations of alternatives and examination of various
alternatives“
During technical reviews defects are found by experts, who focus on the content of
the document.
The experts that are needed for a technical review are:
architects
chief designers
key users.
In practice, technical reviews vary from quite informal to very formal
5. DEFINITION OF TECHNICAL REVIEW
A Technical review is a static white-box testing technique which is
conducted to spot the defects early in the life cycle that cannot be
detected by black box testing techniques.
It is formal review but less formal than inspection.
It is led by moderator.
Technical review focuses on technical content of the document.
Reviewers are generically architects, designers etc.
Generally involves peer review with no management.
6. TECHNICAL REVIEW
Structured encounter in which a group of technical personnel analyze a
work product with the following primary objectives:
improve the original quality of the work product
improve the quality of the review process
7. TECHNICAL REVIEW
Technical Review
• Implications
• More preparation time
• Less material per meeting
• Product must stand or fall on its own
8. WHY WE HOLD TECHNICAL REVIEW
Software Development is a very error-prone process.
Early detection of defects is cost effective, and peer reviews find errors
early.
Peer reviews find many of the same errors as testing, but earlier and
with less effort.
They serve to educate the participants and provide training
They raise a team’s core competence by setting standards of excellence
9. TOOLS FOR TECHNICAL REVIEW
Various tools for different inspection methods.
ICICLE – for inspection of C & C++ programs
Scrutiny & InspeQ for specific inspection processes
ASSIST –supports generic inspection process
For larger list, see:
Home grown tools
Typically built with Access Database.
Reviewer enters defects offline into database.
Eliminates recorder and reader roles.
Gives author time to consider defects before meeting
10. GOALS OF A TECHNICAL REVIEW
Assess the value of technical concepts and alternatives in the product
and project environment;
Establish consistency in the use and representation of technical
concepts;
Ensure, at an early stage, that technical concepts are used correctly;
Inform participants of the technical content of the document.
11. TECHNICAL REVIEW CHARACTERISTICS:
Technical Reviews are documented and uses a defect detection
process that has peers and technical specialist as part of the review
process.
The Review process doesn't involve management participation.
It is usually led by trained moderator who is NOT the author.
The report is prepared with the list of issues that needs to be
addressed.
12. OBJECTIVES OF TECHNICAL REVIEW
To uncover errors in function, logic, or implementation for any
representation of the software.
To verify that the software under review meets its requirements.
To ensure that the software has been represented according to
predefined standards.
To achieve software that is developed in a uniform manner.
To make projects more manageable.
