SD 1.5: User-Level System Structure



		SD 1.5: User-Level System Structure

SE1.5 - System fachlich strukturieren

Contents
Product Flow
Handling
Roles
Methods

Tools Requirements
External Norms
Pre-Tailoring forms
Links to the V-Model Mailinglist

Contents		Product Flow Handling Roles Methods		Tools Requirements External Norms Pre-Tailoring forms Links to the V-Model Mailinglist

Product Flow

From		Product		to		Methods	Tool Req.	Ext. Norms
Activity	State	Chapter	Title	Activity	State	Methods	Tool Req.	Ext. Norms
External	-	All	External Specifications (customer)	-	-			/ISO IEC 12207/ Acquis. Proc.: Initiation, Devlp. Proc.: Syst. Req. Analysis
SD1.1 SD1.2 SD1.3 SD1.4	being proc.	Existing	User Requirements	-	-
-	-	6.2	User Requirements. Organizational Embedding	SD1.6	being proc.	SSM	SSD01
-	-	6.3	User Requirements. Utilization			UCM	SSD01 SSD26
-	-	6.5	User Requirements. External Interfaces				SSD01
-	-	6.6	User Requirements. Description of the Functionality			COM CRC DFM ER EXPM FCTD FNET IAM SBM / STMO	SSD01 SSD05 SSD06 SSD07 SSD08 SSD09 SSD21 SSD22 SSD23 SSD27 SSD28

+ "Chapter" are extra columns from the original printed version of GD 250

This is where the System is structured and described from a user-level point of view. The user-level system structure is modeled and described according to the aspects of the user world. This includes the specification of goals for business processes. In order to explain how the System functions or to define the business processes, sequence descriptions must be set up that represent the cooperation of the user with the System.

The generated descriptions must be refined to a degree that all user-level aspects can be defined and, if necessary, the required understanding on system level between user and implementor of the System can be definitely and completely arranged.

In this activity, the functional fields must be defined independently of a possible or probable technical architecture and realization.

Criticality levels are allocated to the functional fields and the structure elements they are based on within the scope of the description of the functionality.

With regard to functions used to guarantee the system security, external IT security measures and regulations must also be included in the consideration, possibly organizational measures as well.

The structure and process organization at the user has to be specified. Any required personnel measures must be identified and their realization initiated.

The required training measures have to be planned (definition of target groups, curricula, coach). It is necessary to start early with the realization of these measures. The documentation of the measures to be realized is not regulated in the V-Model.

---------- The following part is an extension of the original printed version of GD 250 -----------

Roles

Role	Participation
System Analyst	responsible
Technical Author	cooperating
IT Representative	cooperating
Data Administrator	cooperating
Data Protection Specialist	advising
IT Security Representative	cooperating
User	cooperating
System Administrator	cooperating

Methods

Product Methods Allocation Use
Chapter 6.2
User Requirements.
Organizational Embedding SSM - Subsystem Modeling ⁽²⁾ Generate
Chapter 6.3
User Requirements.
Utilization UCM - Use Case Modeling ⁽²⁾ Generate
Chapter 6.6
User Requirements.
Description of the Functionality COM - Class/Object Modeling ⁽²⁾ Generate
CRC - Class Responsibility Collaboration ⁽²⁾ Generate
DFM - Data Flow Modeling Generate
ER - E/R Modeling ⁽¹⁾ Generate
EXPM - Expertise Model <⁽⁵⁾ Generate
FCTD - Functional Decomposition Generate
FNET - Function Net Modeling ⁽⁴⁾ Generate
IAM - Interaction Modeling ⁽²⁾ Generate
SBM - System Behavior Models /⁽⁴⁾ Generate
STMO - State Modeling in the OO Field ⁽³⁾ Generate

Product	Methods Allocation	Use
Chapter 6.2 User Requirements. Organizational Embedding	SSM - Subsystem Modeling ⁽²⁾	Generate
Chapter 6.3 User Requirements. Utilization	UCM - Use Case Modeling ⁽²⁾	Generate
Chapter 6.6 User Requirements. Description of the Functionality	COM - Class/Object Modeling ⁽²⁾	Generate
CRC - Class Responsibility Collaboration ⁽²⁾	Generate
DFM - Data Flow Modeling	Generate
ER - E/R Modeling ⁽¹⁾	Generate
EXPM - Expertise Model <⁽⁵⁾	Generate
FCTD - Functional Decomposition	Generate
FNET - Function Net Modeling ⁽⁴⁾	Generate
IAM - Interaction Modeling ⁽²⁾	Generate
SBM - System Behavior Models /⁽⁴⁾	Generate
STMO - State Modeling in the OO Field ⁽³⁾	Generate

Notes:
(1) Method ER is to be applied for information systems.
(2) The methods have to be applied in object-oriented developments.
(3) Method STMO is to be applied for the dynamic system modeling in object-oriented procedures.
(4) Method SBM is to be applied for realtime applications or respectively distributed systems with a high level of criticality. Method FNET is to be applied for information systems.
(5) Method EXPM is intended for knowledge-based systems.

Tools Requirements

Product	Functional Tools Requirements
Chapter 6 User Requirements. User-Level Requirements	SSD01 - Recording Requirements
Chapter 6.3 User Requirements. Utilization	SSD26 - Supporting Use Case Modeling
Chapter 6.6 User Requirements. Description of the Functionality	SSD05 - Supporting Function Structure SSD06 - Supporting Function Specification SSD07 - Supporting Modeling of Information Flows SSD08 - Supporting Modeling of Function Dynamics SSD09 - Supporting Information Structuring SSD21 - Transforming Databases, Data Structures Backwards SSD22 - Supporting Class/Object Modeling SSD23 - Supporting Subsystem Modeling SSD27 - Supporting State Modeling in the Object-Oriented Field SSD28 - Supporting Interaction Modeling

External Norms

Norm	Process	Chapter	Obs.
/ISO IEC 12207/	Acquisition Process	Initiation	(s. Part 3 ISO 3.2.1)
/ISO IEC 12207/	Development Process	System Requirements Analysis	(s. Part 3 ISO 3.2.1)

Pre-Tailoring forms

Pre-tailoring Forms	SD Products																		Implementing Conditions
Pre-tailoring Forms
Small Administrative IT Projects
Medium Administrative IT Projects
Large Administrative IT Projects
Small/Medium Technical-Scientific IT Projects
Large Technical-Scientific IT Projects
Selection, Procurement and Adjustment of Off-the-Shelf Products