Previous Next Functional Tool Requirements Homepage  
System Development Submodel  
SSD10 - Supporting Component and Module Specification  

  LSE10 - Spezifikation der Komponenten und Module 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

    SD5.1 - Description of SW Component/Module/Database

  • SW Design (Module). SW Component/SW Module Description
  • Method

    PCODE - Pseudocode

    2 Brief Characteristics

    This service unit defines the requirements for tools applied to specify the logic operation and data handling for a Module or a Component.

    3 Requirements

    3.1 Requirements for Interfaces

    SSD10.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.
    SSD10.I.2 Input interface to SSD02 - Supporting Specification of User Interfaces It is possible to transfer specifications for interfaces generated with SSD02 without further transformation via the object management in order to be integrated into the specification of Components and Modules.
    SSD10.I.3 Input interface to SSD03 - Supporting Architectural Design It is possible to select Components and Modules directly specified in an architecture with SSD03 from the object management as reference points for the specification.
    SSD10.I.4 Input interface to SSD06 - Supporting Function Specification It is possible to integrate directly specifications for functions generated with SSD06 via the object management without further transformation for the specification of Components and Modules.
    SSD10.I.5 Input interface to SSD11 - Supporting Database Specification It is possible to transfer logical schema specifications for databases and data structures collected with SSD11 without further transformation via the object management in order to be integrated into the specification of Components and Modules.
    SSD10.I.6 Input interface to SSD20 - Transforming Code Backwards It is possible to integrate specifications for Components and Modules-generated with SSD20 from the source code-without further transformation from the object management.
    SSD10.I.7 Output interface to SSD12 - Generating Components and Modules It is possible to transmit specifications for Components and Modules without further transformation via the object management to SSD12 in order to generate source code.
    SSD10.I.8 Output interface to SQA14 - Generation of Test Cases It is possible to transmit specifications for Components and Modules without further transformation via the object management to SQA14 in order to generate test cases.

    3.2 Requirements for the Methods Support

    SSD10.M.1 PCODE - Pseudocode
    SSD10.M.1.1 Symbols
    SSD10.M.1.1.1 Control structures Symbols are available for the representation of the control structures sequence, selection, and iteration.
    SSD10.M.1.1.2 Begin and end Symbols are available for the representation of begin and end of a control structure.
    SSD10.M.1.1.3 Abnormal termination Symbols are available for the representation of the abnormal termination of processing within a control structure (cancel statement).
    SSD10.M.1.1.4 Statements Symbols are available to represent statements in a programming language. Programming language statements primarily refer to allocations, calculations, and comparisons.
    SSD10.M.1.1.5 Data declarations Symbols are available for the representation of data declarations down to the level of individual data elements.
    SSD10.M.1.1.6 Data accesses Symbols are available for the representation of data accesses.
    SSD10.M.1.1.7 Parameters Symbols are available for the representation of parameters.
    SSD10.M.1.1.8 Masks Symbols are available for the representation of mask calls.
    SSD10.M.1.1.9 Component/Module Calls Symbols are available for the representation of component and module calls.
    SSD10.M.1.1.10 End of processing Symbols are available for the representation of the termination of processing a Component or a Module.
    SSD10.M.1.1.11 Comments Symbols are available for the representation of comments.
    SSD10.M.1.1.12 Setting the target language It is possible to individually adjust the syntax of the various constructs dependent on the corresponding target environment.
    SSD10.M.1.1.13 Utilization of language elements It is guaranteed that language elements having no corresponding element in the target language are not utilized.

    3.3 Requirements for Functions

    none

    3.4 Other Requirements

    SSD10.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.
    SSD10.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.
    SSD10.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