Previous Next Methods Allocation  
4.38 Elementary Method "Static Analysis" (STAT)  

  4.38 Elementarmethode "Statische Analyse" (STAT)

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
  • 7 Functional Tool Requirements
  • 1 Identification/Definition of the Method

    /Wallmüller, 1990/ chap. 4, pp. 162-163, Static Analysis
    /ISO 9126, 1991/ chap. 4, Definition of Quality Characteristics

    2 Brief Characteristic of the Method

    Objective and Purpose

    One of the objectives of the "Static Analysis" (STAT) is the identification of existing errors or respectively of error-prone situations. Another objective is to make quality measurable. Thus the method contributes its share to meet the basis requirement that it must be possible to prove quality.

    Operational Sequence

    The basic principle of the static analysis is that an object to be assessed which is structured according to a predefined formalism will be read. In this connection errors or error-prone situations are immediately detected or information is gained which allow deductions to errors or respectively error-prone situations after the read process has been completed.

    Errors or error-prone situations might be:

    Metrics are also quantified during the read process. The metrics offer a possibility to measure quality characteristics. However, it must also be evaluated if the measured values are meeting the requirements /ISO 9126, 1991/). An overview of all possible metrics can be found in /IEEE 982.2/.

    3 Limits of the Methods Application

    The static analysis can only be applied for formalized objects to be assessed. Furthermore, the application of the static analysis is only recommended when supported by the appropriate tools.

    4 Specification of the Methods Allocation

    No. Activity Description
    4.1 QA4.1 - Determination of Assessability Method STAT is applied to determine the assessability of objects that are structured according to a predefined formalism. It only completely covers the determination of the assessability in combination with method REV - Review. However, after the realization of a static analysis the number of aspects to be taken into consideration during the review will be much less.
    4.2 QA4.2 - Assessment of the Content of the Product Method STAT is applied to assess the following objects: For the listed objects to be assessed, STAT only completely covers the assessment in combination with other methods. The additional application of method REV - Review is required for all objects to be assessed. However, after the realization of a static analysis the number of aspects to be taken into consideration during the review will be much less.

    In case some of the contents of the object to be assessed are structured according to a predefined formalism, the application of method T is additionally required for the objects User Requirements, Technical Requirements, System Architecture, SW Architecture, and SW Design (Module/Database).

    If the reliability requirements are high, the application of method SIMU - Simulation Models is additionally required for the assessed objects User Requirements and Technical Requirements.

    5 Interfaces

    - not applicable -

    6 Further Literature

    /IEEE 982.2/ IEEE-STD 982.2-1988 - IEEE Guide for the Use of IEEE Standard Dictionary of Measures to Produce Reliable Software, 1988
    /ISO 9126, 1991/ Information Technology, Software Product Evaluation, Quality, Characteristics and Guidelines for their Use
    /Myers, 1991/ Methodisches Testen von Programmen
    /Reynolds, 1976/ Induction as the Basis for Program Verification
    /Sneed, 1988/ Software-Qualitätssicherung
    /Wallmüller, 1990/ Software-Qualitätssicherung
    /Yeh, 1977/ Verification of Programs by Predicate Transformation

    7 Functional Tool Requirements

    SQA01 - Supporting Assessments of Requirements
    SQA02 - Supporting Assessments of User Interfaces
    SQA03 - Supporting Assessments of Architecture
    SQA04 - Supporting Assessments of Process Models
    SQA05 - Supporting Assessments of Function Structures
    SQA06 - Supporting Assessments of Function Specifications
    SQA07 - Supporting Assessments of Information Flow Models
    SQA08 - Supporting Assessments of Dynamic Models
    SQA09 - Supporting Assessments of Information Structures
    SQA10 - Supporting Assessments of Component and Module Specifications
    SQA11 - Supporting Assessments of Logical Schema Specifications
    SQA12 - Static Assessment of Code
    SQA13 - Static Assessment of Texts (no Code)

    Previous Next GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster