2.3 Service Units of the SDE Reference Model

Contents		2.3 Service Units of the SDE Reference Model 2.3.1 General Service Units 2.3.2 Service Units of the Service Complexes for the V-Model 2.3.3 Service Units, Methods, and V-Model Activities 2.3.4 Service Units and Tools 2.3.5 Service Units and Variants 2.3.6 Service Units of SD and QA 2.3.7 Interactions between Service Units of the Security Service Complex to the Service Units in other Service Complexes 2.3.8 Notes for the Description of Service Units Links to the V-Model Mailinglist

2.3 Service Units of the SDE Reference Model

2.3.1 General Service Units

Object Management

User Interface

Workflow Management

Security

2.3.2 Service Units of the Service Complexes for the V-Model

System Development

Quality Assurance

Configuration Management

Project Management

2.3.3 Service Units, Methods, and V-Model Activities

It must be differentiated between the following cases:

1. A service unit covers exactly one method. An example for this case is service unit SSD05 - Supporting Function Structure which exclusively aims at supporting the basic method FCTD - Functional Decomposition.
2. A service unit covers several methods. This is practical if the methods support a connected task. An example for this case is represented by service unit SPM04 - Supporting Planning of the Project Realization which supports the methods BAR - Bar Plan and NPT - Network Planning Technique.
3. A method is covered by several service units. This case only occurs in connection with method STAT - Static Analysis since in this case the method has to be applied for different objects to be assessed.
4. A method is not covered by any service unit. An example for this case is represented by method REV - Review where tool support is not possible.
5. A service unit covering one method may possibly contain other requirements that are not based on a method. An example for this case is service unit SSD02 - Supporting Specification of User Interfaces which-apart from the support of basic method DIAL - Dialog Design Modeling-contains criteria for the specification of window-oriented user interfaces not based on a method.
6. Frequently, however, tool support is also to be advised for those V-Model activities where the Methods Standard does not suggest a method. Therefore there are also a number of service units that do not support a method. An example for this case is service unit SSD17 - Debugging.

Figure 2.3: Interconnection of Service Units, Methods and Activities

2.3.4 Service Units and Tools

2.3.5 Service Units and Variants

Variants are only to be used where a complete identical (semantic) functionality for input/output with different syntax is required. Variants are to be taken into consideration in connection with the following service units:

SUI05	Editing of Texts	(e. g. programming language syntax, prose syntax)
SUI06	Editing of Graphics	Variants depend on the syntax of the graphics to be edited
SSD12	Generating Components and Modules	Variants depend on the target language
SSD13	Generating Databases	Variants depend on the database system to be applied
SSD14	Generating User Interface Formats	Variants depend on the TP monitor of the target environment
SSD15	Compiling	Variants depend on the programming language to be processed
SSD16	Linking	Variants depend on the syntax of the object code and on the target system
SSD17	Debugging	Variants depend on the programming language to be processed
SQA13	Static Assessment of Texts (no Code)	Variants depend on the syntax of the text to be assessed (e. g. prose, formal specification texts)
SQA14	Generation of Test Cases	Versions depend on the syntax of the object to be assessed
SQA15	Supporting Dynamic Assessments	Variants depend on the syntax of the object to be assessed

2.3.6 Service Units of SD and QA

2.3.7 Interactions between Service Units of the Security Service Complex to the Service Units in other Service Complexes

2.3.8 Notes for the Description of Service Units

1. Allocation to V-Model and Methods Allocation

   This contains a list of the (sub-) products of the (sub-) activities of the V-Model that are supported by the service unit. In case basic methods are intended for these (sub-) activities in the Methods Allocation, they will be listed here as well since the service units will have to support these methods.

   The allocation is realized in a common structure:
   

   brief name of the (sub-) activity/long name
   (sub-) product
   method
   

   Example:

   V-Model Activities (Products)

   SD3.3 - Definition of Requirements for the Functionality
   (Technical Requirements.Overall Function of Element")

   SD4.1 - SW Architecture Design
   (SW Architecture)

   Method

   PIM - Process Interaction Modeling
   STM - State Transition Modeling

2. Brief Characteristic

   The total service for a certain service unit is explained.

3. Requirements
   1. Requirements for Interfaces
      Special requirements for the user interface1, interaction with other service units, consistency requirements to be met
   2. Requirements for the Methods Support
      Requirements resulting from the application of certain methods
   3. Requirements for Functions
      Requirements on the functions made available by the tool that are not based on a method
   4. Other Requirements
      Requirements other than the ones listed above

Links to the V-Model Mailinglist

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster