Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA11 - Supporting Assessments of Logical Schema Specifications  

  LQS11 - Prüfungen der logischen Schemaspezifikationen 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 (Database).Database Description
    Data-Dictionary

    QA4.2 - Assessment of the Content of the Product

  • Objects to be assessed
    SW Design (Database).Database Description
    Data-Dictionary

    Method

    STAT - Static Analysis

    2 Brief Characteristics

    This service unit defines the requirements for tools used to assess if

    3 Requirements

    3.1 Requirements for Interfaces

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

    SQA11.M.1 STAT - Static Analysis
    SQA11.M.1.1 DNAV - Data Navigation Modeling/
    LOGM - Logical DB Modeling
    SQA11.M.1.1.1 Assessment of conventions
    SQA11.M.1.1.1.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA11.M.1.1.1.2 Naming conventions It is possible to assess naming conventions.
    SQA11.M.1.1.1.3 Limitations It is possible to assess size and complexity limitations.
    SQA11.M.1.1.1.4 Layout conventions It is possible to assess layout conventions.
    SQA11.M.1.1.1.5 Means of representation It is possible to assess commitments to certain representation types.
    SQA11.M.1.1.2 Missing elements
    SQA11.M.1.1.2.1 Elements missing in logical schema specifications It is possible to list all entity types, relationship types, and attributes of the conceptual schema specification that are not integrated in logical schema specifications.
    SQA11.M.1.1.2.2 Not declared parts in logical schema specifications It is possible to list user-specific parts in logical schema specifications that are not included in the conceptual schema specifications.
    SQA11.M.1.1.3 Adoption of integrity conditions during transformations It is possible to list integrity conditions that have not been transmitted into the logical schema specification during the transformation of the conceptual schema specification.
    SQA11.M.1.1.4 Data navigation diagrams It is possible to list data navigation diagrams that have not been taken into consideration during the transformation of the conceptual schema specification into the logical schema specification.
    SQA11.M.1.1.5 Completeness of the description It is possible to generate a list of all objects for which no descriptions exist.
    SQA11.M.1.1.6 Adaptation Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment.

    3.3 Requirements for Functions

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

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