Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA10 - Supporting Assessments of Component and Module Specifications  

  LQS10 - Prüfungen der Spezifikationen von Komponenten und Modulen unterstützen

Contents  
  • 1 Allocation to V-Model and Methods Allocation
  • 2 Brief Characteristics
  • 3 Requirements
  •       3.1 Requirements for Interfaces
  •       3.2 Requirements for the Methods Support
  •       3.3 Requirements for Functions
  •       3.4 Other Requirements
  • 1 Allocation to V-Model and Methods Allocation

    V-Model

    QA4.1 - Determination of Assessability

  • Objects to be assessed
    SW Design (Module).SW Component/SW Module Description

    QA4.2 - Assessment of the Content of the Product

  • Objects to be assessed
    SW Design (Module).SW Component/SW Module Description

    Method

    STAT - Static Analysis

    2 Brief Characteristics

    This service unit defines the requirements for tools used to support the assessment of Components and Modules.

    3 Requirements

    3.1 Requirements for Interfaces

    SQA10.I.1 Granularity The exchange of control parameters with SWFM01 - Workflow Management is possible for individual closed function packages of the tool by means of a disclosed, documented interface.

    3.2 Requirements for the Methods Support

    SQA10.M.1 STAT - Static Analysis
    SQA10.M.1.1 PCODE - Pseudocode
    SQA10.M.1.1.1 Assessment of Consistency
    SQA10.M.1.1.1.1 Consistency assessment of data elements from data declarations
    SQA10.M.1.1.1.1.1 Unused data elements It is possible to list data elements not utilized by any statement.
    SQA10.M.1.1.1.1.2 Not initialized data elements It is possible to list data elements that are not initialized.
    SQA10.M.1.1.1.1.3 Not declared data elements It is possible to list data elements that are not explicitly declared.
    SQA10.M.1.1.1.1.4 Non-integer index data elements It is possible to list index data elements not defined as integers.
    SQA10.M.1.1.1.1.5 Similar data element names It is possible to list data elements having similar names.
    SQA10.M.1.1.1.2 Assessment of consistency for calculation statements
    SQA10.M.1.1.1.2.1 Non-arithmetic data elements It is possible to list calculation statements utilizing non-arithmetic data elements.
    SQA10.M.1.1.1.2.2 Different data types It is possible to list calculation statements utilizing data elements with different data types.
    SQA10.M.1.1.1.2.3 Different data element lengths It is possible to list calculation statements utilizing data elements having the same data type but different length definitions.
    SQA10.M.1.1.1.3 Assessment of consistency for assignment statements
    SQA10.M.1.1.1.3.1 Different data types It is possible to list assignment statements in which data elements with different data types are used.
    SQA10.M.1.1.1.3.2 Different data element lengths It is possible to list assignment statements in which data elements with the same data type but different length definitions are used.
    SQA10.M.1.1.1.4 Assessment of consistency for comparison statements
    SQA10.M.1.1.1.4.1 Different data types It is possible to list comparison statements in which data elements are used having different data types.
    SQA10.M.1.1.1.4.2 Different data element lengths It is possible to list comparison statements in which data elements are used having the same data type but different length definitions.
    SQA10.M.1.1.1.5 Assessment of consistency for control structures
    SQA10.M.1.1.1.5.1 Syntax check It is possible to check the syntax of statements automatically.
    SQA10.M.1.1.1.5.2 Undesired control structures It is possible to list the use of undesired control structures.
    Undesired control structures may be unconditioned "Go To" statements or dynamic program switch statements like "Alter" in COBOL.
    SQA10.M.1.1.1.6 Assessment of interface consistency
    SQA10.M.1.1.1.6.1 Number of parameters It is possible to list both the calling and the called Components or Modules where the number of parameters does not match.
    SQA10.M.1.1.1.6.2 Parameter characteristics
    SQA10.M.1.1.1.6.2.1 Different data types It is possible to list both the calling and the called Components or Modules where the parameters were defined with different data types.
    SQA10.M.1.1.1.6.2.2 Different lengths It is possible to list both the calling and the called Components or Modules where the parameters were defined with different lengths.
    SQA10.M.1.1.1.6.2.3 Parameter utilization It is possible to list both the calling and the called Components or Modules where the parameters were not utilized.
    SQA10.M.1.1.1.7 Assessment of data access consistency
    SQA10.M.1.1.1.7.1 Closing files It is possible to list files that have not been closed prior to ending the component or module process.
    SQA10.M.1.1.1.7.2 Parameter in CALL statements It is possible to list CALL statements in modules where the type or the number of the CALL parameters does not correspond to the predefined rules.
    SQA10.M.1.1.2 Statistics
    SQA10.M.1.1.2.1 Control structures It is possible to find out how often certain control structures (including interrupt and call statements) have been utilized in a Component or Module.
    SQA10.M.1.1.2.2 Maximum nesting level It is possible to find out the maximum nesting level of control structures in a Component or Module.
    SQA10.M.1.1.2.3 File/database access It is possible to list type, number, and execution time of file and database accesses for individual modules.
    SQA10.M.1.1.3 Structure analysis
    SQA10.M.1.1.3.1 Call hierarchy It is possible to illustrate the hierarchy of calls between Components or Modules.
    SQA10.M.1.1.3.2 Component/module structure It is possible to illustrate the internal structure of Components or Modules.
    In this case, the term Internal Structure of Components and Modules refers to the nesting of closed parts in a specification (internal procedures, functions, packages).
    SQA10.M.1.1.4 Complexity measurements It is possible to find out the complexity within a Component or Modules.
    Common approaches to measure software complexity are those by McCabe or by Halstead.
    SQA10.M.1.1.5 Conformity with standards It is possible to assess if (project) standards (SAA, CUA, Style Guides), when generating masks, are being met.
    SQA10.M.1.1.6 Assessment of conventions
    SQA10.M.1.1.6.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA10.M.1.1.6.2 Naming conventions It is possible to assess naming conventions.
    SQA10.M.1.1.6.3 Limitations It is possible to assess size and complexity limitations.
    SQA10.M.1.1.6.4 Layout conventions It is possible to assess layout conventions.
    SQA10.M.1.1.6.5 Means of representation It is possible to assess commitments to certain representation types.
    SQA10.M.1.1.7 Adaptation Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment.
    SQA10.M.1.1.8 Positioning in case of consistency problems Based on the listings about discovered consistency problems, positioning at the exact position in question within the specification is possible.
    SQA10.M.1.1.9 Completeness of the description It is possible to generate a list of all objects for which no descriptions exist.

    3.3 Requirements for Functions

    SQA10.F.1 Delimitation of to the assessment It is possible to delimit size and extent of the assessment to selectable characteristics.
    Examples for selectable characteristics are consistency checks of data elements, computations, assignment and comparison statements, determination of complexity, usage of language features and comments..
    SQA10.F.2 Procedural language By means of a procedural language it is possible to check other individual assessment criteria.
    A procedural language offers an automatic assessment of further individual assessment criteria.
    SQA10.F.3 Logging It is possible to get the results of the assessment logged.
    In this case, "logging" refers to a protocol of all data that might be utilized for later documentation of the assessment (e. g. test cases, expected results, actual results, messages) and not, however, to an editing of the documentation in the sense of actual assessment protocols.

    3.4 Other Requirements

    SQA10.O.1 Procedural command language The tool has a procedural command language that can be applied by the user to generate and run macros or procedures.
    SQA10.O.2 Complexity There is no limitation of the complexity caused by the tool itself.
    SQA10.O.3 Background Assessments run in the background mode unless an assessment in the foreground mode has been explicitly requested. Since an assessment may take some time it is not necessary to wait for the end of the processing when in the background mode, i. e. other tasks can be realized in the meantime.
    SQA10.O.4 End signal The end of an assessment is signaled.
    This signal may be acoustic (e. g. by means of a beep) or optic (e. g. by means of a special window with a corresponding message).
    SQA10.O.5 Invariance Applying the tool does not change the object to be assessed.

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