Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA01 - Supporting Assessments of Requirements  

  LQS01 - Prüfungen der Anforderungen 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
    (for User Requirements and Technical Requirements
  • QA4.2 - Assessment of the Content of the Product

  • Objects to be assessed
    (for User Requirements and Technical Requirements
  • Method

    STAT - Static Analysis

    2 Brief Characteristics

    This service unit defines the requirements for tools used to support the quality assurance for the following products: The above listed products are assessed with regard to consistency and completeness.

    3 Requirements

    3.1 Requirements for Interfaces

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

    SQA01.M.1 STAT - Static Analysis
    SQA01.M.1.1 Formalized requirement descriptions It is possible to assess the requirement descriptions to find out if they follow a preset formalism.
    SQA01.M.1.2 Assessment of conventions
    SQA01.M.1.2.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA01.M.1.2.2 Naming conventions It is possible to assess naming conventions.
    SQA01.M.1.2.3 Limitations It is possible to assess size and complexity limitations.
    SQA01.M.1.2.4 Layout conventions It is possible to assess layout conventions.
    SQA01.M.1.2.5 Means of representation It is possible to assess commitments to certain representation types.
    SQA01.M.1.3 Requirements allocation
    SQA01.M.1.3.1 Allocation object It is possible to assess if each requirement has been allocated to a subsystem, a DP segment, a software configuration item, an interface, or the development and maintenance environment.
    SQA01.M.1.3.2 Already allocated It is possible to display already allocated requirements.
    SQA01.M.1.3.3 Not yet allocated It is possible to display not yet allocated requirements.
    SQA01.M.1.3.4 Assessment of origin It is possible to assess the origin of all requirements.
    It has to be possible to assess, if the requirement is derived from requirements of a higher level, if the requirement is a post-requirement, etc.
    SQA01.M.1.4 Adaptation Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment.

    3.3 Requirements for Functions

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

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