1. Create an ER model for each of the following descriptions: (a) Each Company operates four Departments, and each Department belongs to one Company. (b) Each Department in part(a) employs one or more Employees, and each Employee works for one Department with a startdate. (c) Each of the Employees in part (b) may or may not have one or more Dependents, and each Dependent belongs to one Employee. (d) suppose: Company with attributes cnumber, cname, caddress, President. Department with attributes dname, dnumber, location. Employee with attributes ename, ssn(for social security number), Sex, address, salary, birthdate. Dependent with attributes dpName, Sex, birthdate, and relationship (to the employee). (e) Represent all the ER diagrams described in (a), (b), (c) and (d) as a single ER diagram. 2. Create an logical data model for relational database of the above designed ER model. Note:1) An logical data model is collection of relational schemas; 2) A relational schema is : tablename(attributename1, attributename2,..., attributenameN). 3. Create a database "Company"; Create each table of the above logical data model into the Company database. 4. Insert at least 3 records into each table of above Company database.

1. Create an ER model for each of the following descriptions: (a) Each Company operates four Departments, and each Department belongs to one Company. (b) Each Department in part(a) employs one or more Employees, and each Employee works for one Department with a startdate. (c) Each of the Employees in part (b) may or may not have one or more Dependents, and each Dependent belongs to one Employee. (d) suppose: Company with attributes cnumber, cname, caddress, President. Department with attributes dname, dnumber, location. Employee with attributes ename, ssn(for social security number), Sex, address, salary, birthdate. Dependent with attributes dpName, Sex, birthdate, and relationship (to the employee). (e) Represent all the ER diagrams described in (a), (b), (c) and (d) as a single ER diagram. 2. Create an logical data model for relational database of the above designed ER model. Note:1) An logical data model is collection of relational schemas; 2) A relational schema is : tablename(attributename1, attributename2,..., attributenameN). 3. Create a database "Company"; Create each table of the above logical data model into the Company database. 4. Insert at least 3 records into each table of above Company database.

Database Systems: Design, Implementation, & Management

11th Edition

ISBN:9781285196145

Author:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel

Publisher:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel

Chapter5: Advanced Data Modeling

Section: Chapter Questions

Problem 8RQ: According to the data model, is it required that every entity instance in the PRODUCT table be...

See similar textbooks

Similar questions

For each of the following collection of entities, give the assumptions concerning the relationship between entities and attributes. EMPLOYEE(EMP_NUM, EMP_LNAME, EMP_INITIAL, EMP-DOB) DEPENDENT(EMP_NUM, DEP_NUM, DEP_FNAME, DEP_DOB)
Make the entity-relationship model in Luicdchart for the following case: In the company Tecno1818 it is necessary to carry out an inventory of the products that are handled, for this the following information is available. Each product has a code, name, price and a manufacturer code. For the manufacturer you have the code and name
Consider the ER diagram shown in Figure 3.22 for part of a BANK database. Each bank can have multiple branches, and each branch can have multiple accounts and loans. a. List the names of all relationship types, and specify the (min, max) constraint on each participation of an entity type in a relationship type. Justify your choices. b. Suppose that every customer must have at least one account but is restricted to at most two loans at a time, and that a bank branch cannot have more than 1,000 loans. How does this show up on the (min, max) constraints?
Create an Entity-Relationship Model to represent the data requirements of the problem given below. Specify the cardinalities of relationships and all-important constraints. Also mention the assumptions if you have made any. [20 Marks] A person can be an employee, alumnus or a student. For person P_id (identifier), date of birth, gender and contacts are stored. Person can have more than one contact numbers and there are no other types of person that exists. An instance of person can belong to more than one type. Date hired and salary is the unique attributes of employee. For alumnus degree is required to be stored that comprises of year and designation. Major department is the attribute of student. A student can be a graduate student or an undergraduate student but not both at the same time. No other type of student exists. For graduate student test score is stored and for undergraduate student class standing is stored. Employee can be faculty, staff or others but not both at the same…
Create an Entity-Relationship Model to represent the data requirements of the problem given below. Specify the cardinalities of relationships and all-important constraints. Also mention the assumptions if you have made any. A person can be an employee,alumnus or a student.For person P_id(identifier), date of birth,gender and contacts are stored. Person can have more than one contact numbers and there are no other types of person that exists.An instance of person can belong to more than one type.Date hired and salary is the unique attributes of employee.For alumnus degree is required to be stored that comprises of year and designation. Major department is the attribute of student. A student can be a graduate student or an undergraduate student but not both at the same time.No other type of student exists.For graduate student test score is stored and for undergraduate student class standing is stored.Employee can be faculty, staff or others but not both at the same time. For faculty…
Create an Entity-Relationship Model to represent the data requirements of the problem given below. Specify the cardinalities of relationships and all-important constraints. Also mention the assumptions if you have made any. A person can be an employee, alumnus, or a student. For a person, P_id (identifier), date of birth, gender, and contacts are stored. A person can have more than one contact number and there are no other types of person that exist. An instance of a person can belong to more than one type. Date hired and salary is the unique attributes of the employee. For alumnus, the degree is required to be stored that comprises of year and designation. The major department is the attribute of the student. A student can be a graduate student or an undergraduate student but not both at the same time. No other type of student exists. For graduate student test score is stored and for undergraduate student class standing is stored. Employees can be faculty, staff, or others but not…
answer should be handwritten and the ER MODEL should be be completeDraw the Entity Relationship Diagram (ERD) with appropriate mapping cardinalities for the following scenario, Patients are treated in a single ward by the doctors assigned to them. Healthcare assistants also attend to the patients; a number of these are associated with each ward. Each patient is required to take a variety of drugs a certain number of times per day and for varying lengths of time. The system must record details concerning patient treatment and staff payment. Some staffs are paid part time and doctors and healthcare assistants work varying amounts of overtime at varying rates, the system will also need to track what treatments are required to what patients
Applying your knowledge in Enhanced Entity Relationship modeling, Develop an EER model for the following situation: A person may be employed by one or more organizations and each organization may be the employer of one or more persons. An organization can be internal organizational unit or an external organization. For persons and organizations, we want to know their ID, name, address and phone number. For persons we want to know their birthdate, and for organizations, we want to know their budget number. For each 6 employment, we want to know the employment date, termination date and bonus. Employment of a person by an organization may result in the person holding many positions over time. For each position, we know its title, and each time someone holds that position, we need to know the start date and termination date and salary. An organization is responsible for each position. It is possible for a person to be employed by one organization and hold a position for which another…
Consider the scenario described by the statement "A customer can make many payments, but each payment is made by only one customer." Use this scenario as the basis for an entity relationship diagram (ERD) representation.
Create an Entity Relationship diagram (ERD) for the following scenario indicating the identifiers and cardinality constraints. A division operates many departments, but each department is operated by only one division. Each division must have at least one department and each department must belong to a division. A department employs many employees, but there may be a department with no employees. Division is characterised by Divisionid and Divisionname and the attributes of department include Deptid and Deptname. Majority of employees called “dept_emps” are employed by a department. However, there are also employees known as “free_lance_emps” who are not assigned to any department. A department may own many projects, but there may be a department with no projects. Employee is characterised by empid, empname, emptype and address. Both dept_emps and free_lance_emps can work on many projects, but there are employees who do not work on any project. A project has at least one employee…
Can you identify what each weak entity in this diagram
An entity in A is associated with at most one entity in B. An entity in B, however, can be associated with any number (zero or more) of entities in A. What is the cardinality ratio? a. one to many b. many to one c. one to one d. many to many

Recommended textbooks for you

Database Systems: Design, Implementation, & Manag…

Computer Science

ISBN:

9781285196145

Author:

Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel

Publisher:

Cengage Learning

Database Systems: Design, Implementation, & Manag…

Computer Science

ISBN:

9781305627482

Author:

Carlos Coronel, Steven Morris

Publisher:

Cengage Learning

Database Systems: Design, Implementation, & Manag…

Computer Science

ISBN:

9781285196145

Author:

Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel

Publisher:

Cengage Learning

Database Systems: Design, Implementation, & Manag…

Computer Science

ISBN:

9781305627482

Author:

Carlos Coronel, Steven Morris

Publisher:

Cengage Learning

SEE MORE TEXTBOOKS