Software Inspection Procedure

Overview
Our Software Inspections purpose it to first reveal defects before unit testing and
second to ensure that coding standards are followed. The Inspection will be characterized
by three different phases. Preparation is the phase in which all members of the inspection
prepare for the inspection by viewing the work product to be inspected. Inspection is the
phase in which all members review the product and report or find defects. Documentation is
the phase in which all the defects are compiled into a document and the document is made
available to those who's access to it would be beneficial.

Preparation
A member of an inspection is expected to spent about an hour previewing the work product
to be inspected prior to the Inspection. The preview is required to fulfill the following
tacks during their preview.

1)Mental White Box Testing: The reviewer is to mentally walk through the code
testing boundary conditions an other white box testing
Techniques. Any defects that he finds he is to document
on a his Preparation sheet(no specific format for
the Preparation sheet)

2)Coding Standard Checking: The reviewer is to check the code to make sure that the
coding standard has obeyed. Any omissions in the coding
standard the reviewer is to document on his Preparation sheet

3)Maintainability Checking: The reviewer is to look over the code documentation. He is
to check that all the necessary documentation is present. He
is also required to check that all the documentation is clear.
Any problems the reviewer finds he is to document on his
Preparation sheet.

Inspection
The inspection phase will include at least three members. First the author is to be present at the
inspection. Second the reviewer is to be at the inspection, otherwise the inspection would be
rather pointless. Third there needs to be a person to serve as moderator and secretary. The
secretary is to maintain a Inspection document. In this inspection document the secretary is to
record all issues bought up, by the reviewer, author, and/or secretary. The secretary is to also to
record the final result of the issue that is brought up. This final result is NOT to
include a solution. An inspection is not to propose a solution to an issue but rather simply point
out the existence of an issue. The final result can include whether an issue was accepted or
denied. It may also be a revision of the issue. At the end of the inspection the members of
the inspection are to write an Inspection summary of the work product and state whether the product
it ready be base-lined or not.

Documentation
All the documents of the inspection is to be turned in to the Quality Assurance Manager(QA). The
documents are the Preparation sheet by all participants of the inspection, the Inspection document
and the Inspection summary. The QA will compile them into a single document and make the available
on the website at the Software Inspection Report link.