Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA02 - Supporting Assessments of User Interfaces  

  LQS02 - Prüfungen der Nutzerschnittstellen 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 Technical Requirements.Technical Requirements for the User Interface and Interface Description).
  • QA4.2 - Assessment of the Content of the Product

  • Objects to be assessed
    (for Technical Requirements.Technical Requirements for the User Interface and Interface Description).
  • Method

    STAT - Static Analysis

    2 Brief Characteristics

    This service unit defines the requirements for tools used to assess if all the contents and user elements of the user interfaces have been described. The structure of the user dialog is assessed as well.

    3 Requirements

    3.1 Requirements for Interfaces

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

    SQA02.M.1 STAT - Static Analysis
    SQA02.M.1.1 DIAL - Dialog Design Modeling
    SQA02.M.1.1.1 Screen mask types It is possible to list which screen mask types relevant for a planned user dialog cannot be found in dialog diagrams.
    SQA02.M.1.1.2 Transition events It is possible to list the transitions from one mask type to another where the transition event (trigger) is not specified in the dialog diagram.
    SQA02.M.1.1.3 Assessment of conventions
    SQA02.M.1.1.3.1 Project standards It is possible to define the conventions to be assessed with regard to individual projects.
    SQA02.M.1.1.3.2 Naming conventions It is possible to assess naming conventions.
    SQA02.M.1.1.3.3 Limitations It is possible to assess size and complexity limitations.
    SQA02.M.1.1.3.4 Layout conventions It is possible to assess layout conventions.
    SQA02.M.1.1.3.5 Means of representation It is possible to assess commitments to certain representation types.

    3.3 Requirements for Functions

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

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