Previous Next Functional Tool Requirements Homepage  
System Development Submodel  
SSD21 - Transforming Databases, Data Structures Backwards  

  LSE21 - Datenbanken, Datenstrukturen rückwärts transformieren

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

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

  • Data-Dictionary
  • SW Design (Database). Database Description
  • SW Design (Module). SW Component/SW Module Description

    • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools used to generate conceptual schema specifications from logical or physical schema specifications for Databases or files. Several conceptual schema specifications can be combined into a shared consistent conceptual schema specification.

    3 Requirements

    3.1 Requirements for Interfaces

    SSD21.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.
    SSD21.I.2 Input interface to SSD09 - Supporting Information Structuring It is possible to integrate information structures generated with SSD09 without further transformation from the object management in order to be utilized in the analysis of database and data structure descriptions.
    SSD21.I.3 Input interface to SSD11 - Supporting Database Specification It is possible to integrate logical schema specifications for databases and data structures generated with SSD11 without further transformation from the object management in order to be converted into information structures.
    SSD21.I.4 Input interface to SSD13 - Generating Databases It is possible to integrate physical schema specifications for databases and data structures generated with SSD13 without further transformation from the object management in order to be converted into logical schema specifications.
    SSD21.I.5 Output interface to SSD09 - Supporting Information Structuring It is possible to transmit information structures generated from logical schema specifications for databases and data structures to SSD09 without further transformation via the object management.
    SSD21.I.6 Output interface to SSD11 - Supporting Database Specification It is possible to transmit logical schema specifications for databases and data structures generated from physical schema specifications to SSD11 without further transformation via the object management.

    3.2 Requirements for the Methods Support

    none

    3.3 Requirements for Functions

    SSD21.F.1 Transformation of logical schema specifications into conceptual ones It is possible to transform a logical schema specification for databases into a conceptual schema specification.
    SSD21.F.2 Completeness of the transformation It is guaranteed that during the transformation of a logical schema specification into a conceptual schema specification all special, user-specific information about entity types, attributes, and relationship types available in the logical schema specification is transmitted into the conceptual schema specification.
    SSD21.F.3 Integrity conditions
    SSD20.F.3.1 Logical It is guaranteed that during the transformation of a logical schema specification into a conceptual schema specification all integrity conditions included in the logical schema specification are either transmitted into the representation of the conceptual schema specification or into the corresponding description.
    SSD20.F.3.2 Physical It is guaranteed that during the transformation of a physical schema specification into a conceptual schema specification all integrity conditions included in the physical schema specification are either transmitted into the representati0on of the conceptual schema specification or into the corresponding description.
    SSD21.F.4 Transformation of physical schema specifications into conceptual ones It is possible to transform physical schema specifications into conceptual schema specifications.
    SSD21.F.5 Completeness of the transformation It is guaranteed that during the transformation of a physical schema specification into a conceptual schema specification all special, user-specific information about entity types, attributes, and relationship types available in the physical schema specification is transmitted into the conceptual schema specification.
    SSD21.F.6 Integration of conceptual schema specifications It is possible to transmit generated conceptual schema specifications and to integrate them with existing conceptual schema specifications into a consistent conceptual schema specification.

    3.4 Other Requirements

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