Previous Next Functional Tool Requirements Homepage  
System Development Submodel  
SSD13 - Generating Databases  

  LSE13 - Datenbanken 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.2 - Realization of Database

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

    • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools used to generate performance-oriented physical schema specifications from logical schema specifications for databases. In this connection, the required procedure code for the database installation can be generated in the corresponding data definition language.

    3 Requirements

    3.1 Requirements for Interfaces

    SSD13.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.
    SSD13.I.2 Input interface to SSD11 - Supporting Database Specification It is possible to integrate directly logical schema specifications for databases and data structures generated with SSD11 without further transformation from the object management in order to generate physical schema specifications.
    SSD13.I.3 Output interface to SSD15 - Compiling It is possible to transmit physical schema specifications for databases and data structures via the object management without further transformation to SSD15 in order to be compiled.
    SSD13.I.4 Output interface to SSD21 - Transforming Databases, Data Structures Backwards It is possible to transmit physical schema specifications for databases and data structures via the object management without further transformation to SSD21 in order to be converted into logical schema specifications.

    3.2 Requirements for the Methods Support

    none

    3.3 Requirements for Functions

    SSD13.F.1 Generation of Physical Schema Specifications With the help of input parameters it is possible to generate physical schema specifications from the logical schema specifications (with recommendations for memory allocation, indices, buffer size, blocking factors, etc.). The input parameters comprise information about the quantity structure, the required time behavior, and-referring to certain processing items-the required data storage or distribution, and the length and number of the records to be processed.
    SSD13.F.2 Completeness of the physical schema specifications It is guaranteed that all elements of the relevant logical schema specifications are transformed into the physical schema specification.
    SSD13.F.3 Accepting integrity conditions It is guaranteed that during the generation of physical schema specifications the integrity conditions contained in the logical schema specifications are integrated into the physical schema specifications. The requirement refers in particular to the fact that the possibly required syntax for corresponding integrity conditions is also generated in the physical schema specification.
    SSD13.F.4 Generation of procedure code It is possible to generate the procedure code required for the database installation from the logical schema specifications.
    SSD13.F.5 Version compatibility The generated physical schema specifications have to take into consideration the performance factors of the current database versions.
    New versions of commercial database systems usually offer improved performance and versatility, as the option to formulate differentiated integrity conditions. In most cases this requires an adjustment of the corresponding tools that are applied to generate physical schema specifications.
    SSD13.F.6 Consideration of performance factors The generated physical schema specifications have to take into consideration all performance factors for which the logical schema specifications or their descriptions contain sufficient user presettings.
    The requirement also means that the possibly required syntax for the physical schema specifications are generated as well, including the database description commands for the generation of indices and proposals for the required memory layout and the corresponding memory allocation.

    3.4 Other Requirements

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