DATABASE AND CLIENT/SERVER APPLICATIONS

ASSESSMENT 02 ER DIAGRAMS
NAME: JAIME SALATHIEL PEJAY BAUTISTA INSTRUCTIONS 1. Use the word processor on the computer to fill in this assessment. 2. Start by inserting your name in the space above. 3. After reviewing these questions, save this file with your answers to your computer using the required file name format: <YourStudentID> Assessment02.doc where <YourStudentID> is your StudentID and there is a blank between it and the Assessment02. When you are finished with the assessment, save the document again and then upload it to the LMS. 4. Click the Choose File button. 5. Locate the file for attachment. 6. Once the file is attached, click Upload File. ASSESSMENT QUESTIONS Using Figure 7.2 from Fundamental of Database Systems, identify the following concepts in the ER schema diagram by name of entity and attribute, e.g., DEPARTMENT.Name. Worth 7 points each. 1. 2. 3. 4. 5. 6. 7. 8. 9. The attributes for PROJECT: PROJECT.Name, PROJECT.Number, and PROJECT.Location. A composite attribute: MPLOYEE.Name. A multi-valued attribute: DEPARTMENT.Locations The key attributes for PROJECT: PROJECT.Number and PROJECT.Name The relationship types: WORKS_FOR, MANAGES, WORKS_ON, DEPENDENTS_OF, SUPERVISION A derived attribute: DEPARTMENT.Number_of_employees A weak entity: DEPENDENT Identifying relationship of a weak entity: DEPENDENTS_OF A partial key of a weak entity type: DEPENDENT.Name

10. EMPLOYEE has a total participation in what relationship types: WORKS_ON and WORKS_FOR 11. EMPLOYEE has a partial relationship in what relationship types: MANAGES, DEPENDENTS_OF, SUPERVISION 12. A recursive relationship: SUPERVISION

Essay Answer. Worth 16 points. 13. There are two main reasons for including class/subclass relationships and specializations in a data model. Briefly describe each of the two. Certain attributes may apply to some, but not all, entities of the superclass. Some relationship types may participate in only by entities that are members of the subclass. The first is that certain attributes may apply to some but not all entities of the superclass. A subclass is defined in order to group the entities to which these attributes apply. The members of the subclass may still share the majority of their attributes with the other members of the superclass. The second reason for using subclasses is that some relationship types may be participated in only by entities that are members of the subclass.