Initial Conceptual Design of the COMPANY Database



Rating - 4/5
451 views

We can now define the entity types for the COMPANY database, based on the requirements described . After defining several entity types and their attributes here, we refine our design  after we introduce the concept of a relationship. According to the requirements listed , we can identify four entity types—one corresponding to each of the four items in the specification:

These Topics Are Also In Your Syllabus  Initial Conceptual Design of the COMPANY Database
1 Types of Operating Systems - Batch operating system, Time-sharing systems, Distributed OS, Network OS, Real Time OS link
2 Set Operations-Introduction link
You May Find Something Very Interesting Here.  Initial Conceptual Design of the COMPANY Database link
3 Null Values link
4 Aggregate Functions link
5 Types Of Systems link

1. An entity type DEPARTMENT with attributes Name, Number, Locations, Manager, and Manager_start_date. Locations is the only multivalued attribute. We can specify that both Name and Number are (separate) key attributes because each was specified to be unique.

These Topics Are Also In Your Syllabus  Initial Conceptual Design of the COMPANY Database
1 Types of Operating Systems - Batch operating system, Time-sharing systems, Distributed OS, Network OS, Real Time OS link
2 Nested Subqueries link
You May Find Something Very Interesting Here.  Initial Conceptual Design of the COMPANY Database link
3 Nested Subqueries link
4 Modification of the Database link
5 Types Of Systems link

2. An entity type PROJECT with attributes Name, Number, Location, and Controlling_department. Both Name and Number are (separate) key attributes.

These Topics Are Also In Your Syllabus  Initial Conceptual Design of the COMPANY Database
1 Types of Operating Systems - Batch operating system, Time-sharing systems, Distributed OS, Network OS, Real Time OS link
2 Control Measures link
You May Find Something Very Interesting Here.  Initial Conceptual Design of the COMPANY Database link
3 Set Operations-Introduction link
4 Null Values link
5 Types Of Systems link

3. An entity type EMPLOYEE with attributes Name, Ssn, Sex, Address, Salary, Birth_date, Department, and Supervisor. Both Name and Address may be composite attributes; however, this was not specified in the requirements. We must go back to the users to see if any of them will refer to the individual components of Name—First_name, Middle_initial, Last_name—or of Address.

These Topics Are Also In Your Syllabus  Initial Conceptual Design of the COMPANY Database
1 Types of Operating Systems - Batch operating system, Time-sharing systems, Distributed OS, Network OS, Real Time OS link
2 Nested Subqueries link
You May Find Something Very Interesting Here.  Initial Conceptual Design of the COMPANY Database link
3 Nested Subqueries link
4 Modification of the Database link
5 Types Of Systems link

4. An entity type DEPENDENT with attributes Employee, Dependent_name, Sex, Birth_date, and Relationship (to the employee).

These Topics Are Also In Your Syllabus  Initial Conceptual Design of the COMPANY Database
1 Types of Operating Systems - Batch operating system, Time-sharing systems, Distributed OS, Network OS, Real Time OS link
2 Schema Diagrams link
You May Find Something Very Interesting Here.  Initial Conceptual Design of the COMPANY Database link
3 Relational Query Languages link
4 Relational Operations link
5 Types Of Systems link

 

 Initial Conceptual Design of the COMPANY Database

So far, we have not represented the fact that an employee can work on several projects, nor have we represented the number of hours per week an employee works on each project. This characteristic is listed as part of the third requirement, and it can be represented by a multivalued composite attribute of EMPLOYEE called Works_on with the simple components (Project, Hours). Alternatively, it can be represented as a multivalued composite attribute of PROJECT called Workers with the simple components (Employee, Hours). We choose the first alternative in Figure ., which shows each of the entity types just described. The Name attribute of EMPLOYEE is shown as a composite attribute, presumably after consultation with the users.


Rating - 4/5
525 views

Advertisements