Deliverable: Data Warehouse Physical Data Models

Physical Data Models of the data warehouse include models for the landing area, the staging area and the base data area. Physical data models include:

· Physical data schema.

Derived from the Entity Relationship Diagram for the logical data model.

· Organization and addressing techniques.

For databases that allow the specification of the organization of the index tables, this is the organization technique, such as b-tree, or hashed. For data tables, this indicates whether the table is indexed.

· Data access paths.

The primary and secondary keys available.

· Integrity rules.

The constraints on the data tables. Where possible, these are implemented as stored procedures, e.g., if the employee salary amount is set to zero then the employee must be in a non-active status.

· Physical location of database data elements and information.

Whether specialized storage, for example, mass storage, is used for the table.

Describe Design

Describe any particularly complex file relationships and access schemes. Document major decisions about the data structures and the reasons for the decisions. Describe guidelines for use of the data model, for example the locking and release of data items that the application accesses.

Size and Format

Most of this deliverable will be documented in the CASE tool. If possible, most of this detail should not be printed. If reports must be printed or a CASE tool is not used, be as concise as possible, while still conveying the critical details of the model. Use approximately one page per database entity or object.

ACTIVITY - DEFINE AND DESIGN CONVERSION PROCEDURES

To define the approach and procedures for converting data from the old to the new system and determine which conversion procedures to automate. Both manual and automated procedures are defined.

ACTIVITY - DEFINE DATA CONVERSION PROCEDURES

To define the procedures for converting data from the old to the new system. Each defined procedure is reviewed to determine which procedures to automate. Both manual and automated procedures are defined.

Disclaimer: Blog contents express the viewpoints of their independent authors and
are not reviewed for correctness or accuracy by
Toolbox for IT. Any opinions, comments, solutions or other commentary
expressed by blog authors are not endorsed or recommended by
Toolbox for IT
or any vendor. If you feel a blog entry is inappropriate,
click here to notify
Toolbox for IT.