Formal Review generally takes place in piecemeal approach that consists of six different steps that are essential. Formal review generally obeys formal process. It is also one of the most important and essential techniques required in static testing.
Six steps are extremely essential as they allow team of developers simply to ensure and check software quality, efficiency, and effectiveness. These steps are given below :
- Planning :
For specific review, review process generally begins with ‘request for review’ simply by author to moderator or inspection leader. Individual participants, according to their understanding of document and role, simply identify and determine defects, questions, and comments. Moderator also performs entry checks and even considers exit criteria.
- Kick-Off :
Getting everybody on the same page regarding document under review is the main goal and aim of this meeting. Even entry result and exit criteria are also discussed in this meeting. It is basically an optional step. It also provides better understanding of team about relationship among document under review and other documents. During kick-off, Distribution of document under review, source documents, and all other related documentation can also be done.
- Preparation :
In preparation phase, participants simply work individually on document under review with the help of related documents, procedures, rules, and provided checklists. Spelling mistakes are also recorded on document under review but not mentioned during meeting.
These reviewers generally identify and determine and also check for any defect, issue or error and offer their comments, that later combined and recorded with the assistance of logging form, while reviewing document.
- Review Meeting :
This phase generally involves three different phases i.e. logging, discussion, and decision. Different tasks are simply related to document under review is performed.
- Rework :
Author basically improves document that is under review based on the defects that are detected and improvements being suggested in review meeting. Document needs to be reworked if total number of defects that are found are more than an unexpected level. Changes that are done to document must be easy to determine during follow-up, therefore author needs to indicate changes are made.
- Follow-Up :
Generally, after rework, moderator must ensure that all satisfactory actions need to be taken on all logged defects, improvement suggestions, and change requests. Moderator simply makes sure that whether author has taken care of all defects or not. In order to control, handle, and optimize review process, moderator collects number of measurements at every step of process. Examples of measurements include total number of defects that are found, total number of defects that are found per page, overall review effort, etc.