Description of this paper

Management Information Systems




Management Information Systems Homework 6;MIS 33:136:370:01/02;Fall 2014, Inst. McGinity;Assigned: October 23;Due: October 30;On your submission, please clearly write your rst and last name, as well as your;section (either 01 or 02) in the upper-righthand corner. Please make arrangements;to staple multiple sheets together.;For each of the below situations, design a database to hold the necessary information using the principles we learned in class, in particular tools for Many-to-Many;relationships, subtypes, memory storage, etc.. Specically, present your solutions by;drawing an entity-relationship (ER) diagram and writing a database design outline;as illustrated in class.;1;Tour Company;You consult for a tour company to implement a database for its operations. The company oers dierent tour packages (e.g. segway tour of garden district, trekking;the Camino Real, etc.) from which customers can book a tour with a guide. After;an elicitation session with management, you get clarity on the following technical;points of their operations;Each tour package (i.e. kind of tour) has a certain price per guest, scheduled;length, and maximum number of guests. A guide might give several dierent;tour packages. A tour always has one guide and sometimes takes more or less;than the scheduled time to nish.;You often see families on vacation participating in your tours.;You also elicit that answers are important to the following questions;Who participated in a given tour? Who was the guide? When did it start, and;how long did it take?;To how many customers did we provide tours last season? What customers;have taken our tours multiple years in a row (i.e. loyalty program)?;From where do our customers come? What are our major demographics?;This child was found unattended / hiding on the bus / being too awesome;in the museum: Who are this childs parents? What is their mobile phone;number?;1;Hand in a database design outline and entity-relationship diagram for a database appropriate for this scenario. Structure your database to eciently store the necessary;data to answer the above questions.;2;Get in the zone...;AutoZone (5,000 stores, $9b revenues, $17b market cap) contracts you to develop;a database of all its auto parts. After a meeting, you understand that there are;many dierent types of parts (e.g. fuel lters, signal lamp, wheel nut, tire, etc.;etc.), and within each type, there are many specic kinds of part types (e.g. Spectre;Clear view fuel lter, PX1271 signal lamp, etc., etc.). Also, you know that there;are vehicle makes (e.g. Ford, Volkswagen, Nissan, etc.), and within each make many;dierent years, models, and engine specications (e.g. 2014 Jetta 2.8T). Through;your elicitation session you understand the following;Each specic part has a unique SKU code. However, each part has a manufacturer who has its own part number which would be good to have when;requesting more parts.;Each type of vehicle is identied by a specic vehicle type code which corresponds to a specic combination of vehicle specic make, model name, year;and engine description. For simplicity, do not include separate tables for known;model names and engine types;Generally, a part is compatible with many dierent vehicle types.;The database is designed to be useful for employees. Common questions include;Which tail light bulbs are compatible with a 2008 Subaru Forester?;What is the cheapest lter for this vehicle?;Ive got the manufacturer on the phone: What is their internal part number;for the spark plug that ts this customers 2010 Camry?;Hand in an entity-relationship diagram and a design outline for a database appropriate for this information.


Paper#17587 | Written in 18-Jul-2015

Price : $27