Reference no: EM132983648

ACIS 5504 Database Development - Virginia Polytechnic Institute and State University

Entity Relationship and Relational Models

This milestone involves creating an Entity Relationship model and a data dictionary that implements that model for a simple business situation. For this milestone you will begin by understanding the business situation and the user requirements, then design a data based to be implemented in the next milestone.

Business Situation for Project
The business situation for the project is that of Global Computer Solutions (GCS). The detailed description of the business situation is problem 11 in chapter 5 and is presented on pages 195-200 of the textbook. The assignment activities that you must complete are presented below.

(Note: Ignore the last paragraph on page 200 beginning "Your assignment is.... ", the only activities you must complete for this milestone are listed below and detailed in the milestone 2 and 3 requirements).

Project Requirements

Complete the following activities:
- Write a description of the business situation suitable to convince users and managers you understand the problem from their perspective. (1-2 pages) (5 points)
- Create an ER model for this business situation. Your model should include only entities and relationships, no attributes. You may use either Crow's Foot notation similar to Figure 4.35 or UML notation similar to Figure 4.37. Whichever notation you use, be sure to label your relationships in both directions as shown in Figure 4.37, Department "offers" 0:M Courses and one Course is offered by" 1:1 Department. In addition, you must include intersection entities that implement the M:N relationships in your model.

- Create a data dictionary for your ER model. All attributes including keys and foreign keys must be identified. Use these naming conventions for tables and attributes in your data dictionary. Entity names should match problem the domain and be understandable to users of the system. Attributes uses as keys or foreign keys being with c_, other attributes begin with letters that indicate their data type including, t_ for text d_ for date, n_ for numbers with decimal places, i_ for integers, b_ for boolean, etc. Attributes should also have a two charcter suffix derived from the table name, e.g., _cu for a customer table. The primary key of the customer table would be something like c_customer_cu, the date of first order by the customer might by d_firstOrder_cu, and the current balance would be n_currentBalance_cu. This file contains a sample data dictionary

Attachment:- Entity Relationship and Relational Models.rar