Previous Next Functional Tool Requirements Homepage  
System Development Submodel  
SSD25 - Supporting Process Diagrams  

  LSE25 - Prozeßdiagramme unterstützen

Contents  
  • 1 Allocation to V-Model and Methods Allocation
  • 2 Brief Characteristics
  • 3 Requirements
  •       3.1 Requirements for Interfaces
  •       3.2 Requirements for the Methods Support
  •       3.3 Requirements for Functions
  •       3.4 Other Requirements

    • 1 Allocation to V-Model and Methods Allocation

    V-Model

    SD1.1 - Recording of Actual Status and Analysis

  • User Requirements.Actual Status and Current Analysis

    • SD1.2 - Description of Application System

  • User Requirements.Preliminary System Description

    • SD1.4 - Definition of Marginal Conditions

  • User Requirements.Marginal Conditions

    • SD2.1 - Technical System Design

  • System Architecture.Representation of the Technical System Architecture
  • Technical Requirements.Overall Function of Element

    • SD3.5 - Definition of Requirements for the Development and SWMM Environment

  • Technical Requirements.Technical Requirements for the Development and SWMM Environment

    • SD4.1 - SW Architecture Design

  • SW Architecture.Solution Proposals
  • SW Architecture.Modularization/Database Design

    • Method

    PRODIAG - Process Diagrams

    2 Brief Characteristics

    This service unit defines the requirements for tools used to support the object-oriented method PRODIAG - Process Diagrams.

    3 Requirements

    3.1 Requirements for Interfaces

    SSD25.I.1 Granularity The exchange of control parameters with SWFM01 - Workflow Management is possible for individual closed function packages of the tool by means of a disclosed, documented interface.
    SSD25.I.2 Input Interface to SSD22 - Supporting Class/Object Modeling It is possible to access information about classes and objects defined with SSD22 via the object management.
    SSD25.I.3 Input Interface to SSD24 - Supporting Module Diagrams It is possible to access information about main programs defined by SSD24 via the object management.
    SSD25.I.4 Input Interface to SSD29 - Formal Specification It is possible to access information about specification defined with SSD29 via the object management.
    SSD25.I.5 Input Interface to SSD30 - Formal Verification It is possible to access information about verifications realized with SSD30 via the object management.
    SSD25.I.6 Input Interface to SSD31 - Analysis of Covert Channels It is possible to access information about the analysis for covert channels realized with SSD31 via the object management.

    3.2 Requirements for the Methods Support

    SSD25.M.1 PRODIAG - Process Diagrams
    SSD25.M.1.1 Symbols
    SSD25.M.1.1.1 Processors A symbol is available for the representation of hardware units able to execute programs.
    SSD25.M.1.1.2 Devices A symbol is available for the representation of hardware units not able to execute programs.
    SSD25.M.1.1.3 Links A symbol is available for the representation of physical communication links between processors and from these to devices.
    SSD25.M.1.2 Names It is possible to allocate identifying names for processors and devices.
    SSD25.M.1.3 Allocation of Processes It is possible to extend process symbols with a list of process names.
    SSD25.M.1.4 Description of Links It is possible to explain links by means of a description.
    SSD25.M.1.5 Additional Descriptions It is possible to file detailed information about processors, devices, links and processors in additional descriptions.

    3.3 Requirements for Functions

    none

    3.4 Other Requirements

    SSD25.O.1 Upward Compatibility It must be possible to process objects that were generated with an older release of the tool with the later release of that tool, without loss of information and functionality.
    SSD25.O.2 Procedural Command Language The tool has a procedural command language that can be applied by the user to generate and run macros or procedures.
    SSD25.O.3 Complexity There is no limitation of the complexity caused by the tool itself.

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