![]() |
![]() |
![]() |
|
![]() |
|||
| SD 2: System Design |
Contents
|
|
|
|---|
Product Flow
| From | Product | to | Methods | Tool Req. | Ext. Norms | |||
|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | |||
| External | - | All | Product Information | - | - | |||
| PM2 | accepted | All | Offer Evaluation (1) | - | - | |||
| PM5 | accepted | All | Cost/Benefit Analysis | - | - | |||
| SD1 | accepted | Existing | User Requirements | - | - | |||
| - | - | Existing | System Architecture | SD1 (2) , SD3 SD4-SW PM4 PM5 |
submitted |
BA COM CRC ER FCTD IAM PRODIAG SIMU SSM |
||
| - | - | Existing | Technical Requirements | SD3 | being proc. |
COM CRC PRODIAG SSM |
||
| - | - | Existing | Operational Information: User Manual Diagnosis Manual Operator Manual Other Application Information |
SD3 | being proc. | |||
| - | - | Existing | Interface Overview | SD4-SW CM4 |
being proc. |
COM DFM SSM |
||
| - | - | Existing | Interface Description | SD3 SD4-SW CM4 |
being proc. |
ACC COM DVER FS IAM SSM STMO |
||
| - | - | Existing | Integration Plan | SD4-SW QA3 |
being proc. |
BAR DTAB NPT/ |
||
+ "Chapter" are extra columns from the original printed version of GD 250
Handling
Figure 4.3: SD2 - System Design
This solution proposal is evaluated with the help of the feasibility studies that are based on the User Requirements and the available product information. The result of this evaluation with regard to the possible use of off-the-shelf-products has to be taken into consideration in the possibly following update of the System Architecture.
The solution proposal is refined and the allocation of User Requirements to the elements of the System Architecture is realized. Details for the Technical Requirements must be generated, as far as this is possible.
The definition of the System Architecture ends with the identification of the interfaces (system interfaces to the environment [e. g. to the user and other systems] and interfaces between elements of the System).
Each interface identified in the System Architecture must be entered into the Interface Overview and be documented in the Interface Description.
Roles
| Role | Participation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| IT Representative | cooperating (SD2.1,
SD2.3)
| IT Security Representative |
cooperating (SD2.3 | responsible (SD2.2) Project Leader |
cooperating (SD2.1,
SD2.3)
| System Analyst |
cooperating (SD2.3)
| System Designer |
responsible (SD2.1,
SD2.3,
SD2.4,
SD2.5,
SD2.6)
| Technical Author |
cooperating (SD2.1,
SD2.6) |
|
Sub-activities
Tools Requirements
External Norms
Links to the V-Model Mailinglist
(1) In case off-the-shelf products are to be used.
(2) In case a requirements controlling is to be realized on the basis of an actual architecture proposal.
(3) If necessary, several competing solution proposals can be set up and realized.


This page online
GDPA Online
Last Updated 10.Sep.2002 by
C. Freericks