 |
 |
 |
|
| 3 Functional Tool Requirements |
3 Functional Tool Requirements
The following chapters which are structured according to the preliminary structure of an SDE contain descriptions of the individual service units that make up the SDE reference model, together with the corresponding requirements.
3.1 Notes for the Description of the Tool Requirements
Each functional tool requirement has been allocated an alphanumeric name and can thus be uniquely identified.
The requirements are in hierarchical order to guarantee applicability and comprehensibility for different users. The hierarchical trees thus generated are not limited with regard to their depth.
The requirements are identified according to the following schema:
| Rn.p.q |
Which means:
| R | = | SOM | for Object Management |
| R | = | SUI | for User Interface |
| R | = | SWFM | for Workflow Management |
| R | = | SSEC | for Security |
| R | = | SSD | for System Development |
| R | = | SQA | for Quality Assurance |
| R | = | SCM | for Configuration Management |
| R | = | SPM | for Project Management |
"n" is the number of the individual service unit
Which means:
| p | = | I | for Requirements for Interfaces |
| p | = | M | for Requirements for the Methods Support |
| p | = | F | for Requirements for Functions |
| p | = | O | for other Requirements |
"q" refers to a requirement within a service unit and consists of numbers separated by dots; the count of numbers informs about the hierarchy level of the requirement.
Example:
- SSD01.I.2.1 and SSD01.I.2.2 are refinements or improvements of the requirement
SSD01.I.2 (service unit "Recording Requirements", requirements for interfaces). - SCM01.O identifies the other requirements of service unit "Supporting Configuration Planning and Control".
Links to the V-Model Mailinglist
Mail 0281 - Re: Werkzeugunterstuetzung (281)
|
|
|
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
|