|SQA19 - Supporting Assessments of Project Realization Plans|
LQS19 - Prüfungen der Projektablaufpläne unterstützen
|SQA19.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.|
|SQA19.F.1||Instantiation of activities||It is possible to check if all project-specifically selected activity types are actually instantiated.|
It is possible to check if the instantiated activities correspond to the activity types of the Project Manual.|
Activities with regard to deleted activity types must not exist.
|SQA19.F.3||Initial delay||It is possible to list the initial delays of activities.|
|SQA19.F.4||End delay||It is possible to list the end delays of activities.|
It is possible to signal resource conflicts.|
Resource conflicts occur after an overload of resources with regard to time (e. g. the time schedule for a staff member is far from realistic).
|SQA19.F.6||Negative float time||
It is possible to signal negative float times.|
Negative float times occur if the deadline for the latest possible end of an activity is set prior to the planned end of that activity.
|SQA19.F.7||Cycles in the network plan||
It is possible to signal cycles in the network plan.|
Cyclic dependencies between the activities of a network plan refer to planning errors.
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.
|SQA19.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.|
|SQA19.O.2||Complexity||There is no limitation of the complexity caused by the tool itself.|
|SQA19.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.|
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).
|SQA19.O.5||Invariance||Applying the tool does not change the object to be assessed.|
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|