|
Technical Reviews
About the purpose of techincal reviews the IEEE standard says: "The purpose of a technical review is to evaluate a software product by a team of qualified personnel to determine its suitability for its intended use and identify discrepancies from specifications and standards." In other words the technical review is a meeting in which a team analyzes a work product to see it its quality is as expected or if it needs some improvement. The standard further states that not necessarily all aspects of the review object have to be examined and that it is a possible purpose of the meeting to come up with alternatives for a better design. The list of work products for which the review can be applied is quite big: Software requirements specification , Software design description, Software test documentation, Software user documentation, Maintenance manuals, System build procedures, Installation procedures and Release notes are possible candidates for the review. The review meetings should be planned in the project plan or they can be held on request e.g. by the quality group. The roles involved in a technical review are as follows:
- Decision maker
- Review leader
- Recorder
- Technical staff
- Management staff (optional)
- Other team members (optional)
- Customer or user representative (optional)
According to the IEEE standard the input to the technical review shall include the following:
- A statement of objectives for the technical review (mandatory)
- The software product being examined (mandatory)
- Software project management plan (mandatory)
- Current anomalies or issues list for the software product (mandatory)
- Documented review procedures (mandatory)
- Relevant review reports (should)
- Any regulations, standards, guidelines, plans, and procedures against which the software product is to be examined (should)
- Anomaly categories (See IEEE Std 1044-1993 [B7]) (should)
Instead of describing the technical review procedure in words I put this into a diagram. In the following flow chart you find the steps of the review, the expected inputs i.e. work product and other documents, and a rough description of each process step in the comment boxes:
|
|