Scenario 2: This is a simple list table of a company trying to keep track of employee assignment to company projects (in other words, not a database but a flat one table file). You will design a database for this company so that they won't be relying on a simple 1 table list system to keep track of their data. Looking at the table below, identify the separate entities and attributes and design a logical level Entity Relationship Diagram for this company. Project Project Name Project Project Employee Employee Department Department Hourly Code Manager Mr. Ajay Budget No. Name No. Name Rate PC010 Reservation 120500 S100 Mohan D03 Database 21.00 System РС010 Reservation Mr. Ajay 120500 S101 Vipul D02 Testing 16.50 System PC010 Reservation Mr. Ajay 120500 S102 Riyaz D01 IT 22.00 System HR System PC011 Mrs. 500500 S103 Pavan D03 Database 18.50 Charu PC011 HR System Mrs. 500500 S104 Jitendra D02 Testing 17.00 Charu PC011 HR System Mrs. 500500 S315 Роoja D01 IT 23.50 Charu PC012 Attendance Mr. 710700 S137 Rahul D03 Database 21.50 Rajesh System Attendance PC012 Mr. 710700 S218 Avneesh D02 Testing 15.50 Rajesh System Attendance PC012 Mr. 710700 S109 Vikas D01 IT 20.50 System Rajesh 1|Page

Scenario 2: This is a simple list table of a company trying to keep track of employee assignment to company projects (in other words, not a database but a flat one table file). You will design a database for this company so that they won't be relying on a simple 1 table list system to keep track of their data. Looking at the table below, identify the separate entities and attributes and design a logical level Entity Relationship Diagram for this company. Project Project Name Project Project Employee Employee Department Department Hourly Code Manager Mr. Ajay Budget No. Name No. Name Rate PC010 Reservation 120500 S100 Mohan D03 Database 21.00 System РС010 Reservation Mr. Ajay 120500 S101 Vipul D02 Testing 16.50 System PC010 Reservation Mr. Ajay 120500 S102 Riyaz D01 IT 22.00 System HR System PC011 Mrs. 500500 S103 Pavan D03 Database 18.50 Charu PC011 HR System Mrs. 500500 S104 Jitendra D02 Testing 17.00 Charu PC011 HR System Mrs. 500500 S315 Роoja D01 IT 23.50 Charu PC012 Attendance Mr. 710700 S137 Rahul D03 Database 21.50 Rajesh System Attendance PC012 Mr. 710700 S218 Avneesh D02 Testing 15.50 Rajesh System Attendance PC012 Mr. 710700 S109 Vikas D01 IT 20.50 System Rajesh 1|Page

Oracle 12c: SQL

3rd Edition

ISBN:9781305251038

Author:Joan Casteel

Publisher:Joan Casteel

Chapter1: Overview Of Database Concepts

Section: Chapter Questions

Problem 6HOA

See similar textbooks

Similar questions

You have been asked to design part of a database for a hospital. Thehospital managers provided you with an informal description of theirdata which you can find on the next page in Figure 1.(a) Provide an Enhanced Entity-Relationship Model for the hospital’s data model (Figure 1) in form of a diagram in Chen notation. Identify special attributes (including keys) in the diagramand include participation and cardinality constraint annotationsfor your relationships.List and explain any additional assumptions you think you haveto make because the specification was unclear or incomplete.Note that there should not be many such extra assumptions.Marking CriteriaThe following criteria will be used to mark your model:• extent to which your model is correct, minimal (no featuremodelled twice), complete and expressive• correct use of Chen notation (including special attributes)• correct cardinality and participation constraints (includingnotation)• readability and presentation of your answer. You…
Create an ER diagram that correctly describes the database for exams at Campus in Bäcksvängen in accordance with the following description: (Own assumptions must be clearly described.) Staff for various functions are involved in the exams. All staff have a full name and a unique staff code. Some people are examiners on one or more courses. A course has one name and one unique ladok code. For a course, you can add up its points based on the associated elements. One part is part of a course (for example an exam, a laboratory or project). A course can have several different parts. An element has a name, a description, a torque code, one point and two or more grades (eg: U, G, VG). An element can only belong to one course. Since the database is to process the exams, it is obvious that a part like described as an examination has an examination opportunity that is identified, among other things, by the date, start time, end time and that it is possible to calculate total writing time. A…
The crow's foot in a diagram a.) is only used to show N:M relationships. b.) shows the relationship between three entities. c.) indicates that more than one of that entity type can be involved in that relationship. d.) shows the minimum number of entities that can be involved in a relationship. When translating an ER model into database tables a.) each relationship is defined by a normal form. b.) each entity is represented with a table. D.) each relationship is represented with a table.
Create an ER model related to the following entities and relationships: Department, Student, Professor, Course, Section, Grade, Major. (For attributes inside each table, you only need to insert several reasonable attributes. No need to have a comprehensive list. For many-to-many relationship, you also need to insert one extra table to handle the many-to-many relationship. The final database design will have more tables than the number of entities listed above.) A given department can offer many courses. A given course can be offered by only one related department. A given course can have many related sections. A given professor can teach many sections. A given section can only be related to one course and taught by one professor. A given professor can have appointment with different departments A given department can have many professors. A given department can offer several majors. A given major can be offered by only one related department. A given student can have several majors. A…
These questions are in sequence and the previous question needs to be referred to answer the next question: This is the previous question that was askedQuestion 1(question to be answered at the end): Create the Entity-Relationship (ER) Diagram for the following scenario: We want to maintain a database for a Faculty within a multi-campus regional university. The faculty has a number of schools and each school is characterized by its school-code which is unique, name, and campus location. Schools employ professors who are characterized by their unique staff-id, name and the school they work for. A school offers courses that are characterized by their course-code which is unique, course name and the school. There are subjects offered within the faculty and these arecharacterized by unique subject-code, title and the school that offers them. Students enroll into courses that are characterized by student-id which is unique, name, address and phone.The following business rules apply• A…
Using er assistant create an Entity Relationship Diagram(ERD) with appropriate entries, relevant attributes, and relations to support the following business rules, and write a few lines to defend your erd. You need to design a database to keep track of clubs at a high school. Attributes: A student may only join one club Some students do not join at all Club needs to have one student Need to capture students: Name Address Year of grad All Phone numbers Club name Club advisor Meeting dates
You have been asked to design and implement a database for CTU, which includes 3 entities (tables), as follows: Students Faculty Courses Part 1 Create a Word document that includes the following: Identify at least 3 attributes for each entity, including the following: Student's entity should have an attribute for the program the student is enrolled in. Faculty should have an attribute identifying their rank. Properly identify all of the primary keys (use solid underlines). Create an entity relationship diagram (ERD) from the entities. You may use SmartDraw, Visio, Erwin, or even Word to draw the diagram. Take a screenshot (no need if you use Word), and insert it into the Word document. Part 2 Use Microsoft Access to implement the database that you designed in Part 1, and include the following: Create the Student, Faculty, and Course tables in Access. Add a few instances in each table. Create 2 queries for the following objectives: Find the student names for all students who are in the…
For this project you will choose a business or use the previously chosen business to design a database through thestages.Your business must meet the following requirements: It must have 2 or more master or parent tables It must have 3 or more child or transaction tables The project will include the following elements for the chosen business.1. Introduction and Overview of the database2. Identify the business rules of this business as it applies to the data3. Create an Entity Relationship Diagram in crow’s feet notation.4. Create a relational diagram using a 3 column crow’s feet diagram. Make sure you include all primary and foreignkeys and data types on all columns.5. Create a table in the lab document to identify the primary key for each entity.6. Explain and apply the integrity rules for each entity.7. Use a table in the lab document to define the relationships between each entity. Make sure you list thecardinality of the relationships.8. Create the database in SQLite.9. Show SQL…
Subject: Database Design UCSICafe is a coffee shop which set up in many countries such as Malaysia, Australia and New Zealand. UCSICafe has many employees, and these employees work for a department (headquarter or branches) which located in a country. For example, Michael Lee works as a finance manager in finance department which is located in Melbourne, Australia and Melbourne is the headquarter Important NoteYou are required to:1. use crow-foot notation in drawing entity relationship diagram; 2. include constraints and descriptions/assumption in your answer.
The project team at University of Kentucky is moving forward with the new Student Grading System. The information system will have three external entities, with the following data flows: Entity Data flow from the Entity Data flow to the Entity Student Tasks Submission Graded Tasks Student Records System Online attendance Final Grade Instructor Grading Parameters Grade Report Moreover, the respective information system will have four subsystems: Establish Gradebook, Assign Final Grade, Grade Student Work Produce Grade Report, and a data store called Gradebook. The data flows are as follows: Data Flow From To Class Roster Student Records System Entity Establish Gradebook Process Final Grade Assign Final Grade Process Student Records System Entity Final Grade Assign Final Grade Process Gradebook Data Store Grading Details Gradebook Data Store Assign Final Grade Process Submitted Work Student…
The project team at University of Kentucky is moving forward with the new Student Grading System. The information system will have three external entities, with the following data flows: Entity Data flow from the Entity Data flow to the Entity Student Tasks Submission Graded Tasks Student Records System Online attendance Final Grade Instructor Grading Parameters Grade Report Moreover, the respective information system will have four subsystems: Establish Gradebook, Assign Final Grade, Grade Student Work Produce Grade Report, and a data store called Gradebook. The data flows are as follows: Data Flow From To Class Roster Student Records System Entity Establish Gradebook Process Final Grade Assign Final Grade Process Student Records System Entity Final Grade Assign Final Grade Process Gradebook Data Store Grading Details Gradebook Data Store Assign Final Grade Process Submitted Work Student Entity…
Which of the following is a key part of conceptual design in an entity relationship model? This model resolves the many-to-many relationships to multiple one-to-many relationships. This model adds all of the attributes for each entity. This model converts attributes into columns. This model does not depend on the database management software or the hardware used to implement the model.