Review is done earliest in SDLC Review is systematic examination of document to find and remove defects.Reviews is used to documents such requirements specifications, system designs, code, test, plans and test case.
Review for a test design doc or tdd checks for spellings ,format ,accuracy and coverage of functional requirements in it.
Types of defects found by reviews
Deviations from Standards
Requirements are ambiguous or missing
Design Defects-Design does not match req
Insufficient maintainability-Code is complex to maintain
Basic Review Process
Doc under review is studies by reviewer.
Reviewer identifies issues or problems and informs author either verbally or in documented form.
Author decides on any action to take in response to comments and updates accordingly.
Activities in a formal review-12 vvvimp steps-PDEEKECIPNIRMDDERFEC
Planning-Reviewer is selected. He can be expericined or un experienced, someone outside the company etc. Each reviewer is provided a role to provide them with a unique focus on document under review.
Defining entry and exit criteria-
Used for most formal review like inspection-
Entry criteria-To define the entry criteria to define review. Example doc needs to be ready to start the review etc.
Exit Criteria-When to stop the review.
Kick off-Distribute docs to all persons involved in the review process, explain objectives and role of persons involved. Can be done through meeting or just sending an email.
Entry Criteria-Entry Criteria is met here.
Individual preparation-Work done by each individual before the meeting like source documents, noting potential defects, questions ,comments etc.
Noting incidents-Potential defects,questions,comments are logged.
Review meeting-Discussions regarding defects found
Examine-Recording of physical meeting
Rework-Correcting the defects is called rework
Follow up-Review leader will check if the agreed defects have been addressed
Checking exit criteria-Exit criteria defined at start if process is checked to ensure that exit criteria is met.