Previous Next V-Model Official Homepage by IABG  
Header SW Design: SW Component/ SW Module (SwDes)  

  SW-Entwurf: SW-Komponent/SW-Module

  • Introduction
  • Document Index
  • Document Structure
  • Links to the V-Model Mailinglist
  • Introduction

    After determining the architecture of the SW Unit, this product describes the detailed design of a SW Component or a SW Module. Results of an analysis about resource and time requirements analysis will also be documented.

    This document describes how and which functions and data are realized by the SW Component or the SW Module, and also which data and services can be exchanged via the interfaces-down to the level of a programming specification. The realization of the data are to be included into the product Data-Dictionary.

    Such a product exists for each SW Module, each SW Component (of each SW Unit of each Segment in the System). It is possible to combine several SW Designs into one product "SW Design".

    Document Index

    1. General Information
    2. SW Component/SW Module Description
          2.1. Characterization of the Task
          2.2. Environment
          2.3. Interfaces
                2.3.1. Passive-Active Call Matrix
                2.3.2. Input/Output Data
                2.3.3. Further Interfaces
          2.4. Realization of the SW Component/ SW Module
          2.5. Local Data
          2.6. Exceptional Behavior
    3. Characteristic Quantities

    Document Structure

    1. General Information

    See schema 1. General Information.

    2. SW Component/SW Module Description

    The realization of each individual SW Component and each SW Module is described in detail, down to the programming specification level.

    2. 1. Characterization of the Task

    The task, the realized function and the purpose of the SW Component/SW Module are described.

    2. 2. Environment

    The environment of the SW Component or the SW Module to be described and its decomposition into SW Components and/or SW Modules are described.

    2. 3. Interfaces

    2. 3. 1. Passive-Active Call Matrix

    The passive-active call matrix, which contains an overview of the embedding, documents the relationships: For clarification not only text, but also a graphic may be used.

    2. 3. 2. Input/Output Data

    In addition to the input and output data and next to syntax and semantics it must also be described how the SW Component/the SW Module reacts to faulty data: which input/output data are checked, how are they checked, how is the reaction if the data do not match?

    2.3.3. Further Interfaces

    Here the process interfaces and the interfaces to SW Components outside the operational software (e. g. to the operating or runtime system) must be described.

    2. 4. Realization of the SW Component/ SW Module

    The control and data flow of the SW Component/SW Module will be represented as a programming specification.

    The SW Component/SW Module must be described completely: algorithms for the normal and exceptional case/in the case of error, initialization/completion steps, pre- and postconditions, processing of global data and states, etc.

    The realization of the data (data type and format, location) has to be included into the product Data-Dictionary.

    2. 5. Local Data

    Here the local data of a module with regard to type, format, initialization, range, content, purpose and access method, etc. will be described.

    2. 6. Exceptional Behavior

    Algorithms to detect and repair error conditions and for well-defined termination are to be described.

    3. Characteristic Quantities

    This chapter deals with, among other things:

    Links to the V-Model Mailinglist

    Mail 0653 - QS-Plan: Fragen zu Festlegung der Kritikalität, Vererbung, Infizierung und zughörigen Dokumenten (653)
    Mail 0577 - Kenngrößen (577)

    Previous Next This page online  •  GDPA Online  •  Last Updated 06.Mar.2003 by C. Freericks