- Please do NOT submit a copy of your deliverable for every member of the group. Only ONE COPY FOR EACH GROUP should be submitted by one of the members of the group on or before the due date through Moodle.
- Please submit a single file (doc or pdf) with all your material (text, figures, images etc.).
- Please make sure that you write the Course and Section number, the name of the group members and the group number clearly on the first page of your deliverable.
Deliverable 1 must contain an analysis of the intended database system, and a conceptual schema. It must describe the problems encountered in this phase and justify the solutions.
What is expected:
- Outline the goals of this phase of the project.
- Analyze the entire application for the Online Hotel Reservation System and come up with an extended ER diagram. Use the notation for E/R model constructs and additional notation for specialization/generalization hierarchies we learned in class.
- Show entity types, relationship types (including class/subclass relationship types), and attributes. Show different types of attributes (simple/composite, single-valued/multivalued, stored/derived) if needed. Show roles on recursive relationship types.
- Show key attributes (only one key per entity type should be shown on the ER diagram).
- Include structural constraints (cardinalities ratio and participation constraints). Use both notations for the constraints of relationship types on the diagram as an exercise (the traditional one and the (min, max) notation).
- Use some diagram editor to draw a clean diagram.
- Mention any assumptions you made in doing the above that go beyond what is given in the project description. In particular, mention all assumptions that led you in determining structural constraints.
- Make a list of constraints that apply over and above what you can show in the diagram. In particular make a list of additional keys for entity types (if there are any).
- Besides the above, comment on the difficulties you faced in doing this conceptual design task.
NOTE: The above specification will drive your subsequent phases. As in any actual design and implementation, you will be revising what you do here as you proceed through the phases. Please be explicit and detailed when writing your deliverable. This will help you in the long run!