PRIDE ® -DBEM
Data Base Engineering Methodology
PHASE 4 - ENTERPRISE PHYSICAL DATA BASE DESIGN
ACTIVITY D - CREATE D.D.L. STATEMENTS

EXAMPLES   TOOLS & TECHNIQUES   FUNCTIONAL MATRIX   CHECKLIST   FORMS

TRANSLATE THIS PAGE TO... Chinese (simple)   Japanese       Dutch   French     German     Italian    
Free Translation courtesy of ALS      Chinese (traditional)   Korean       Portuguese       Russian       Spanish         

CONTENTS

This section contains the following:


 
    BUSINESS PURPOSE

    The purpose of this activity is to create the Data Definition Language and Data Communications Language statements necessary to implement and/or modify the affected portions of the EPDBM. It is executed by Data Base Administration and Data Communications Administration.  

    OVERVIEW

    The detailed design for each hardware/software combination was prepared in the previous activity and represented in the EPDBM. In this activity, each such design is translated into Data Definition Statements in the exact syntax required by the DBMS or file system being used.

    The role of Data Communications Administration in this activity is to create the statements necessary to implement the parts of the network design referring to the application at hand.

    When the statements are complete, they are executed and corrected if necessary in a test environment. If no production systems are currently using this section of the data base, the new structures can then be implemented in their final form. Actual data is not loaded into the data base until the corresponding ISEM project(s) reach the installation phase.

    If the modifications made in this activity affect parts of the data base which are shared by other systems, then the impacted systems must themselves be changed, probably as part of other ISEM projects, before the transition to the new data base is made. Depending on the degree of data independence of the DBMS used and the depth of the physical changes, these modifications can range from nothing at all to major projects.

    At the end of this activity, the EPDBM design or modification for a system is complete and tested for validity.

    PREPARING FOR REVIEW

    DBA/DCA assures that all of the Phase 4 activities and materials have been properly completed. A Phase Review Checklist is available for this purpose. A formal Phase 4, "EPDBM Design Manual" is then prepared. The manual is reviewed and checked by Quality Assurance prior to distribution to management for review.

    The Phase 4 Manual contains the following items:

    • Phase Cover Page - including a Table of Contents, along with a distribution/approval list.
    • EPDBM Narrative - as prepared in Activity C.
    • EPDBM Files Matrix - as prepared in Activity C.
    • EPDBM Records Matrix - as prepared in Activity C.
    • Data Resource Layouts - as prepared in Activity C.
    • ELDBM/EPDBM Files Matrix - as prepared in Activity C.
    • ELDBM/EPDBM Records Matrix - as prepared in Activity C.
    • ALDBM/EPDBM Files Matrix - as prepared in Activity C.
    • ALDBM/EPDBM Records Matrix - as prepared in Activity C.
    • Phase Review Checklist - specifying acceptance criteria for the deliverables mentioned above.
     

    STEPS IN EXECUTION

    1. Data Base Administration prepares the required file structure statements and tests them.

    2. Data Communications Administration prepares the required Data Communications Statements and tests them.

    3. DBA/DCA prepare a formal Phase 4 manual, "EPDBM Design Manual."

    4. Quality Assurance reviews the "EPDBM Design Manual" for consistency. DBA/DCA implement changes accordingly.

    5. DBA/DCA schedules a Phase 4 review meeting with Information Resource Management, Data Resource Management, Systems Resource Management, Data Engineering, and Project Management. Copies of the "EPDBM Design Manual" are distributed to management prior to the review meeting.

   


Copyright © 1971-2009 by M. Bryce & Associates
Palm Harbor, Florida, USA
All rights reserved.