Previous Next Functional Tool Requirements Homepage  
Quality Assurance Submodel  
SQA17 - Supporting Assessments of Project Resource Management  

  LQS17 - Prüfungen der Projektressourcenverwaltung 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.2 - Assessment of the Content of the Product

  • (object to be assessed
    Project Plan.Resource Plan)
  • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools used to assess

    3 Requirements

    3.1 Requirements for Interfaces

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

    SQA17.F.1 Not initialized calendars It is possible to list all resources having a not initialized calendar.
    SQA17.F.2 Not initialized scales of charges It is possible to list all resources having not initialized scales of charges.
    SQA17.F.3 V-Model roles It is possible to check if all roles of the V-Model mentioned in the Project Manual have been allocated to staff members.
    SQA17.F.4 Allocation of roles It is possible to check if a V-Model role has been allocated to every staff member of the project.
    SQA17.F.5 Allocation of activities It is possible to check if a Work Order has been allocated to every staff member of the project.
    SQA17.F.6 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

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