Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA07 - Supporting Assessments of Information Flow Models  

  LQS07 - Prüfungen der Informationsflußmodelle 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
    User Requirements.Actual Status and Current Analysis
    User Requirements.Description of the Functionality

    • Interface Overview
    Technical Requirements.Overall Function of Element
    Technical Requirements.Technical Requirements for the Interfaces
    System Architecture.Explanation of the Cooperation of Technical Elements

    QA4.2 - Assessment of the Content of the Product

  • Objects to be assessed
    User Requirements.Actual Status and Current Analysis
    User Requirements.Description of the Functionality

    • Interface Overview
    Technical Requirements.Overall Function of Element
    Technical Requirements.Technical Requirements for the Interfaces
    System Architecture.Explanation of the Cooperation of Technical Elements

    Method

    STAT - Static Analysis

    2 Brief Characteristics

    This service unit defines the requirements for tools used to support the assessment of data flow models and control flow models.

    3 Requirements

    3.1 Requirements for Interfaces

    SQA07.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

    SQA07.M.1 STAT - Static Analysis
    SQA07.M.1.1 DFM - Data Flow Modeling
    SQA07.M.1.1.1 Assessment of consistency
    SQA07.M.1.1.1.1 Isolated processes It is possible to list processes from data flow diagrams that are neither receiver nor sender of data flows.
    SQA07.M.1.1.1.2 Isolated terminators It is possible to list terminators from data flow diagrams that are neither receiver nor sender of data flows.
    SQA07.M.1.1.1.3 Isolated data stores It is possible to list data stores that are neither receiver nor sender of data flows.
    SQA07.M.1.1.1.4 Data flows with gaps It is possible to list data flows that are not completely defined across all hierarchy levels.
    SQA07.M.1.1.1.5 Interface consistency in connection with hierarchical structure The interfaces from one level to the next are automatically assessed with regard to consistency.
    SQA07.M.1.1.2 Utilization assessment
    SQA07.M.1.1.2.1 Unused processes It is possible to list processes not contained in any data flow diagram.
    SQA07.M.1.1.2.2 Unused terminators It is possible to list terminators not contained in any data flow diagram.
    SQA07.M.1.1.2.3 Unused data stores It is possible to list data stores not contained in any data flow diagram.
    SQA07.M.1.1.2.4 Unused data flows It is possible to list data flows not contained in any data flow diagram.
    SQA07.M.1.1.3 Assessment of conventions
    SQA07.M.1.1.3.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA07.M.1.1.3.2 Naming conventions It is possible to assess naming conventions.
    SQA07.M.1.1.3.3 Limitations It is possible to assess size and complexity limitations.
    SQA07.M.1.1.3.4 Layout conventions It is possible to assess layout conventions.
    SQA07.M.1.1.3.5 Means of representation It is possible to assess commitments to certain representation types.
    SQA07.M.1.1.4 Completeness of description It is possible to generate a list of all objects for which no descriptions exist.
    SQA07.M.1.1.5 Adaptation Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment.
    SQA07.M.1.2 CFM - Control Flow Modeling
    SQA07.M.1.2.1 Assessment of consistency
    SQA07.M.1.2.1.1 Isolated processes It is possible to list processes from control flow diagrams that are neither receiver nor sender of control flows.
    SQA07.M.1.2.1.2 Isolated terminators It is possible to list terminators from control flow diagrams that are neither receiver nor sender.
    SQA07.M.1.2.1.3 Isolated control stores It is possible to list control stores that are neither receiver nor sender of control flows.
    SQA07.M.1.2.1.4 Control flows with gaps It is possible to list control flows that are not completely defined across all hierarchy levels.
    SQA07.M.1.2.1.5 Interface consistency between hierarchies The consistency of interfaces from one level to the next one is automatically checked.
    SQA07.M.1.2.2 Utilization assessment
    SQA07.M.1.2.2.1 Unused processes It is possible to list processes not contained in any control flow diagram.
    SQA07.M.1.2.2.2 Unused terminators It is possible to list terminators not contained in any control flow diagram.
    SQA07.M.1.2.2.3 Unused control stores It is possible to list control stores not contained in any control flow diagram.
    SQA07.M.1.2.2.4 Unused control flows It is possible to list control flows not contained in any control flow diagram.
    SQA07.M.1.2.3 Assessment of conventions
    SQA07.M.1.2.3.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA07.M.1.2.3.2 Naming conventions It is possible to assess naming conventions.
    SQA07.M.1.2.3.3 Limitations It is possible to assess size and complexity limitations.
    SQA07.M.1.2.3.4 Layout conventions It is possible to assess layout conventions.
    SQA07.M.1.2.3.5 Means of representation It is possible to assess commitments to certain representation types.
    SQA07.M.1.2.4 Completeness of the description It is possible to generate a list of all objects for which no descriptions exist.
    SQA07.M.1.2.5 Adaptation Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment.

    3.3 Requirements for Functions

    SQA07.F.1 Delimitation of to the assessment It is possible to delimit size and extent of the assessment to selectable characteristics.
    SQA07.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.
    SQA07.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

    SQA07.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.
    SQA07.O.2 Complexity There is no limitation of the complexity caused by the tool itself.
    SQA07.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.
    SQA07.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).
    SQA07.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