Previous Next V-Model Official Homepage by IABG  
Header  
SD 2.5: Interface Description  

  SE2.5 - Schnittstellen beschreiben

Mail 0304 - Re: Anwenderforderung zur Datenhaltung auf Ebene der SE 1.2
Contents  
  • Product Flow
  • Handling
  • Roles
  • Methods
  •  
  • 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 Existing User Requirements - -     /ISO IEC 12207/

    Devlp. Proc.:
    Sys. Arch. Design

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

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

    Handling

    * Interface Description

    All interfaces identified in the Interface Overview must be specified in the Interface Description. By taking into consideration the type of the individual interface and the type of the corresponding architecture elements, the relevant information about use, syntax and semantics of the interface has to be documented.

    * Description of the Interfaces between the IT Security Measures and the Participating Architecture Elements

    The interfaces of the IT security measures to the participating architecture elements have to be documented.

    Roles

    Role Participation
    System Designer responsible

    Methods

    Product Methods Allocation Use
    Chapter 2
    Interface Description.
    Description of the interfaces
    ACC - Analysis of Covert Channels (5) Generate
    COM - Class/Object Modeling (2) Generate
    DVER - Design Verification (4) Generate
    FS - Formal Specification (1) Generate
    IAM - Interaction Modeling (2) Generate
    SSM - Subsystem 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
    SSD23 - Supporting Subsystem 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 System Architectural Design (s. Part 3 - ISO 3.2.1)


    Notes:

    (1) Method FS is to be applied in case of special requirements with regard to correctness, e. g. based on very high criticality.

    (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 ACC must be applied according to [ITSEC].

    Links to the V-Model Mailinglist

    Mail 0720 - Re: Abgrenzung zwischen Anwenderforderungen und Technischen Anforderungen (720)

    Previous Next This page online  •  GDPA Online  •  Last Updated 07.Mar.2004 by C. Freericks