|
|
 |
Information and Communications
Technology Qualifications
| Back to list of Prescriptions
| Prescription: DA600 (DA200)Data Analysis |
| Aim of Module | To enable students to build a data model and become familiar with the normalisation process.
|
| Credits | 7
|
| Student Learning hours | 70
|
| Content Revised | 2000
|
| Prescription Expiry Date | Nov 2005
|
LEARNING OUTCOMES
The Student Will
| | | | | A | 1 | Design a data model for a simple organisation. | | | | | A | 2 | Perform Relational Data Analysis resulting in data being expressed in third normal form. | | | | | A | 3 | Consolidate entities in the data model, removing redundancies. |
CONTENT
| | | | > | Draw a Data Model including: | | | - | Relationships between entity types | | | - | Types of relationships in terms of cardinality, optionality, exclusivity and involution | | | - | Attributes of entity types | | | | | > | Explain the design of unique identifiers | | | - | Including candidate keys, primary keys, composite keys, foreign keys.
|
top
| | | | > | Expressing information in unnormalised logical form and identifying keys. | | | | | > | Converting the unnormalised data to first, second and third normal form, testing resulting relations at each stage. | | | | | > | Define further normal forms.
|
top
| | | | > | Comparison of 3NF relations against the data model; removal of redundant entity types and relationships, resulting in a Normalised Data Model.
|
top
| | | | Note | | > | Some authors refer to a data model as an entity relationship diagram and/or entity model. |
|
|
