C1. “Nomadic Desert Camp, Oman" requires an Information System to maintain the details of the amenities provided by them to their tourists and the customers. The customer bill given below [Figure C1] is an example of a record used by them for booking the amenities. Draw an Entity Relationship Diagram. Your Entity Relationship Diagram (ERD) should show Entities, attributes, Key attributes, optionality, and cardinality. Also consider the following points for developing relationships: i. A customer can book one or more amusements. ii. There are different types of amusements available in the camp. iii. The booking done by each customer will be assigned with a unique Booking ID. iv. Each item is assigned with a unique ID for identification. v. Each item's current available quantity iQlso maintained in the table Item Details.

C1. “Nomadic Desert Camp, Oman" requires an Information System to maintain the details of the amenities provided by them to their tourists and the customers. The customer bill given below [Figure C1] is an example of a record used by them for booking the amenities. Draw an Entity Relationship Diagram. Your Entity Relationship Diagram (ERD) should show Entities, attributes, Key attributes, optionality, and cardinality. Also consider the following points for developing relationships: i. A customer can book one or more amusements. ii. There are different types of amusements available in the camp. iii. The booking done by each customer will be assigned with a unique Booking ID. iv. Each item is assigned with a unique ID for identification. v. Each item's current available quantity iQlso maintained in the table Item Details.

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

Chapter4: Entity Relationship (er) Modeling

Section: Chapter Questions

Problem 21RQ

See similar textbooks

Similar questions

What is Entity relationship modeling produce an entity relationship diagram for the scenerio below;A new relational database is being developed for a university library, the database should allow the librarian to track individual copies of the books, record borrower information, (students can borrow multiple boks), the due date return, fine payable ( for books returned late) and other relevant information Explain the different types of relationships including the cardinality and participation constraint for every relationship identified
An instructor has several phone numbers. When reducing the ER diagram down to a schema this must be addressed. Which of the following statements are true? a. an instructors phone is what is known as a multi-valued attribute b. a multi-valued attribute of an entity is expressed as a separate schema with attributes including the primary key of the original entity and the multi-valued attribute c. the instructor should have a column for each type of phone number d. multi-valued attributes must be flatted out to a separate attribute for each component
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.
Was cardinality ever used as a representation of anything in an entity-relationship diagram? 1:The unique identifier that is used to store data 2:The maximum number of entity instances that may be used in a connection 3:The total number of primary keys associated with an object. 4:The total number of attributes possessed by an entity
Consider the below ERD in Figure 03 of Student Enrolment system and answer the below questions. List the strong (non-weak) entity types in the ER diagram. Is there a weak entity type? If so, give its name, partial key, and identifying relationship. What constraints do the partial key and the identifying relationship of the weak entity type specify in this diagram? List the names of all relationship types, and specify the (min, max) constraint on the participation of an entity type in a relationship type. Justify your choices. List concisely the user requirements that led to this ER schema design
What kinds of information could you capture about this relationship? What would the new ERD look like? Would the intersection entity be considered dependent or independent? Can you think of other kinds of M:N relationships that exist in the real world? How would you resolve these M:N relationships if you were to include them on an ERD? The newly created office of the university, the Student Housing Office, helps enrolled students find apartments for them to stay in while attending school. The office asks apartment owners to fill in an information form about their units for rent that are available (location, number of bedrooms, monthly rent, utilities, curfew, kitchen, CR, distance to campus, etc.). Students needing assistance need to register with the service - they in turn can search the rental information to find apartments that meet their needs or budget. Students then can contact the owners directly to see the unit and possibly rent it. IF it gets rented, the apartment owners…
3 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…
For 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)
Suppose that we wish to keep a genealogy. The information we wish to record about each person includes their name, date of birth, phone number, and degrees obtained . We also need to keep track of the mother, father, and children of each person. Draw a complete Entity-Relationship diagram. You must include all the details, sad as keys, weak entities (if any), cardinality constraints, etc. Your diagram must avoid redundancy.
(a) Explain carefully four ways in which the diagram fails to model the intended world. In each case make sure you contrast the actual meaning with the intended meaning. (b) Give an entity-relationship diagram, still using two entity types, which correctly models the intended world. (c) Give a database schema (including primary keys) for the ER diagram which you have given in the previous part. (d) Is there any part of the ER diagram which is not captured in the schema? How might this aspect be captured in the final database?

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

Principles of Information Systems (MindTap Course…

Computer Science

ISBN:

9781285867168

Author:

Ralph Stair, George Reynolds

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

Principles of Information Systems (MindTap Course…

Computer Science

ISBN:

9781285867168

Author:

Ralph Stair, George Reynolds

Publisher:

Cengage Learning

SEE MORE TEXTBOOKS