Create and ERD based on the Crow's Foot Model, using the following requirements. Include Primary Keys, Foreign Keys, and Relationship types (weak/strong): 1. An INVOICE is written by a SALESREP. Each sales representative can write many invoices, but each invoice is written by a single sales representative. 2. The INVOICE is written for a single CUSTOMER. However, each customer can have many invoices. 3. An INVOICE can include many detail lines(INV_LINE), each of which describes one product bought by the customer. 4. The product information is stored in a PRODUCT entity. 5. The product's vendor information is found in a VENDOR entity.

Create and ERD based on the Crow's Foot Model, using the following requirements. Include Primary Keys, Foreign Keys, and Relationship types (weak/strong): 1. An INVOICE is written by a SALESREP. Each sales representative can write many invoices, but each invoice is written by a single sales representative. 2. The INVOICE is written for a single CUSTOMER. However, each customer can have many invoices. 3. An INVOICE can include many detail lines(INV_LINE), each of which describes one product bought by the customer. 4. The product information is stored in a PRODUCT entity. 5. The product's vendor information is found in a VENDOR entity.

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

Given the entity STUDENT and attributes: ST_INTIAL, ST_LNAME, ST_FNAME, ST_EMAIL, ST_PHONE . Use the Chen notation to depict the relationships:
Based on: Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors Show the Relational Algebra AND Domain Relational Calculus formulas for each. Show a portfolio of the Flubs by a Professor Show a portfolio of all Flubs and Bounces (the Flubs bounced) by all of a Professor's Colleagues
Based on: Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors Create the SQL for a single View called "Flubbergasting" of a Professor which includes all attributes from Entity-Relationship Diagram, as well as how many Flubs, the average number of Bounces the Flubs had, and total Citations across all Flubs by that professor.
Based on the following Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors Write the necessary SQL Queries for the following functions. Adding a new Professor Changing a specific Professor's Professor_Name Removing a Flub by ID Show a portfolio of the Flubs by a Professor in reverse chronological order Show how many Bounces and how many Citations a Flub of particular ID has Show a portfolio of all Flubs and Bounces (the Flubs bounced) by all of a Professor's…
In the space provided below, draw an ER diagram that includes entities for Clients, Contracts, and Contacts. Clients have the following attributes: ClientID (primary key), ClientName, ClientAddress. Contracts have the following attributes: ContractID (primary key), ContractType, LicenseFee. Contacts have the following attributes: ContactID (primary key), ContactName, ContactAddress. Draw a relationship between Clients and Contracts such that a Client can be assigned to many contracts, but it can also exist without having any contracts at all in the database. Conversely, a contract can be assigned to only one client but must be assigned to a client in order to exist. Name your relationship “Signs”. Draw a relationship between Clients and Contacts such that a client must be assigned to one and only one contact. A contact can exist in the database without being assigned to a client, but a contact can be assigned to more than one client. Name your relationship “Has”. Use…
Based on the following Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_DateThere are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor)There are Bounces (ie shares) where a Professor can share another Professor's FlubAdd ID attributes as necessaryContent of Flubs only needs to be a text of fixed lengthProfessors can have/be Colleagues (ie friends/followers)A Flub can get Citations (ie likes) by other Professors--------- Create the Relational Model for the Flubber database based upon your ER Diagram above, meeting all the same requirements. Include all necessary Primary Key and Foreign Key constraints. This should be syntactically correct to test in a MySQL database.
Let's break down the information into entities, attributes, and relationships: Entities: 1. Ship - ShipID (Primary Key) - ShipName - ShipType 2. Captain - CaptainID (Primary Key) - CaptainName - CaptainLicense 3. ShipmentTrip - TripID (Primary Key) - DeparturePort - ArrivalPort - RouteDetails 4. ShipmentManifest - ManifestID (Primary Key) - Date - GoodsList 5. Goods - GoodsID (Primary Key) - GoodsName - GoodsType (BM or LM) 6. Port - PortID (Primary Key) - Street - City - State - PostalCode - Country Relationships: - Ship to ShipmentTrip (Many-to-Many): - Ship can participate in multiple ShipmentTrips, and a ShipmentTrip can involve multiple Ships. Create a junction table `Ship_ShipmentTrip` with attributes `ShipID` and `TripID`. - Captain to ShipmentTrip (Many-to-Many): - A Captain can be assigned to multiple ShipmentTrips, and a ShipmentTrip can have multiple Captains. Create a junction table `Captain_ShipmentTrip` with attributes `CaptainID` and `TripID`. - Captain to Ship…
Question 30 Which of the following is the term for the number of entities involved in a relationship? Group of answer choices degree ordinality minimum cardinality class maximum cardinality
Create an ERD using Visio or any other tool for the following scenario. Your ERD should show all the tables, attributes for each table and identify all primary and foreign keys. A hair salon has many customers and many stylists - the first name, last name, and phone number need to be stored for customers and stylists. The hair salon offers many services - hair cutting, styling, coloring, permanents, etc. Each service has a cost and the estimated time. Customers schedule appointments with a stylist. The appointment can consist of one or more than one service - i.e. a person may want a hair cut and coloring. Some customers purchase products at their appointments. A product has a brand, description, category and price. Please show all work and the finished diagram. Thank you!
Consider the following parking tickets. Create ERD using Crow’s Foot notation with relationship cardinality, modality, & relationship strength and implement normalization on each entity to finalize your ERD. Note that St Lic, Lic No (car plate # and State where it is issued) are for a car; St ID, LN, FN, and Phone# are for the owner of the car; code represents a specific parking violation with the corresponding fine.
which of the followings are weak key attributes, derived attribute, entity rounded, weak entity, multivalue attribute, associative entity and identifying relationship are of the following listed enitites, attributes and relationships: hospital(HOSP_NAME, COUNTRY ,ADDRESS) medicine(REG_NO ,MED_NAME,PRICE ,EXP_DATE) doctor( DOC_ID NUMBER, DNAME, GENDER, QUALIFICATION ,JOB_SPECIFICATION ,HOSP_NAME ) nurse( NURSE_ID NUMBER, NAME ,GENDER ,DOC_ID NUMBER, HOSP_NAME) patient(SSN NUMBER ,FNAME ,LNAME ,AGE,GENDER ,NURSE_ID NUMBER ,REC_ID) reception(REC_ID NUMBER,TEL_NO ,EMAIL ,HOSP_NAME ) appointment(APPOINT_NO NUMBER, APPOINT_DATE DATE , APPOINT_TIME time,REC_ID NUMBER) visit(VISIT_DATE DATE, SSN NUMBER, HOSP_NAME ) purchase(SSN NUMBER, DOC_ID NUMBER) medicine country( REG_NO NUMBER, MAN_COUNTRY )
Which of the following symbols represents an optional relationship in an E-R model? a. a straight line b. a dashed line c. a straight line with a crows foot at both ends d. a straight line with a crows foot at one end