Due: Draft 9/5/2012, Final version 9/10/2012
Your first step is to analyze the domain you would like to manage with your database, and to construct an entity-relationship diagram for the data.
A good database always starts with a careful and thorough analysis of the problem domain and the logic behind the application. As a team, you should set up a meeting with your client to collect information about the client's needs. You should keep a detailed documentation of this information, which will be the basis for your design. Your should consider what entities should be part of the application and how they should be linked, what are the attributes of these entities and relationships. Your Entity-Relationship design should model every relevant aspect of the application in a logic and efficient way.
Specify an entity-relationship diagram for your design. As always, don't forget to underline key attributes and include arrowheads and rounded arrows indicating the multiplicity of relationships. If there are weak entity sets, indicate them by double lines, as described in class.
In order to catch problems at an early stage, each team is required to have their design reviewed by me. Please set up an appointment with me as soon as you have a draft of your diagram.
For this part of the project, each team will submit an entity-relationship diagram through class Moodle. The diagram should be drawn in Microsoft Visio, which is a component of MS Office and is available on College computers.