Previous Next V-Model Official Homepage by IABG  
Header  
SD 4.2-SW: Design of Internal and External SW Interfaces  

  SE4.2-SW - SW-interne und -externe Schnittstellen entwerfen

Contents  
  • Product Flow
  • Handling
  • Roles
  •  
  • Methods
  • Tools Requirements
  • External Norms
  • Product Flow

    From Product to Methods Tool Req. Ext. Norms
    Activity State Chapter Title Activity State
    SD1 accepted All User Requirements - -     /ISO IEC 12207/

    Devlp. Proc.:
    SW Arch. Design

    SD2 accepted All System Architecture - -    
    SD3 accepted All Technical Requirements - -    
    SD4.1-SW accepted All Software Architecture - -    
    SD4.1-SW accepted All Interface Overview - -    
    SD2.5 being proc. Existing Interface Description SD4.3-SW
    SD5-SW
    CM4.3
    submitted ACC (1)
    COM (2)
    DVER (4)
    FS (5)
    IAM (2)
    STMO (3)
    SSD02
    SSD22
    SSD27
    SSD28
    SSD29
    SSD30
    SSD31

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

    Handling

    The interfaces identified during the SW Architecture design in the Interface Overview have to be individually described-in detail-in the Interface Description. Interfaces that have already been described must be further specified, if necessary.

    IT security aspects, in the same way as their role was already important during the interface identification, must be further observed, and with particular care. All interfaces of the IT security-specific and the IT security-relevant SW Components/SW Modules must be described with regard to their purpose and with regard to their parameters. The separation from the portion that is not IT security-relevant must be visible.

    Roles

    Role Participation
    SW Developer responsible

    Methods

    Product Methods Allocation Use
    Chapter 2
    Interface Description.
    Description of the Interfaces
    ACC - Analysis of Covert Channels (1) Generate
    COM - Class/Object Modeling (2) Generate
    DVER - Design Verification (4) Generate
    FS - Formal Specification (5) Generate
    IAM - Interaction Modeling (2) Generate
    STMO - State Modeling in the OO Field (3) Generate

    Tools Requirements

    Product Functional Tools Requirements
    Chapter 2
    Interface Description.
    Description of the Interfaces
    SSD02 - Supporting Specification of User Interfaces
    SSD22 - Supporting Class/Object Modeling
    SSD27 - Supporting State Modeling in the Object-Oriented Field
    SSD28 - Supporting Interaction Modeling
    SSD29 - Formal Specification
    SSD30 - Formal Verification
    SSD31 - Analysis of Covert Channels

    External Norms

    Norm Process Chapter Obs.
    /ISO IEC 12207/ Development Process Software Architectural Design (s. Part 3 - ISO 3.2.1)


    Notes:

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

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

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

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