Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA09 - Supporting Assessments of Information Structures  

  LQS09 - Prüfungen der Informationsstrukturen 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

  • System Architecture.Requirements Allocation
    Technical Requirements.Technical Requirements for the Interfaces
    SW Design (Database).Database Description
    Data-Dictionary

    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

  • System Architecture.Requirements Allocation
    Technical Requirements.Technical Requirements for the Interfaces
    SW Design (Database).Database Description
    Data-Dictionary

    Method

    STAT - Static Analysis

    2 Brief Characteristics

    This service unit defines the requirements for tools used to support the assessment of information structures.

    3 Requirements

    3.1 Requirements for Interfaces

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

    SQA09.M.1 STAT - Static Analysis
    SQA09.M.1.1 ER - E/R Modeling
    SQA09.M.1.1.1 Consistency Check
    SQA09.M.1.1.1.1 Entity types and functions It is possible to list the entity types existing in the E/R models of the incoming and outgoing data flows of a process but not in the E/R model of the process.
    SQA09.M.1.1.1.2 Attributes and functions It is possible to list the attributes existing in E/R models of incoming and outgoing data flows of a process but not in the E/R model of the process.
    SQA09.M.1.1.1.3 Entity types and data store It is possible to list the entity types existing in E/R models of incoming and outgoing data flows of a data store but not in the E/R model of the data store.
    SQA09.M.1.1.1.4 Attributes and data store It is possible to list the attributes existing in E/R models of incoming and outgoing data flows of a data store but not in the E/R model of a data store.
    SQA09.M.1.1.1.5 Entity types with the same primary keys It is possible to list entity types with the same primary key.
    All attributes depending on a key should be combined in an entity.
    SQA09.M.1.1.1.6 Attributes with the same name It is possible to list attributes having the same name in different entity types.
    Attributes with the same name can refer to redundantly defined attributes.
    SQA09.M.1.1.1.7 Aggregations and specializations
    SQA09.M.1.1.1.7.1 Matching attributes in entity subtypes and its corresponding supertype It is possible to list entity subtypes the attributes of which do not differ from its supertype.
    If the attributes are the same, the entity subtype and its supertype are identical.
    SQA09.M.1.1.1.7.2 Matching attributes in several entity subtypes It is possible to receive information about matching attributes in several entity subtypes.
    Matching attributes in several entity subtypes may point out that the attribute should be entered in the supertype.
    SQA09.M.1.1.1.7.3 Matching relationships in several entity subtypes It is possible to receive information about matching relationships in several entity subtypes.
    Matching relationships in several entity subtypes may point out that the relationship should be entered in the supertype.
    SQA09.M.1.1.1.7.4 Single entity subtypes It is possible to list entity type hierarchies consisting of only one entity subtype.
    An entity type hierarchy that only consists of one entity subtype may be incomplete or incorrect.
    SQA09.M.1.1.1.8 Assessment of redundancy It is possible to list several 1:N relationships between two entity types.
    Several 1:N relationships between two entity types can point to the fact that a relationship is redundant.
    SQA09.M.1.1.1.9 Assessment with regard to 1:1 relationships It is possible to list 1:1 relationships between two entity types.
    1:1 relationships between two entity types can point to the fact that the two entity types ought to be combined.
    SQA09.M.1.1.1.10 Isolated entity types
    SQA09.M.1.1.1.10.1 Overall model It is possible to list entity types existing in the overall model but not existing in any of the partial data models.
    SQA09.M.1.1.1.10.2 Partial model It is possible to list entity types to which no relationships are allocated.
    SQA09.M.1.1.2 Assessment of conventions
    SQA09.M.1.1.2.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA09.M.1.1.2.2 Naming conventions It is possible to assess naming conventions.
    SQA09.M.1.1.2.3 Limitations It is possible to assess size and complexity limitations.
    SQA09.M.1.1.2.4 Layout conventions It is possible to assess layout conventions.
    SQA09.M.1.1.2.5 Means of representation It is possible to assess commitments to certain representation types.
    SQA09.M.1.1.3 Assessment of Completeness
    SQA09.M.1.1.3.1 Missing data type It is possible to list attributes to which no data type has been allocated.
    SQA09.M.1.1.3.2 Missing range It is possible to list attributes to which no value range has been allocated.
    SQA09.M.1.1.3.3 Missing attributes It is possible to list entity types to which no attributes have been allocated.
    SQA09.M.1.1.3.4 Missing keys It is possible to list entity types to which no key has been allocated.
    SQA09.M.1.1.4 Completeness of the description It is possible to generate a list of all objects for which no descriptions exist.
    SQA09.M.1.1.5 Adaptation Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment.
    SQA09.M.1.2 ELH - Entity Life History
    SQA09.M.1.2.1 Assessment of completeness
    SQA09.M.1.2.1.1 Missing state diagrams It is possible to list all entity types to which no state diagram has been allocated.
    SQA09.M.1.2.1.2 Missing state changing events It is possible to list all state changes to which no state changing event has been allocated.
    SQA09.M.1.2.1.3 Missing integrity conditions It is possible to list all entity types together with the corresponding state changes for which no integrity conditions have been entered.
    SQA09.M.1.2.2 Assessment of conventions
    SQA09.M.1.2.2.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA09.M.1.2.2.2 Naming conventions It is possible to assess naming conventions.
    SQA09.M.1.2.2.3 Limitations It is possible to assess size and complexity limitations.
    SQA09.M.1.2.2.4 Layout conventions It is possible to assess layout conventions.
    SQA09.M.1.2.2.5 Means of representation It is possible to assess commitments to certain representation types.
    SQA09.M.1.2.3 Completeness of description It is possible to generate a list of all objects for which no descriptions exist.
    SQA09.M.1.2.4 Adaptation Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment.
    SQA09.M.1.3 NORM - Normalization
    SQA09.M.1.3.1 Assessment of consistency
    SQA09.M.1.3.1.1 First normal form It is possible to list the non-key attributes that are not functionally dependent on the key.
    SQA09.M.1.3.1.2 Second normal form It is possible to list the non-key attributes that are functionally dependent on a subkey.
    SQA09.M.1.3.1.3 Third normal form It is possible to list the non-key attributes that are transitively dependent on each other.
    SQA09.M.1.3.2 Assessment of conventions
    SQA09.M.1.3.2.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA09.M.1.3.2.2 Naming conventions It is possible to assess naming conventions.
    SQA09.M.1.3.2.3 Limitations It is possible to assess size and complexity limitations.
    SQA09.M.1.3.2.4 Layout conventions It is possible to assess layout conventions.
    SQA09.M.1.3.2.5 Means of representation It is possible to assess commitments to certain representation types.

    3.3 Requirements for Functions

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

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