Previous Next V-Model Official Homepage by IABG  
Header  
SD 4-SW: Preliminary SW Design  

  SE4-SW - SW-Grobentwurf

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
    SD1 accepted All User Requirements - -      
    SD2 accepted All System Architecture - -    
    SD3 accepted All Technical Requirements - -    
    SD2 being proc. Existing Interface Description SD5-SW
    CM4
    submitted ACC (7)
    COM (2)
    DVER (6)
    FS (5)
    IAM (2)
    STMO (3)
     
    SD2 being proc. Existing Interface Overview SD5-SW
    CM4
    submitted COM (2)
    MODIAG (2)
    SSM (2)
     
    SD2 being proc. Existing Integration Plan SD7-SW
    SD8
    QA2
    submitted    
    SD3 being proc. Existing Operational Information:
    User Manual
    Diagnosis Manual
    Operator Manual
    Other Application Information
    SD5-SW being proc.    
    - - All Software Architecture SD5-SW submitted ACC (7)
    COM (2)
    DVER (6)
    FS (5)
    MODIAG (2)
    ODT (8)
    PIM (3)
    PRODIAG (2)
    SSM (2)
    STM (4)
    STRD (8)
     

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

    Handling

    Figure 4.5

    Figure 4.5: SD4 - Preliminary SW Design

    This activity includes the design of the Software Architecture, inclusive of: the completion of the Interface Overview, the description of the SW interfaces, and the update of the Integration Plan on SW level.

    It is task of the Software Architecture design to set up processes with regard to the dynamics of the SW Unit, and possibly to realize the allocation to processors; it is also to design communication and synchronization of the processes and to define SW Modules, SW Components and Databases from the point of view of the static structure of the SW Unit. A short performance specification has to be set up for each of these architecture elements, and the generated interfaces must be identified. The cooperation of SW Modules/Processes, SW Components and Databases must then be specified in the Interface Description. This information is used as a starting point for the detailed software design.

    The Operational Information (User Manual, Diagnosis Manual, Operator Manual, Other Application Information) started on system level must now be completed by the information about the SW Unit in question.

    Roles

    Role Participation
    SW Developer responsible (SD4.1-SW, SD4.2-SW, SD4.3-SW)
    Technical Author cooperating (SD4.1-SW, SD4.3-SW)

    Sub-activities

    SD4.1 - SW Architecture Design,
    SD4.2 - Design of Internal and External SW Interfaces,
    SD4.3 - Specification of SW Integration

    Tools Requirements

    Being defined

    External Norms

    Being defined

    Links to the V-Model Mailinglist

    Mail 0524 - Mehrere Fragen zum V-Modell (524)
    Mail 0139 - Re: V-Modell 97 (139)
    Mail 0134 - V-Modell 97 (134)


    (1) "IT security specific or IT security relevant portions" also refers to the functions of high criticality that are realized by corresponding measures.

    (2) The methods have to be applied in object-oriented developments.

    (3) Method PIM is to be applied when the design contains several processes to be parallelly executed.

    (4) Method STM is to be applied if complex situations have to be considered during the run of the function or the process.

    (5) Method FS is to be applied in case of special requirements to correctness, e. g. based on very high criticality. According to [ITSEC], FS is required for the description of the formal security model with the evaluation level E4, for the preliminary design FS is required with the evaluation level E6.

    (6) A formal specification on two different abstraction levels is required for the application of DVER. Because of the great effort, the most critical portions of a specification have to be selected for which the DVER has to be applied. According to [ITSEC], method DVER is required for the proof of the formal security model with the evaluation level E4, for the proof of consistency between security model and preliminary design DVER is required with the evaluation level E6.

    (7) Method ACC must be applied according to [ITSEC].

    (8) Method ODT is to be applied for a realtime-oriented development with parallel processes; otherwise method STRD has to be applied.

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