 |
 |
 |
|
 |
|||
| SQA08 - Supporting Assessments of Dynamic Models |
LQS08 - Prüfungen der Ablaufmodelle unterstützen
1 Allocation to V-Model and Methods Allocation
V-Model
QA4.1 - Determination of Assessability
User Requirements.Description of the Functionality
System Architecture.Explanation of the Cooperation of Technical Elements
Technical Requirements.Overall Function of Element
QA4.2 - Assessment of the Content of the Product
User Requirements.Description of the Functionality
System Architecture.Explanation of the Cooperation of Technical Elements
Technical Requirements.Overall Function of Element
Method
2 Brief Characteristics
This service unit defines the requirements for tools used to assess-among other things-if all events, states, conditions, and functions are included in the sequence models and if they have been correctly allocated.
3 Requirements
3.1 Requirements for Interfaces
| SQA08.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
| SQA08.M.1 | STAT - Static Analysis | |
| SQA08.M.1.1 | FNET - Function Net Modeling | |
| SQA08.M.1.1.1 | Assessment of conventions | |
| SQA08.M.1.1.1.1 | Project standards | It is possible to define the conventions to be assessed with regard to individual projects. |
| SQA08.M.1.1.1.2 | Naming conventions | It is possible to assess naming conventions. |
| SQA08.M.1.1.1.3 | Limitations | It is possible to assess size and complexity limitations. |
| SQA08.M.1.1.1.4 | Layout conventions | It is possible to assess layout conventions. |
| SQA08.M.1.1.1.5 | Means of representation | It is possible to assess commitments to certain representation types. |
| SQA08.M.1.1.2 | Interface consistency in connection with hierarchical structure | The interfaces from one level to the next are automatically assessed with regard to consistency. |
| SQA08.M.1.1.3 | Interface consistency in connection with submodel generation | The interfaces from one submodel to the next are automatically assessed with regard to consistency. |
| SQA08.M.1.1.4 | Assessment of consistency | |
| SQA08.M.1.1.4.1 | Completeness of the function tree | It is possible to list all functions that are used in the function net but that are not defined in the static function tree. |
| SQA08.M.1.1.4.2 | Unused elementary functions | It is possible to list all elementary functions that are not used in any of the function nets. |
| SQA08.M.1.1.4.3 | Conditions for elementary functions | It is possible to list all elementary functions for which no conditions are defined. |
| SQA08.M.1.1.4.4 | Initial condition | It is possible to list all sequences that do not begin with a date or time condition. |
| SQA08.M.1.1.4.5 | End condition | It is possible to list all sequences that do not end with a data condition. |
| SQA08.M.1.1.5 | Completeness of the description |
It is possible to generate a list of all objects for which no descriptions exist. These objects may be functions, conditions, triggers, and distributors. |
| SQA08.M.1.1.6 | Adaptation | Individually adapted forms of representation for the object to be assessed are taken into consideration during the assessment. |
| SQA08.M.1.2 | SBM - System Behavior Models | |
| SQA08.M.1.2.1 | Petri Nets | |
| SQA08.M.1.2.1.1 | Capacity | It is possible to assess if the capacity of the channels in a net with an initial marking is not exceeded in all the following markings. |
| SQA08.M.1.2.1.2 | Keeping the tokens | It is possible to assess if the number of tokens in a net with an initial marking remains constant in all the following markings. |
| SQA08.M.1.2.1.3 | Possibility to activate | It is possible to assess if all instances in a net with an initial marking can be activated. |
| SQA08.M.1.2.1.4 | Free of deadlocks | It is possible to assess if in a net with a given initial marking at least one instance exists in each following marking that is able to switch. |
| SQA08.M.1.2.1.5 | Reachability | It is possible to assess if a given follow-up marking can be reached in a net with a given initial marking. |
| SQA08.M.1.2.1.6 | Assessment of conventions | |
| SQA08.M.1.2.1.6.1 | Project standards | It is possible to define the conventions to be assessed with regard to individual projects. |
| SQA08.M.1.2.1.6.2 | Naming conventions | It is possible to assess naming conventions. |
| SQA08.M.1.2.1.6.3 | Limitations | It is possible to assess size and complexity limitations. |
| SQA08.M.1.2.1.6.4 | Layout conventions | It is possible to assess layout conventions. |
| SQA08.M.1.2.1.6.5 | Means of representation | It is possible to assess commitments to certain representation types. |
| SQA08.M.1.2.2 | State charts | |
| SQA08.M.1.2.2.1 | Reachability | It is possible to assess if a given follow-up marking can be reached in a state chart with a given initial marking. |
| SQA08.M.1.2.2.2 | Events | It is possible to list all transitions to which no events have been allocated. |
| SQA08.M.1.2.2.3 | Conditions | It is possible to list all transitions to which no conditions have been allocated. |
| SQA08.M.1.2.2.4 | Actions | It is possible to list all states to which no actions have been allocated. |
| SQA08.M.1.2.2.5 | Activities | It is possible to list all states to which no activities have been allocated. |
| SQA08.M.1.2.2.6 | Assessment of conventions | |
| SQA08.M.1.2.2.6.1 | Project standards | It is possible to define the conventions to be assessed with regard to individual projects. |
| SQA08.M.1.2.2.6.2 | Naming conventions | It is possible to assess naming conventions. |
| SQA08.M.1.2.2.6.3 | Limitations | It is possible to assess size and complexity limitations. |
| SQA08.M.1.2.2.6.4 | Layout conventions | It is possible to assess layout conventions. |
| SQA08.M.1.2.2.6.5 | Means of representation | It is possible to assess commitments to certain representation types. |
| SQA08.M.1.2.3 | Specification and Description Language (SDL) | |
| SQA08.M.1.2.3.1 | Assessment of conventions | |
| SQA08.M.1.2.3.1.1 | Display of limitations | It is possible to display size and complexity limitations of the tool. |
| SQA08.M.1.2.3.1.2 | Display of limits | It is possible to display the current exhaustion of the size and complexity limitations while working with the tool. |
| SQA08.M.1.2.3.1.3 | Control of limitations | It is possible to automatically control if the size and complexity limitations are exceeded and, if so, to display this fact. |
| SQA08.M.1.2.3.2 | Interface consistency in case of hierarchical refinement | |
| SQA08.M.1.2.3.2.1 | Assessment of channel-block interfaces | In case a channel is refined, the channel-block interfaces are automatically assessed with regard to consistency. |
| SQA08.M.1.2.3.2.2 | Assessment of interfaces | If subtrees and an overall tree diagram are simultaneously available for blocks or processes, the interfaces are automatically assessed with regard to consistency. |
| SQA08.M.1.2.3.2.3 | Assessment of hierarchy levels | In case of process-block allocations, it is possible to assess the hierarchy levels with regard to consistency. |
| SQA08.M.1.2.3.2.4 | Assessment with regard to available process | In case of process-block allocations it is possible to assess if a process has been allocated to each terminal block. |
| SQA08.M.1.2.3.3 | Assessment of consistency | |
| SQA08.M.1.2.3.3.1 | Assessment of syntax | The assessment of the syntax for an entire system description extends over all existing connectors and above that. |
| SQA08.M.1.2.3.3.2 | Assessment of visibility | The visibility of identifiers for types, signals, variables, formal parameters, procedures, and macros is assessed at each occurrence whenever they occur. |
| SQA08.M.1.2.3.3.3 | Assessment of the limited applicability | A limited applicability of identifiers for types, signals, variables, formal parameters, procedures, and macros is assessed at each occurrence in the case of given visibility. |
| SQA08.M.1.2.3.4 | Completeness of the description | |
| SQA08.M.1.2.3.4.1 | Blocks and processes | It is possible to display information about not-described blocks and processes. |
| SQA08.M.1.2.3.4.2 | Signals | It is possible to display information about unused signals. |
| SQA08.M.1.2.3.4.3 | Input | It is possible to display information about states for which no input signal has been entered. |
| SQA08.M.1.2.3.4.4 | Start/stop symbols | It is possible to display information about missing start or stop symbols. |
3.3 Requirements for Functions
| SQA08.F.1 | Delimitation of to the assessment | It is possible to delimit size and extent of the assessment to selectable characteristics. |
| SQA08.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. |
| SQA08.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
| SQA08.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. |
| SQA08.O.2 | 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. |
| SQA08.O.3 | 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). |
| SQA08.O.4 | 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
|