Draw an ER diagram and then map it into a relational schema (database) for the following scenario. • For each MEMBER we keep track of the unique MemdID, a well as Name, Zip, and the Date the membership was paid. • For each MEMBERSHIP type we keep track of the unique Mid, as well as MName and Price • For each PASS CATEGORY we keep track of the unique PassCatID, as well as PCName and Price • For each ONE DAY PASS we keep track of the unique PassID and Date • For each MERCHANDISE item we keep track of the unique MrchID, as well as Name and Price • For each sale TRANSACTION we keep track of the unique Tid and Date • Each member pays for exactly one membership type; each membership type has at least one member but can have many members. • Each member can buy many day passes but does not have to buy any, each day pass was bought by exactly one member • Each day pass belongs to exactly one pass category; a pass category can have many individual day passes issued for it but does not have to have any. • Each sale transaction involves exactly one member; each member can be involved in many sale transactions but does not have to be involved in any. • Each merchandise item is sold via at least one sale transaction, but it can be sold via many sale transactions; each sale transaction involves at least one merchandise item but can involve many merchandise items. • Every time a merchandise item is sold via a sale transaction, we keep track of the quantity (how many instances of that particular merchandise item were sold via that particular sale transaction)

Principles of Information Systems (MindTap Course List)

12th Edition

ISBN:9781285867168

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter5: Database Systems And Applications

Section5.7: Information Systems @ Work: Brandwatch: Applying Business Intelligence To Social Media Data To Make Advertising Decisions

Problem 1CTQ

See similar textbooks

Related questions

Question

Draw an ER diagram and then map it into a relational schema
(database) for the following scenario.
• For each MEMBER we keep track of the unique MemdID, a well as Name, Zip, and the Date
the membership was paid.
• For each MEMBERSHIP type we keep track of the unique Mid, as well as MName and Price
• For each PASS CATEGORY we keep track of the unique PassCatID, as well as PCName and
Price
• For each ONE DAY PASS we keep track of the unique PassID and Date
• For each MERCHANDISE item we keep track of the unique MrchID, as well as Name and
Price
• For each sale TRANSACTION we keep track of the unique Tid and Date
• Each member pays for exactly one membership type; each membership type has at least
one member but can have many members.
• Each member can buy many day passes but does not have to buy any, each day pass was
bought by exactly one member
• Each day pass belongs to exactly one pass category; a pass category can have many
individual day passes issued for it but does not have to have any.

• Each sale transaction involves exactly one member; each member can be involved in many
sale transactions but does not have to be involved in any.
• Each merchandise item is sold via at least one sale transaction, but it can be sold via many
sale transactions; each sale transaction involves at least one merchandise item but can
involve many merchandise items.
• Every time a merchandise item is sold via a sale transaction, we keep track of the quantity
(how many instances of that particular merchandise item were sold via that particular sale
transaction)

Expert Solution

Trending now

This is a popular solution!

Step by step

Solved in 4 steps with 1 images

SEE SOLUTION Check out a sample Q&A here

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.