Previous Next Functional Tool Requirements Homepage  
System Development Submodel  
SSD12 - Generating Components and Modules  

  LSE12 - Komponenten und Module generieren

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

    SD6.1 - Coding of SW Modules

  • Implementation Document: Modules. Code
  • Implementation Document: Modules. Listings/Protocols
  • Implementation Document: Modules. Procedures

    • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools used to generate-depending on the corresponding target language-the source code from the specifications for Components or Modules and-depending on the corresponding target system-the required procedure code.

    3 Requirements

    3.1 Requirements for Interfaces

    SSD12.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.
    SSD12.I.2 Input interface to SSD10 - Supporting Component and Module Specification It is possible to directly integrate specifications for Components and Modules generated with SSD10 from the object management without further transformation in order to generate source code.
    SSD12.I.3 Output interface to SSD15 - Compiling It is possible to transmit source code generated for Components and Modules via the object management without further transformation to SSD15 in order to be compiled.
    SSD12.I.4 Output interface to SSD17 - Debugging It is possible to transmit source code for Components and Modules via the object management without further transmission to SSD17 in order to be debugged.
    SSD12.I.5 Output interface to SSD20 - Transforming Code Backwards It is possible to transmit generated source code for Components and Modules via the object management without further transformation to SSD20 in order to be converted into specifications.
    SSD12.I.6 Output interface to SQA14 - Generation of Test Cases It is possible to transmit generated source code 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

    SSD12.F.1 Code generation It is possible to transform specifications of Components and Modules into compilable or interpretable code, depending on the corresponding target system. The term target systems refers here to Compiler or Interpreter for source code and procedure code of certain manufacturers.
    SSD12.F.2 Completeness The code generation is complete to a degree that manual additions and modifications in the following steps are not required.
    SSD12.F.3 Implicit prevention of manual modifications Manual modifications of generated code are implicitly prevented by the tool.
    SSD12.F.4 Maintenance on code level in exceptional cases
    SSD12.F.4.1 Explicit selection of manual modifications Manual modifications of generated code are only possible after explicit selection.
    This way the maintenance on code level is to be made possible.
    SSD12.F.4.2 Modularity The generated code has a modular structure so code sections for the communication with the user via the user interface, for the executive sequencing, for special processing, and for data or database accesses can be identified as complete units.
    SSD12.F.4.3 Structured programming The generated code corresponds to the principles of structured programming.
    SSD12.F.5 Integration of existing Components and Modules
    SSD12.F.5.1 Explicit integration It is possible to get explicitly existing code for Components and Modules integrated into the resulting code during the generation.
    In the present case, explicitly identified code sections are integrated by the user into the code only for the actual generating run.
    SSD12.F.5.2 Automatic integration It is possible to get automatically existing code for Components and Modules integrated into the resulting code during the generation.
    In the present case, existing code sections-e. g. for login or security routines, cancel and error recovery routines, or help routines-are integrated into the code during all generating runs.
    SSD12.F.6 Comments
    SSD12.F.6.1 Suppression of comments It is possible to suppress comments (e. g. from the specification) in the generated code.
    SSD12.F.6.2 Structuring comments It is possible to generate structuring comments automatically.
    SSD12.F.6.3 Comprehensive comments It is possible to set differently the frequency and the detail of automatically generated comments.

    3.4 Other Requirements

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