Previous Next V-Model Official Homepage by IABG  
RE Homepage  
RE 3.3.8 SW Architecture (SwArc)  

  SW-Architektur

Contents  
  • Introduction
  • Document Index
  • Document Structure
  • Introduction

    The SW Architecture (preliminary design) contains proposals for possible SW Architectures and for the selected decomposition of the SW Unit: dynamically into individual processes, statically into SW Components, SW Modules, and Databases. The interrelations among processes, SW Components, SW Modules, and Databases are illustrated. Furthermore, the external and internal interfaces of the SW Unit are identified and, finally, the allocation to the requirements is made.

    Such a product exists for each SW Unit.


    Document Index

    1. General Information
    2. Modularization/Database Design
          2.1. Overview of SW Components, SW Modules, Processes and Databases
          2.2. Individual Descriptions
                2.2.m. SW Component/SW Module/Process/Database (m)
          2.3. Dynamic Sequence Model
    3. Interfaces
          3.1. External Interfaces of the SW Unit
          3.2. Internal Interfaces of the SW Unit
    4. Requirements Allocation

    Document Structure

    1. General Information

    See schema 1. General Information.

    2. Modularization/Database Design

    The modularization describes the static decomposition of a SW Unit into SW Components and SW Modules as well as the real-time-specific connections. Furthermore, this chapter includes a preliminary design of the Databases (if available) of the SW Unit.

    2. 1. Overview of SW Components, SW Modules, Processes and Databases

    All SW Modules, processes, SW Components, and Databases are listed, together with their identifications and a long name. A graphical representation should be selected as well (tree) to illustrate the "exists of" hierarchy.

    2. 2. Individual Descriptions

    2. 2. m. SW Component/SW Module/Process/Database (m)

    The SW Component/the SW Module/the process/the Database is defined by a performance specification (purpose and function) and by the utilized resources (CPU, memory, peripherals, processors).

    If relevant this also contains the allocation of the SW Component/the SW Module to the process to be realized.

    Note: "m" is used for consecutive numbers of individual descriptions from 2.2.1 to 2.2.n and as place holder for the identifier of the SW Component, the SW Module, the process, or the Database, according to the conventions for identification defined in the CM Plan.

    2. 3. Dynamic Sequence Model

    This chapter describes the dynamic interrelations of processes. Graphical methods are best suited for the representation.

    This chapter also describes the mechanisms and concepts made available by the runtime environment and during the realization of the processes.

    3. Interfaces

    The external interfaces of the SW Unit resulting from the Technical Requirements and the System Architecture and the internal interfaces resulting from the structure of the SW Unit are identified and allocated to the SW Components, SW Modules and Databases.

    This chapter is integrated into the product Interface Overview.

    3. 1. External Interfaces of the SW Unit

    External interfaces are interfaces of the SW Unit to its environment, i. e. to other SW Units or HW Units and to the user.

    3. 2. Internal Interfaces of the SW Unit

    Internal interfaces of the SW Unit are interfaces between SW Components, SW Modules and Databases.

    4. Requirements Allocation

    The relationships to the Technical Requirements will be set up. It must be documented if all requirements for the corresponding SW Unit are covered and how the requirements have been allocated to processes/SW Components/SW Modules/Databases.

    In connection with the requirements allocation, the following items have to be observed:

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