Logical Data Design
The focus of logical data design is development of a Logical Data Model. This model represents CMS data within the scope of a system development project and shows the specific entities, attributes, and relationships involved in a business function's view of information.
NOTE: There are references within this section that refer the reader to the Operating Procedures and Guidelines section. Please download the Operating Procedures and Guidelines section to view these references.
The Logical Data Design process diagram depicts the milestones, control points, and deliverables as they occur during the following steps:
- Initiate Data Design Services
- Assess Data Design Needs
- Start the Project Logical Data Model from the EDM
- Extend the Project Logical Data Model
- Assign Data Information Security Categories
- Generate the Project Metadata Repository
- Validate and Approve the Project Logical Data Model
- Complete the Project Logical Data Model
Logical data design tasks are performed in the Requirements Analysis Phase and the Design & Engineering Phase of the CMS System Development Life Cycle (SDLC) as indicated in the CMS Integrated IT Investment & System Life Cycle Framework, which is available on the CMS Intranet. The same logical data design tasks are also required in alternative development methods.
The Logical Data Design process creates the following deliverables:
- Data Design Estimate,
- Conceptual Data Model,
- System Context Diagram,
- Project Metadata Repository,
- Data Issue Documents (where applicable),
- Logical Data Model,
- Data Architecture for Repository Update, and
- Proposed New EDM entries
Please refer to the download section to receive the complete documentation.
The focus of the New Model Review Procedure is to explain the steps to be followed and deliverables to be produced to ensure that a logical data model conforms to CMS logical data modeling standards. CMS Central Data Administration (CDA) performs new logical model reviews for application projects. CDA uses standard layouts to report the results of a review to the business owner and application development team. The standard review results report is created using a reporting feature in the Erwin data model. Various templates have been custom designed for each type of data model (logical only, physical only, and logical/physical). The templates for these reports, named Report Template Builder (.rtb) file, are referred to in the New Model Review Procedure document. The Report Template Builder (.rtb) includes a set of standard, preformatted data model report templates to be used for Erwin data model reporting.