A university needs to design a database. Below are the list of entities, attributes, and business rules. - Room is identified by Room No and also has Capacity. A room can be either a lab or a classroom, nothing else. - Computer identified by Computer No and has attributes ComputerType, Description and ProcessorSpeed. - A Media is identified by Media No and has attributes of Type and Description. - A room cannot be both classroom and a lab. There also no other room types to be incorporated into the system. - A lab has one or more computer. However, a classroom does not have any computers and it contains different type of board need to be saved. - A room can be provided with one type of media, several types of media, or no media. A media does not belong to a room, they are borrowed and returned.

A university needs to design a database. Below are the list of entities, attributes, and business rules. - Room is identified by Room No and also has Capacity. A room can be either a lab or a classroom, nothing else. - Computer identified by Computer No and has attributes ComputerType, Description and ProcessorSpeed. - A Media is identified by Media No and has attributes of Type and Description. - A room cannot be both classroom and a lab. There also no other room types to be incorporated into the system. - A lab has one or more computer. However, a classroom does not have any computers and it contains different type of board need to be saved. - A room can be provided with one type of media, several types of media, or no media. A media does not belong to a room, they are borrowed and returned.

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

Q1. Draw an E-R Diagram for the following situation. At the university system each STUDENT must be assigned an ADVISOR who counsels students about degree requirements and helps students register for classes (COURSE). Each student must register (REGISTRATION) for classes with the help of an advisor, but if the student's assigned advisor is not available, the students may register with any advisor, We must keep track of students, the assigned advisor for each, and the name of the advisor with whom the students registered for the current term. Tips: Attributes of STUDENT include Student ID (the identifier), Name, and Major. Attributes of ADVISOR include Advisor ID (the identifier), Name, and Department. Attributes of COURSE include Course ID (the identifier), Title, and Credits. Attributes of REGISTRATION include Semester, and Year. Based on your background, think of logical and standard relationships between the given entities.
A well-structured database starts from an effective Entity Relationship Diagram (ERD). For this part of the question, you will need to sketch an ERD for the following gym scenario: A member must have a member ID, name and contact number, can be enrolled in one or more gym session. A gym session can be enrolled in by one or more members. Each gym session is identified by a session ID, and has a name, date and instructor details (Instructor ID). An instructor has an instructor ID, name and contact number, and must only be assigned to one gym session. A gym session can have one or more instructors assigned in it.” *show entities, relationship types and cardinalities. Crow’s foot model notations recommended.
Design the database, following an ER model. 1. Patients: Patients are tracked by a unique patient ID. Personal information includes first name, last name, phone number, Date of Birth, and sex. The combination of the Patient's first and last name must be unique. Patient's sex is a mandatory field. Patient can be registered at any clinic. 2. Cancer: Type of cancer is tracked by a unique ID. Cancer is categorized as either Oral, Lung, Breast, Liver, Blood, Bone, Pancreatic, Cervical, or Prostrate. Stage of cancer can be Stage I, Stage II, or Stage III Stage of cancer detection. Treatment given: Chemotherapy only, Surgery with chemotherapy, Surgery only or Radiation therapy. Patient_id is an FK which references the ID of the Patient. Clinic_id is an FK which references the ID of the Clinic that patient register. Patient information must be stored at one clinic. Patient Date of detection of Cancer. 3. Clinic: Clinics are…
Careful design of the interface between the ordering system and the product database during Phase 1 will help the development of the new product database in Phase 2. Create a UML class diagram for the system as follows. Use noun identification to list the candidate classes. Select the classes. For each class, list at least one attribute and one operation. Draw a possible class diagram. For the interface between the ordering system and the product database: Select a design pattern that will allow the product database to be replaced in Phase 2 without modifications to the ordering system. Why would you choose this design pattern? Make a sequence diagram for ordering a toy.
Doctors have id. name. date of birth. and specialty. Patients have id. name, and date of birth. and address. Medicines have name. patent number, and milligrams We want to build A database that keeps track of the medicines prescribed by a doctor to patients The prescription process happens in a hospital. (a) Draw a complete Entity-Relationship diagram for the description above. You must include all the details, such as keys, weak entities (if any). cardinality constraints., etc Your diagram must use n-ary relationships You must use arrow notation Your diagram must avoid redundancy.
Question=1)DRAW : Matrix diagram of this entities project will be about a student attendance. Entities: student, course, instructor, attendance, enrollment, department, class. Relationships: Student is enrolled in course, Course has instructor, Department has many courses, Entities: 1. Student - Attributes: Student_ID (Primary Key), Name, Age, Email, Phone _Number 2. Course - Attributes: Course_ID (Primary Key), Course_Name, Department_ID (Foreign Key) 3. Instructor - Attributes: Instructor_ID (Primary Key), Name, Department_ID (Foreign Key) 4. Attendance - Attributes: Attendance _ID (Primary Key), Student_ID (Foreign Key), Course_ID (Foreign Key), Date, Status 5. Enrollment - Attributes: Enrollment_ID (Primary Key), Student_ID (Foreign Key), Course_ID (Foreign Key), Enrollment Date 6. Department - Attributes: Department_ID (Primary Key), Department_Name 7. Class - Attributes: Class_ID (Primary Key), Class_Name, Department_ID (Foreign Key) Draw Matrix diagram of this scaniorio
1. Create an EER diagram to keep track of information for an art museum given that the following criteria is met: The museum has a collection of art objects. Each art object has a unique identification, an artist (if known), a year (when it was created, if known), a title, an epoch (Renaissance, Modern, Ancient, etc.), and a description. The arts objects are classified in the museum in several ways as discussed below: Arts objects are categorized based on their type. The main types are: painting and sculpture, plus another type they called “other” to accommodate objects that do not fall into one of the two main types. A painting has a paint type (oil, watercolor, etc.), material on which it is draw on (paper, canvas, wood, etc.), and style (modern, abstract, impressionism, etc.). A sculpture has a material from which it was created (wood, stone, iron, etc.), height, weight, and style. An art object in the other category has a type (print, photo, etc.) and a style. Art objects…
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.
Match the term with its description by placing the letter of the definition in the space preceding the term. ✓ Attribute ✓ Entity ✓ Entity set ✓ One-to-many relationship ✓ Overlap constraint A. A property or description of an entity B. An association among two or more entities C. A collection of unique tuples D. An object in the real world that is distinguishable from other obje E. One entity can be associated with many of another entity F. Two or more subclasses can contain the same entity. G. A set of possible values for an attribute H.A collection of similar entities
Swing Jazz Club ERD Problem Follow the Simple Procedure for ERD diagramming to design an ERD using the following user provided information. Remember the ERD will eventually turn into the design for a database from a top down view. Make sure you resolve any many to many conflicts. Label an identifier or primary key and all pertinent attributes given. If an attribute is not readily apparent from the user information, then make one up that makes sense for the particular entity. Therefore, all entities should end up with at least an identifier and another attribute that makes sense. You may use any of the approaches shown by the book, though the ER-Model and Crow’s foot are the most common. Make sure you show entities, relationships, cardinality, and optionality. Swing Jazz Club The Swing Jazz Club teaches swing and jazz dancing and offers both private and group lessons. Swing Jazz charges $60 dollars per hour for a private lesson and $10 dollars per hour for a group lesson.…
San Diego Hospital Example ERD Problem Entity Relationship Diagramming is a "top down" user process. Take the following user provided information and draw the appropriate ERD. Follow the Simple Procedure for ERD diagramming to design an ERD using the following user provided information. Remember the ERD will eventually turn into the design for a database from a top down view. Make sure you resolve any many to many conflicts. Label an identifier or primary key and all pertinent attributes given. If an attribute is not readily apparent from the user information, then make one up that makes sense for the particular entity. Therefore, all entities should end up with at least an identifier and another attribute that makes sense. Please use a drawing tool of some type to show the ERD diagram (Word, PowerPoint, and Visio all work well). I want you to get in the habit of drawing these with a computer instead of by hand, as this will be important as we get to more difficult…
1. Draw a data model for the following entities, considering the entities as representing a system for a patient billing system and including only the attributes that would be appropriate for this context: • Patient (age, name, hobbies, blood type, occupation, insurance carrier, address, phone). Insurance carrier (name, number of patients on plan, address, contact name, phone). Doctor (specialty, provider identification number, golf handicap, age, phone, name)