SD 1.2: Description of Application System



		SD 1.2: Description of Application System

SE1.2 - Anwendungssystem beschreiben

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	being proc.	Existing	User Requirements	-	-
-	-	6.1	User Requirements. Preliminary System Description	SD1.3 SD1.4 SD1.5 SD1.6	being proc.	COM CRC DFM IAM PRODIAG SSM STMO UCM	SSD01 SSD05 SSD07 SSD22 SSD23 SSD25 SSD26 SSD27 SSD28
-	-	3	User Requirements. IT Security Objective	SD1.3 SD1.4 SD1.5 SD1.6	being proc.		SSD01

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

An overall horizon must be specified for the system functionality within the scope of this activity. This is realized by means of a preliminary system description which is the background for all further refinements and additions of the User Requirements.

The description of the overall horizon has to consider the following criteria:

It is necessary to define which user-level tasks are to be supported by the System. Therefore, the integration of the System into the organization or the integration environment must be described.

The overall horizon must point out the overall functionality to be covered in the final version and which priorities are expected in the course of the following development.

The overall horizon must include the application concept in order to derive the technical and organizational application environment and the marginal conditions (within the scope of activity SD1.4 - Definition of Marginal Conditions).

The overall horizon must include quantitative estimations that can be used to make basic technical decisions with the correct order of magnitude (network organization, computing power, etc.).

The representation of the overall horizon must be very exact in order to make it possible in future to decide when this overall horizon should or can be left and technical decisions might be reconsidered accordingly.

The use of predefined user-level items (standard topics) must be taken into consideration. Possible candidates for the reuse on the level of the User Requirements within the scope of the planned development must be named.

In addition to the operational requirements for the System, the customer must specify the IT security objectives. The security objectives may consist of certain protection goals for some operational functions or processed information with regard to availability, integrity and confidentiality (i. e. reliability), or else an already specified security policy to be realized in the overall System. It must be specified in the User Requirements if, and if yes, which requirements with regard to availability, integrity or confidentiality exist for certain functions or information. The IT security objectives are the basis for a threat and risk analysis from which IT security requirements for the elimination of intolerable risks can be concluded. The IT security requirements must then be realized by the corresponding IT security measures.

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

Roles

Role	Participation
System Analyst	responsible
User	cooperating

Methods

Product Methods Allocation Use
Chapter 6.1
User Requirements.
Preliminary System Description COM - Class/Object Modeling ⁽²⁾ Generate
CRC - Class Responsibility Collaboration ⁽²⁾ Generate
DFM - Data Flow Modeling Generate
IAM - Interaction Modeling ⁽²⁾ Generate
PRODIAG - Process Diagrams ⁽²⁾ Generate
SSM - Subsystem Modeling ⁽²⁾ Generate
STMO - State Modeling in the OO Field ⁽¹⁾ Generate
UCM - Use Case Modeling ⁽²⁾ Generate

Product	Methods Allocation	Use
Chapter 6.1 User Requirements. Preliminary System Description	COM - Class/Object Modeling ⁽²⁾	Generate
CRC - Class Responsibility Collaboration ⁽²⁾	Generate
DFM - Data Flow Modeling	Generate
IAM - Interaction Modeling ⁽²⁾	Generate
PRODIAG - Process Diagrams ⁽²⁾	Generate
SSM - Subsystem Modeling ⁽²⁾	Generate
STMO - State Modeling in the OO Field ⁽¹⁾	Generate
UCM - Use Case Modeling ⁽²⁾	Generate

Notes:
(1) Method STMO is to be applied for the dynamic system modeling in object-oriented procedures.
(2) The methods have to be applied in object-oriented developments.

Tools Requirements

Product	Functional Tools Requirements
Chapter 6.1 User Requirements. Preliminary System Description	SSD01 - Recording Requirements SSD05 - Supporting Function Structure SSD07 - Supporting Modeling of Information Flows SSD22 - Supporting Class/Object Modeling SSD23 - Supporting Subsystem Modeling SSD25 - Supporting Process Diagrams SSD26 - Supporting Use Case Modeling SSD27 - Supporting State Modeling in the Object-Oriented Field SSD28 - Supporting Interaction Modeling
Chapter 3 User Requirements. IT Security Objective	SSD01 - Recording Requirements

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