ER Diagram
The second stage of the project is the development of an entity-relationship (ER) model for the database. This model will guide the development of your logical database design.
- Expected duration
- 4 hours
- Deadline
- 1645 on Lesson 15
- Points
- 50 points
Learning Objectives
- Create an ER model for the development of a real-world system
Help Policy
- Authorized Resources
- Any, except classmates working on other teams
- Notes
- Never copy another person’s work and submit it as your own.
-
You must document all help received from all sources, including the instructor and instructor-provided course materials (such as the textbook).
Assignment
Develop a complete ER diagram for your project. At a minimum, your diagram should include a half-dozen entities although more may be required depending on the scope of your project outlined in the proposal.
The diagram that you submit must be “professional” – i.e., you cannot scan a hand-drawn diagram or take a picture of a whiteboard. Many tools support the creation of ER diagrams; draw.io is freely available online as one example that you can use.
Submission
Submit your ER diagram using Blackboard. Include your documentation statement as part of your Blackboard submission.
If the tool used to create your ER diagram does not support the notation used in class or in the textbook (e.g., draw.io does not provide support for disjoint and overlapping constraints for specializations of entities), you must 1) indicate the deviation in your submission and 2) prove that you have thought about these issues by augmenting your diagram with a written description of what should appear. Including this information will waive grading penalties that might otherwise be imposed for these deviations but does not excuse “gross” violations, such as submitting a UML class diagram in lieu of a ER diagram.