RelationalDBDesign RelationalDBDesign



Database Analysis  «Prev  Next»
Lesson 4 Resources and Help page
Objective Database Course resources

Database Course Resources

Glossary

Throughout this course, you will have the opportunity to review definitions of key terms.
These terms are defined in the Relational Database Analysis - Glossary.
Each link the left hand navigation represents a module in the course.

Conduct a Current-State Analysis

This work stream should focus on assessing existing practices, management routines, and reporting and control processes. The results should clearly document data quality practices, key stakeholders, systems, and reporting.
It is important, during this exercise, that the team captures an initial set of issues that may be driving data quality. Any gaps and issues identifi ed in this effort will be accounted for during the execution of data quality projects.

Relational Database Analysis Store

The following book contains useful additional information with respect to database design.
DB Design for Mere Mortals

Exercise submissions

After completing some exercises, you will be required to cut and paste your source code into a text submission box and click on the submit button. Before beginning the next module which discusses relational constraints , let us take a quick overview with respect to what a relational model is.

What is A Data Model

A data model is a conceptual representation of the data structures that are required by a database. The data structures include the data objects, the associations between data objects, and the rules which govern operations on the objects. As the name implies, the data model focuses on what data is required and how it should be organized rather than what operations will be performed on the data. To use a common analogy, the data model is equivalent to the building plans of an architect.
A data model is independent of hardware or software constraints. Rather than try to represent the data as a database would see it, the data model focuses on representing the data as the user sees it in the real world. It serves as a bridge between the concepts that make up real-world events and processes and the physical representation of those concepts in a database.