Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA16 - Ensuring Consistency of the Contractual Tailoring  

  LQS16 - Konsistenz des Ausschreibungsrelevanten Tailoring sichern

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.2 - Assessment of the Content of the Product

  • (object to be assessed
    Project Manual.Project-Specific V-Model

    • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools used to assess if a project-specific V-Model is consistent after activity and product types have been deleted from the general V-Model.

    3 Requirements

    3.1 Requirements for Interfaces

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

    none

    3.3 Requirements for Functions

    SQA16.F.1 Unnecessary activity types It is possible to assess if all activity types that do not generate or update product types have been deleted.
    A product type is generated by an activity type, i. e. if it occurs in the product flow of this activity in state "planned" on the input side, and in a different state than "planned" on the output side.
    SQA16.F.2 Unnecessary product types It is possible to assess if all product types that are not required anywhere have been deleted.
    A product type is required by an activity type if it occurs on the input side of the product flow of this activity type.
    SQA16.F.3 Activity descriptions
    SQA16.F.3.1 Activity types It is possible to check that the activity descriptions of not deleted activity types do not contain references to already deleted activity types.
    SQA16.F.3.2 Product types It is possible to check that the activity description of not deleted activity types do not contain references to already deleted product types.
    SQA16.F.4 Deletion conditions It is possible to check if all contractual deletion conditions for the project-specific V-Model have been taken into consideration.
    SQA16.F.5 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

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