By the end of this class, the student should be able to: ¶

• Develop the relational schema from the conceptual schema. ¶
• Ensure that the relational schema is in the Boyce-Codd normal form (BCNF). ¶
• Document the relational database schema. ¶

• Present the artefact A4 (Conceptual Data Model). ¶
• Map the classes and relationships of the conceptual schema into relation schemas. ¶
• For each relation, identify the functional dependencies (FD) that apply. ¶
• If the relation is not in BCNF and there are no other impediments, look for several possible decompositions (lossless) in relations in BCNF and choose the “best decomposition” (which preserves more dependencies, that makes more sense, etc. ). ¶
• If there is no satisfactory decomposition to BCNF and if the relation is no longer in 3NF, consider the decomposition lossless for 3NF, preserving the functional dependencies. ¶

• Test the local PostgreSQL setup and the connection to the production PostgreSQL server. ¶

• Database Specification Component ¶
  • EBD Component | EBD Template (GitLab Wiki) ¶
  • A5. Relational Schema, Validation and Schema Refinement ¶

• MediaLibrary Example ¶
  • A5. Relational Schema, Validation and Schema Refinement ¶

• Scott W. Ambler, UML 2 Class Diagrams: An Agile Introduction ¶
• UML Class and Object Diagrams Overview ¶
• Summary of Mapping Rules from Logical UML Models to Relational Schemas (PT) ¶

• LBAW Computational requirements ¶
• Computational Resources > PostgreSQL for Data Persistence ¶
• Template PostgreSQL ¶

• Develop and discuss the relational schema. ¶
• Normalize and refine the relational schema. ¶
• Continue the development of the EBD component. ¶

« Previous | Index | Next » ¶