![]() The table instances (records) should look reasonable.į. Insert at least 10 records into each table. Insert records to your tables and create reasonable queries for your application.Į. Convert the E-R diagram into a relational database schema. The ER model should be self-explainable or with some necessary explanations for unclear notations in the model.ĭ. That is a formal modeling the database requirements. Again, make your relationships realistic and meaningful. Construct an E-R diagram, which will reflect your choice of the entity sets, their relevant attributes, and the relationships among them. In addition, don't make too many simplifying assumptions.Ĭ. Do not discuss something that is obvious (e.g., that a student can take several courses). You may have some reasonable assumptions for your application. Here you need to give the database requirements in natural language: talking about entities, attributes, keys, the nature of relationships between entities, any constraints, etc. As a general guideline, you should probably have about five to eight entity sets and similar number of relationships sets in an ER model.ī. Anyway, you should be familiar with the domain in order to have a professional design. Begin by choosing an application domain, e.g., the database for a local volleyball league or the database for a Society of Coffee Fans. You are required to select a domain (EXPERT TO DECIDE) which you are familiar with, then translate the theoretical concepts into the terms of a concrete DBMS to implement the database using MySQL Workbench (preferable).Ī. This is the forth attempt already and still contains missing answers.ĮXAMPLE OF HOW A DIAGRAM SHOULD LOOK LIKE: Please label your answers to the questions accordingly. Appreciate your effort over this project!
0 Comments
Leave a Reply. |