Previous Next V-Model Official Homepage by IABG  
Header  
SD 2: System Design  

  SE2 - System-Entwurf

Contents  
  • Product Flow
  • Handling
  • Roles
  • Sub-activities
  •  
  • Tools Requirements
  • External Norms
  • Links to the V-Model Mailinglist
  • 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

    Figure 4.3: SD2 - System Design

    * Setting up the System Architecture

    Based on the user-level requirements and the marginal conditions (User Requirements) a solution proposal is generated for a possible technical system structure (System Architecture).(3) The appropriate use of off-the-shelf-product must be given special attention.

    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.

    * Setting up the Integration Plan

    As soon as the System Architecture is selected the specification of the system integration must be started. The integration strategy has to be defined in the Integration Plan and must explain which elements, which measures, and which resources are required for the integration of the System.

    * Documentation of already recognizable Operational Information

    At this point, information may already be available that is relevant for Operational Information (User Manual, Diagnosis Manual, Operator Manual, Other Application Information). Therefore, all that information should be used in the present documents that might be of interest for the user documentation.

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

    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

    SD2.1 - Technical System Design
    SD2.2 - Realization of Efficiency Analysis
    SD2.3 - Investigation of Feasibility
    SD2.4 - Allocation of User Requirements
    SD2.5 - Interface Description
    SD2.6 - Specification of System Integration

    Tools Requirements

    Being defined

    External Norms

    Being defined

    Links to the V-Model Mailinglist

    Mail 0595 - Re: Unterstützung der Betriebseinführung (595)
    Mail 0524 - Mehrere Fragen zum V-Modell (524)
    Mail 0246 - Re: Umfang von SE 1.2 bei inkrementeller Entwicklung (246)
    Mail 0178 - Re: Technische Anforderungen (178)
    Mail 0148 - SE 2, Systemarchitektur (149)


    Notes:

    (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.

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