Previous Next Functional Tool Requirements Homepage  
System Development Submodel  
SSD06 - Supporting Function Specification  

  LSE06 - Spezifikation der Funktionen 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.5 - User-Level System Structure

  • User Requirements.Description of the Functionality
  • SD3.3 - Definition of Requirements for the Functionality

  • Technical Requirements.Overall Function of Element
  • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools applied to specify

    3 Requirements

    3.1 Requirements for Interfaces

    SSD06.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.
    SSD06.I.2 Input interface to SSD05 - Supporting Function Structure It is possible to transfer functions directly collected with SSD05 from the object management as reference points for the specification.
    SSD06.I.3 Output interface to SSD10 - Supporting Component and Module Specification It is possible to transmit specifications for functions via the object management without further transformation to SSD10 in order to specify Components and Modules.
    SSD06.I.4 Output interface to SQA14 - Generation of Test Cases It is possible to transmit specifications for functions via the object management without further transformation to SQA14 in order to generate test cases.

    3.2 Requirements for the Methods Support

    none

    3.3 Requirements for Functions

    SSD06.F.1 Means of representation
    SSD06.F.1.1 Nassi-Shneiderman It is possible to describe functions by means of Nassi-Shneiderman diagrams (action diagrams).
    SSD06.F.1.2 Title Block Each description is started with a title block.
    SSD06.F.1.3 Description of control structures It is possible to represent sequence, selection and iteration as control structures.
    SSD06.F.1.4 Data stores
    SSD06.F.1.4.1 Representation It is possible to graphically represent data store accesses.
    SSD06.F.1.4.2 Links It is possible to represent the links between a data store and the corresponding entities.
    SSD06.F.1.5 Control structures Symbols are available for the representation of control structures.
    SSD06.F.1.6 Data access Symbols are available for the representation of data accesses.
    SSD06.F.1.7 Block structures It is possible to graphically represent logically connected structures.
    SSD06.F.1.8 Representation of constructs It is possible to graphically represent begin and end of constructs.
    SSD06.F.1.9 Masking structures It is possible to extract or to expand logically connected structures in Nassi-Shneiderman diagrams (action diagrams).

    3.4 Other Requirements

    SSD06.O.1 Upward compatibility It must be possible to process objects generated with an older release of the tool with the later release of that tool, without loss of information and functionality.
    SSD06.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.
    SSD06.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