Previous Next Methods Allocation  
4.34 Method Category "Review" (REV)  

  4.34 Methodenkategorie "Review" (REV)

Contents  
  • 1 Identification/Definition of the Method
  • 2 Brief Characteristic of the Method
  • 3 Limits of the Methods Application
  • 4 Specification of the Methods Allocation
  • 5 Interfaces
  • 6 Further Literature
  • Links to the V-Model Mailinglist

    • 1 Identification/Definition of the Method

    REV is a category of methods; the individual applicable methods are described in detail in REV - Review (in Annex 1) by listing the selection criteria. A special method is only defined within the scope of the operationalization.

    /IEEE 1028, 1988/ can be used as an overview description.

    2 Brief Characteristic of the Method

    Objective and Purpose

    The objective of a "Review" (REV) is the identification of errors and the detection of violations of specifications, standards and plans. A Review also has to show and to analyze error types for an improvement and correction of the development process.

    Operational Sequence

    Reviews utilize the human ability to think and to analyze in order to evaluate and assess complex problems.

    The basic procedures used for the individual methods of the category REV are generalized in the following.

    In all, a review consists of the following steps:

  • review planning
  • review preparation
  • review meeting

    • The review planning comprises setting up the review team, the definition of time and location of the review meeting, as well as making available the required documents (object to be assessed, assessment criteria). Normally, the review manager is responsible for the review planning.

    The preparation phase is required for the individual preparation of each team member, according to his role.

    The review meeting is headed by a review manager. Any errors detected during a review meeting, the suggested measures and recommendations, as well as the decisions made are documented. The review manager is in charge of the generation of the result documentation.

    The meeting ends with the definition of the review result. The following results are possible:

    Recommendation

    To start the preparation phase it is recommended to arrange a preparatory meeting where the review team is introduced to the object to be assessed, to the assessment criteria, and to the review procedure.

    The Pareto Diagram is a suitable means of representation for the error types and their consequences to the development process.

    3 Limits of the Methods Application

    - not applicable -

    4 Specification of the Methods Allocation

    No. Activity Description
    4.1 QA4.1 - Determination of Assessability Method REV is applied to find out if all objects to be assessed are assessable. The assessment must be realized according to specially defined assessment criteria.

    REV completely covers the assessability ascertainment. However, it is recommended to apply method STAT - Static Analysis as well in order to reduce the effort in connection with objects to be assessed that are structured according to a predefined formalism. The number of the aspects to deal with will then be considerably less.

    4.2 QA4.2 - Assessment of the Content of the Product Method REV is applied to assess the following objects: The assessment of the content must be realized in accordance with predefined assessment criteria for each object to be assessed. For the objects Integration Plan, Assessment Plan, Assessment Specification, CM Plan, Configuration Identification Document (CID), Change Order und Change Memo, REV completely covers the assessment.

    In case of objects to be assessed that are structured according to a predefined formalism (User Requirements, Technical Requirements, System Architecture, SW Architecture, SW Design (Module/Database), Implementation Documents (Implementation Document: Components Database, Modules, , SW Units), Data-Dictionary, Interface Overview and Interface Description) it is recommended to additionally apply method STAT - Static Analysis in order to reduce the effort. The number of the aspects to deal with will then be considerably less.

    For the assessed objects User Requirements, Technical Requirements, System Architecture, SW Architecture, SW Design (Module/Database), Operational Information, and Assessment Procedure the method T - Test is also required, provided the contents of the object to be assessed are structured according to a predefined formalism.

    In the case where the reliability requirements are high, the application of method SIMU - Simulation Models is also required for the objects User Requirements and Technical Requirements to be assessed.

    4.3 PM6 - Phase Review Phase reviews are usually based on previous individual assessments. Subject of a phase review is the corresponding complete baseline documentation. By means of method REV technical, economical, time, management, and risk aspects have to be evaluated within the scope of a phase review.

    Method REV completely covers activity PM6 - Phase Review.

    5 Interfaces

    - not applicable -

    6 Further Literature

    /Freedman, 1982/ Handbook of Walkthroughs, Inspections, and Technical Reviews
    /IEEE 1028, 1988/ IEEE-STD 1028-1988 - IEEE Standard for Software Reviews and Audits, 1988
    /Myers, 1991/ Methodisches Testen von Programmen
    /Wallmüller, 1990/ Software-Qualitätssicherung

    Links to the V-Model Mailinglist

    Mail 0632 - Produktstatus Projekthandbuch (632)

    Previous Next This page online  •  GDPA Online  •  Last Updated 07.Feb.2003 by C. Freericks