A Technical Review (also known asa peer review), is considered to be aformal review type, even though noManagers are expected to attend. Itinvolves a structured encounter, inwhich a peer/s analyse the workwith a view to improve the quality of the original work.
Ideally led by the Moderator
Attended by peers /technical experts
Documentation is required
No Management presence
Solving technical problemsA walkthrough is a set of proceduresand techniques designed for a peer group, lead by the author to reviewsoftware code. It is considered to bea fairly informal type of review. Thewalkthrough takes the form ameeting, normally between one andtwo hours in length.
Led by the Author
Attended by a peer group
Varying level of formality
Defect findingAn inspection is a formal type of review. It requires preparation onthe part the review team membersbefore the inspection meeting takesplace. A follow-up stage is also arequirement of the inspection. Thisensures that any re-working iscarried out correctly.
Led by a Moderator
Attended by specified roles
Metrics are included
Entry and Exit Criteria
Defect findingAn informal review is an extremelypopular choice early on in thedevelopment lifecycle of bothsoftware and documentation. Thereview is commonly performed bypeer or someone with relevantexperience, and should be informaland brief.
No formal process
No documentation required
Widely used reviewSoftware Validation and Verificationcan involve analysis, reviewing,demonstrating or testing of allsoftware developments. This willinclude the development processand the development product itself.Verification and Validation isnormally carried out at the end of the development lifecycle (after allsoftware developing is complete).But it can also be performed muchearlier on in the developmentlifecycle by simply using reviews.Validation involves the actualtesting. This should take place after verification phase has beencompleted.Validation:
confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use have been fulfilled.
Validation: Are we building the rightproduct?Verification would normally involvemeetings and reviews and toevaluate the documents, plans,requirements and specifications.This can be achieved by usingreviews and meetings etc.Verification:
confirmation by examination and provision of objective evidence that specified requirements have been fulfilled.
Verification: Are we building theproduct right?The Waterfall model is also knownas the ‘Sequential model’. Eachstage follows on from the previousone. The testing is performed in‘block’ as the last stage.Planning or Test creation is notconsidered until the actual softwarecode has been written. This canresult in problems being found muchlater in the project lifecycle than isdesirable.
Walkthrough ReviewTechnical ReviewInspection
V & VValidationVerificationWaterfall Model