Database Concepts (7th Edition)
7th Edition
ISBN: 9780133544626
Author: David M. Kroenke, David J. Auer
Publisher: PEARSON
expand_more
expand_more
format_list_bulleted
Concept explainers
Expert Solution & Answer
Chapter 4, Problem 4.17RQ
Explanation of Solution
IE Crow’s Foot E-R diagram:
IE is information engineering and it uses crow’s feet to denote many side of relationship. Hence it is referred as IE Crow’s feet ER diagram.
IE Crow’s Foot E-R diagram for the entities DEPARTMENT and EMPLOYEE:
Explanation:
- The “Department” entity contains an attributes of “Dep_Name”, “Dep_ID”, and “Dep_Location”...
Expert Solution & Answer
Want to see the full answer?
Check out a sample textbook solution
Students have asked these similar questions
Draw an ER-Diagram for this situation and place minimum and maximum cardinalities on the diagram?
Entity type:
• EMPLOYEE with attribute: EmpID , Name (Firstname :besan, Lname) , Address :Amman, Birth_of_Date25/5/02 .
• DEPARTMENT with attribute : DeptID , DeptName , Loc
Relationship:
Works_in Relationship between EMPLOYEE and DEPARTMENT and each employee is works in zero or many department and each department worked by one or many employee.
draw an E-R diagram that indicates the entity sets and their attributes. Identify and label significant relationship sets between pairs of entities, the degree of relationship sets and the cardinality and participation constraints.
Create an ER DIAGRAM that shows relationship between eachother and post the picture please .
An Inventory entity can be associated with zero or many Beer entities.
A Beer entity can be associated with one and only one Inventory entity.
An Inventory entity can be associated with zero or one Brewery entity.
A Brewery entity can be associated with zero or many Inventory entities.
An Employee entity can be associated with one and only one Brewery entity.
A Brewery entity can be associated with zero or many Employee entities.
An Employee entity can be associated with zero or many Order entities.
An Order entity can be associated with one and only one Employee entity.
These business rules assume that a brewery company has an inventory of beers, which are brewed by one or more breweries and supplied by one or more suppliers. The breweries employ one or more employees and can receive orders for their beers.
Chapter 4 Solutions
Database Concepts (7th Edition)
Ch. 4 - Prob. 4.1RQCh. 4 - Prob. 4.2RQCh. 4 - Prob. 4.3RQCh. 4 - What is a use case, and what is its purpose?Ch. 4 - Give an example of a data constraint.Ch. 4 - Prob. 4.6RQCh. 4 - Define the term entity, and give an example other...Ch. 4 - Explain the difference between an entity class and...Ch. 4 - Define the term attribute, and give examples for...Ch. 4 - Define the term identifier, and indicate which...
Ch. 4 - Prob. 4.11RQCh. 4 - Prob. 4.12RQCh. 4 - Prob. 4.13RQCh. 4 - Prob. 4.14RQCh. 4 - List and give an example of the three types of...Ch. 4 - Prob. 4.16RQCh. 4 - Prob. 4.17RQCh. 4 - Prob. 4.18RQCh. 4 - Define the term weak entity, and give an example...Ch. 4 - Explain the ambiguity in the definition of the...Ch. 4 - Define the term associative entity, and give an...Ch. 4 - Define the terms supertype, subtype, and...Ch. 4 - What is an exclusive subtype relationship? Give an...Ch. 4 - What is an inclusive subtype relationship? Give an...Ch. 4 - Prob. 4.25RQCh. 4 - Prob. 4.26RQCh. 4 - Prob. 4.27RQCh. 4 - Prob. 4.28RQ
Knowledge Booster
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.Similar questions
- Data modelling is most often accomplished through the use of a(an) ________________. a. entity-relationship diagram b. data-flow diagram c. functional decomposition diagram d. activity diagramarrow_forwardDraw an E-R diagram for a patient appointment system. Consider the entities patient, patient appointment, doctor, prescription,and pharmacy. Identify and depict the cardinality of each relationship. Also identify the attributes and candidate key of each entityarrow_forwardDesign the Entity Relationship Diagram (ERD) showing entities, attributes, primary key and relationship cardinality for the following scenario. Any employee works for only a department and under supervision of a manager (where manager is also an employee). Employee's address, city code & city name also has been recorded. Every employee may work for multiple project, but an employee may be on vacation and not assigned to any projects. Working hour may be different for an employee for different projects. Projects are broken into tasks; A task is created for one project and assigned to one department. Requisitions are made for projects; Each requisition could ask for any number of items; Items could be: equipment item or materials item and are coded in a similar way; Each requisition is for one project and is made to one supplier. The important data fields are employee_id, employee_name ,employee_address, employee_email, department_id, department_name, location, city_code, city_name,…arrow_forward
- Use ER Assistant to draw your diagram. Draw a generalization hierarchy containing Employee, Administrator, and Faculty entities. The Employee entity is the supertype, and the Administrator and Faculty entities are the subtypes. The Employee entity has attributes as follows: EmpNo (primary key), EmpName, and EmpAddress. The Administrator entity has attributes as follows: AdmTitle, AdmContractLength The Faculty entity has attributes as follows: FacTenure, FacRank The generalization hierarchy should be disjoint but not complete.arrow_forwardDraw an Entity relationship diagram (ER) for a university according to the following rules: +-- For each student the university needs to keep track of: first name, last name, student id, address, phone no and their major. - The student id is identical for each student. -- Each course has a number, name and credit. The course number is unique for each course. + -- Each department has a name, code and location. The code is unique for each department. - Each course may has one or more sections where each section is belong to only one course. -- A department offers one or many courses. 7- Some courses have perquisite courses. 8- Each student could register in one or more courses. In your diagram you need to show the following: 1- The primary key for each entity. 2- The cardinality and participation between entities.arrow_forwardDraw an Entity relationship diagram (ER) for a university according to the following rules: ‐ For each student the university needs to keep track of: first name, last name, student id, address, phone no and their major. ‐ The student id is identical for each ‐ Each course has a number, name and credit. The course number is unique for each course. ‐ Each department has a name, code and The code is unique for each department. ‐ Each course may has one or more sections where each section is belong to only one ‐ A department offers one or many 7-‐ Some courses have perquisite courses. 8-‐ Each student could register in one or more courses. In your diagram you need to show the following: 1-‐ The primary key for each entity. 2-‐ The cardinality and participation between entities.arrow_forward
- Use the following business rules to create a Crow’s Foot Entity Relationship Diagram. Write all appropriate connectivities and cardinalities in the ERD. Add other linking entities as needed. • A department employs many employees, but each employee is employed by one department. • Some employees, known as “rovers,” are not assigned to any department. • A division operates many departments, but each department is operated by one division. • An employee may be assigned many projects, and a project may have many employees assigned to it. • A project must have at least one employee assigned to it. • One of the employees manages each department, and each department is managed by only one employee. • One of the employees runs each division, and each division is run by only one employee.arrow_forwardDesign an Enhanced Entity Relationship diagram (EERD) by referring the below given scenario. Use appropriate notations and names to draw the diagram. Scenario All EMPLOYEESs working in the University of Technology and Applied Sciences are grouped into ACADEMICS and ADMIN_STAFFs. An Admin_staff cannot be considered as Academics. An Employee is Identified with a EmpCode, Academic is having a specific attribute Degree and a Status is assigned to an Admin_Staff. Some of the Academics are further classified as LECTURER and PROFESSOR. LrsCode is a specific attribute for a Lecturer and PrfCode is a specific for a Professor. Lecturers can be considered as Professors after a few years of experience.arrow_forwardDesign a system to track advance payments made to employees. Use uml diagrams and design patterns in this system. The design steps will be as follows. Step 1 - Prepare an analysis document on the given topic. Step 2 - Create a Use case diagram for your requirement that contains at least 3 actor, 10 use case and use all relationship type Step 3 - Create an activity diagram for requirement Step 4 - Create a class diagram for all requirement that contains at least 10 class, necessary relations and types. Add the important attributes of the classes to the model. Step 5 - Use three design patterns, at least one creation, one structural, and one behavioral pattern, integrated into your classroom design. Step 6 - Code one of the design patterns you use with java. Note: The design should be homogenate. Excessive usage of any property type, object type, or function type is not suitable. For example, for creating 10 relations between classes, the number of relation types for aggregation,…arrow_forward
- Draw an Entity Relationship Diagram (ERD) using Unified Modelling Language (UML) notationaccording to the below business rules. Your design should be at the logical level – include primaryand foreign key fields and remember to remove any many-to-many relationships.Sheep farm feed supplier business rules:• All entities must have surrogate primary keys.• A contact person represents one or more suppliers, and each supplier has exactly onecontact person.• A supplier supplies many feed products, and every feed product can be supplied by manysuppliers.• Each feed product belongs to a specific feed type, and many feed products can have thesame feed type.arrow_forwardFor each entity, there needs to be an indication of whether it is one-to-one, one-to-many or many-to-many relationship. Here are the answers I have but I could use more guidance with it. I struggle with this type of question. BOOK and BOOK COPY (1:1) COURSE and COURSE-SECTION (M:N) COURSE-SECTION and ROOM (M:1) INSTRUCTOR and COURSE (1:M) ROOM and INSTRUCTOR (M:1)arrow_forwardDraw an Entity Relationship Diagram (ERD) using Unified Modelling Language (UML) notation according to the below business rules. Your design should be at the logical level – include primary and foreign key fields and remember to remove any many-to-many relationships. Business rules for hairdressers: 1. All entities should have surrogate primary keys. 2. Each hairdresser can work at multiple different salons over time, and every salon employs many different hairdressers. 3. The job title of a hairdresser at a specific salon must be stored in the database. 4. The name and surname of each hairdresser must be stored in the database. 5. The name of each salon must be stored in the database. 6. Every hairdresser is certified to have several different skills, and each skill can be mastered by many different hairdressers. 7. The name of each skill must be stored in the database. 8. The date that a specific hairdresser was certified to have a specific skill must be stored in the database.arrow_forward
arrow_back_ios
SEE MORE QUESTIONS
arrow_forward_ios
Recommended textbooks for you
Fundamentals of Information SystemsComputer ScienceISBN:9781305082168Author:Ralph Stair, George ReynoldsPublisher:Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:9781305082168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning