home / study / engineering / computer science / computer science questions and answers / dbms 110 database design and management s04 entity relationship design erd vinces vinyls ... Question: DBMS 110 Database Design and Management S04 Entity Relationship Design ERD Vinces Vinyls DB Cong... (5 bookmarks) DBMS 110 Database Design and Management S04 Entity Relationship Design ERD Vinces Vinyls DB Conger Chap 4 Chapter 4 in the Conger Book discusses how you use database modeling templates in Microsoft Visio, creating entities, attributes and relationships. We will be using Vince's Vinyls database that we have worked with in Chapter 2 & 3. S04 VincesVinylsDesignDocument.docx is also attached to this assignment. This should be used as a resource to create a Microsoft Visio logical model / ER Design using crows feet notation. Please read Chapter 4 before attempting the ERD for Vinces Vinyls. Use the Vinces Vinyls Scenario, page 79-80 TO DO items / tasks: 1 6. These questions have been repeated below. Create an initial Microsoft Visio Document, using all this information and submit this document, using this assignment link. Item 7 is not to be completed for this assignment. The Vinces Vinyls, Student or Group Review, will occur in Session 05. This assignment is worth a maximum of 20 points. TO DO questions to consider when building Vince's Vinyls ERD. 1. Review all the requirements and rules that you have gathered from your interviews and after reviewing Vinces records. 2. Define your entities and attributes and the relations that exist between them 3. Create a logical model using crows feet notation in Visio or another tool approved by your instructor. 4. Add all the entities and their attributes. You dont need to worry about data types for now. 5. Identify the key fields for each entity and the foreign keys. 6. Analyze the diagram. Identify which role (i.e., domain, linking, lookup, weak) each entity plays in your database. Vinces Vinyl Design Document Scenario, Conger Book You are eager to show Vince some progress on the database. You sit down to analyze all the materials you have gathered to see if you can make some sense of them. Make sure you review the material in the previous two chapters. Issues with the current system. Vince has difficulty tracking his current inventory. He needs to know the relative value of his inventory. He needs to track sales better. He is unsure how much money he has spent or earned. He would like to be able to track requests. inconsistent pricing for both purchases and sales Database requirements for each stakeholder involved in the database. For Vince The database needs to track inventory. The database needs to track purchases of albums from customers and sellers. The database needs to track sales to customers. The database needs to store requests. The database needs to store some customer information such as emails. For Sellers Database needs to record sales and prices. For Customers The database will list what is available. The database will store and process requests. The database will provide more consisting processing. Business rules. For Vince business rules are vague and fluid. That is part of his problem. Here are a few business rules: Vince records the conditions of the vinyl and covers when he buys. Purchases are rated mint, good, fair, and poor, depending on their condition. Most customers get discounts. Vinyls that Vince doesnt want to buy can be left behind to go in the 5-for-a-dollar bin. Major security rules for the database. There are very few security concerns for Vinces database. If he starts collecting customer information, that data should be secured. If he eventually goes online, the database will have to be protected against accidental or malicious attack. Nouns found on the forms, interview, the questionnaire, and the job shadow report, with preliminary entities and attributes. Nouns: Sellers Name, Sellers Phone Number, Album, Notes, Condition, Paid, Date, Customer, Price, Tax, Total Entities and attributes: Seller (Sellers Name, Sellers Phone Number, Album, Notes, Condition, Paid) Sale (Date, Customer, Album, Price, Tax, Total) Inventory (Album, Paid, Price, Condition) Inventory is implied from the discussions, interviews, and purpose of the database) Identify some candidate keys. For Seller, Sellers Name or Phone Number For Sale, maybe Date and Album combined (though that is not guaranteed to be unique) For Inventory, possibly Album though that is not guaranteed unique. View comments (2)