Previous Next V-Model Official Homepage by IABG  
Header  
SD 3.3: Definition of Requirements for the Functionality  

  SE3.3 - Anf. an die Funktionalitšt definieren

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 All User Requirements - -      
    SD2 accepted All System Architecture - -    
    SD3.1
    SD3.2
    being proc. Existing Technical Requirements - -    
    - - 5.x.2 Technical Requirements.
    Overall Function of Element
    SD3.4
    SD3.5
    being proc. COM (2)
    CRC (2)
    DFM
    DTAB (6)
    ELH (5)
    ER (1)
    FCTD
    FNET (4)
    IAM (2)
    SBM/ (4)
    STM (7)
    STMO (3)
    SSD01
    SSD04
    SSD05
    SSD06
    SSD07
    SSD08
    SSD21
    SSD22
    SSD27
    SSD28

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

    Handling

    This activity has to define the requirements for the technical functionality of the SW Unit/HW Unit.

    The functionality to be realized by the SW Unit/HW Unit has to be identified and to be established. The requirements with regard to the reactions of the SW Unit/HW Unit in a normal and in an exceptional case must be defined.

    Here the functionality of HW Units also includes electrical, mechanical and optical function parts.

    Roles

    Role Participation
    System Designer responsible

    Methods

    Product Methods Allocation Use
    Chapter 5.x.2
    Technical Requirements.
    Overall Function of Element
    COM - Class/Object Modeling (2) Generate
    CRC - Class Responsibility Collaboration (2) Generate
    DFM - Data Flow Modeling Generate
    DTAB - Decision Table Technique (6) Generate
    ELH - Entity Life History (5) Generate
    ER - E/R Modeling (1) Generate
    FCTD - Functional Decomposition Generate
    FNET - Function Net Modeling (4) Generate
    IAM - Interaction Modeling (2) Generate
    SBM - System Behavior Models/ (4) Generate
    STM - State Transition Modeling (7) Generate
    STMO - State Modeling in the OO Field (3) Generate

    Tools Requirements

    Product Functional Tools Requirements
    Chapter 5.x.2
    Technical Requirements.
    Overall Function of Element
    SSD01 - Recording Requirements
    SSD04 - Supporting Process Modeling
    SSD05 - Supporting Function Structure
    SSD06 - Supporting Function Specification
    SSD07 - Supporting Modeling of Information Flows
    SSD08 - Supporting Modeling of Function Dynamics
    SSD21 - Transforming Databases, Data Structures Backwards
    SSD22 - Supporting Class/Object Modeling
    SSD27 - Supporting State Modeling in the Object-Oriented Field
    SSD28 - Supporting Interaction Modeling

    External Norms

    Being defined

    Links to the V-Model Mailinglist

    Mail 0716 - Abgrenzung zwischen Anwenderforderungen und Technischen Anforderungen (716)
    Mail 0256 - Re: Midestanforderungen (256)


    Notes:

    (1) Method ER is to be applied for information systems.

    (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) Method SBM is to be applied for realtime applications or respectively distributed systems with a high level of criticality. Method FNET is to be applied for information systems.

    (5) Method ELH is to be applied for information systems.

    (6) Method DTAB is to be applied for the description of complex facts and circumstances.

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

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