Database Projects/5e - Professor Jerry Post

More documents

Recommendations

Info

Chapter Outline Introduction to Database Projects, 2 RMN Auto Sales (2005), 3 Purchases, 3 Sales, 3 Warranties and Payments, 4 Exercises, 5 Monster Video (2005), 7 Initial Appraisal, 7 Proposal Options, 8 Installation, 8 Exercises, 11 Big Chemical, Inc. (2005), 12 Employee Information, 12 Sensors, 12 Employee Access, 13 Exercises, 15 Big Teeth Reality TV (2005), 16 Applications, 16 Episodes and Events, 17 Exercises, 18 Cerulean Bee (2005), 20 Artwork, 20 Orders, 22 Exercises, 23 Orange Blossom Nursery (2007), 24 Plant Orders, 24 Payments and Billing, 26 Delivery, 26 Purchases, 27 Exercises, 28 Projects Round Avon Theater Troupe (2007), 29 Shows, 30 Bills and Salaries, 31 Traveling Shows, 32 Sales Analysis, 32 Exercises, 33 Joe’s Chops (2007), 34 Choosing Options, 34 Web Site Communications, 35 Itemized Billing, 36 Exercises, 37 Rational Room Reservations (2010), 38 Rooms, 38 People, 39 Reservations, 40 Exercises, 42 Pliable Plastic Production (2010), 43 Design, 43 Input Purchases, 44 Production, 45 Shipping, 46 Exercises, 46 On the Hoof Dairy (2010), 48 Cows, 48 Feed, 49 Medical Treatments, 50 Exercises, 50 1
Introduction to Database Projects Project Descriptions To learn how to build business applications, you need to work on a database project. The projects described in this appendix are simpler than real-life projects but complex enough to illustrate common problems that you will encounter. The projects are designed to be built throughout the term. Students should demonstrate a completed database application at the end. Preliminary assignments are given for each project to get you started. However, the most important aspect of the case is to build the final, complete application. To provide additional feedback, the instructor should also evaluate the projects at two intermediate stages: (1) the list of normalized tables and (2) some initial forms and reports. The most important advice to students is that you must begin work on the project as soon as possible. Do not put the project off until the end of the term. To have any chance at completing the project, most students will have to put in 20 to 40 hours of time. The project will reinforce the concepts discussed in the chapters—particularly data normalization and application design. If you work on the project throughout the semester, you will gain a better understanding of the topics, and you will finish most of the project before the end-of-term crunch. Class projects are slightly different from real-world applications, but have many features in common. One of the most challenging aspects is that any project contains a level of uncertainty and ambiguity. When you start a real-life project, you never know exactly what the project is going to involve. As you talk with users, you encounter contradictions, uncertainty, and confusion over terms and goals. In real-life, you resolve these problems through experience and discussions with managers. With class projects, you do not have direct access to the managers and users. The instructor can answer some questions, but you will need to make your own decisions and interpretations. When you first read the case, try to focus on the big picture. Identify the environment, goals, and objectives of the proposed system. Take notes on the company and jot down additional questions. Research the industry and similar firms to help identify terms, goals, and potential problems. When you begin to analyze the individual forms and reports, identify the overall purpose of each form. You should be able to describe the purpose of each form in one sentence. For any of the cases, you should make this list and keep it handy so you always remember the overall purpose of the application. Remember that you will probably have to rework the normalization several times before the project is complete. Remember that every time you change the primary keys, you have to delete relationships. Try to develop a good normalized list before you begin creating forms and reports, but leave yourself enough time to go back and change the tables if you find problems. In many cases it pays to start small and add tables and features slowly. Start with an initial set of tables and keys that you are certain are correct. Then begin building forms. Add columns and tables as you need them. If your initial tables are correct, you should be able to add new columns and tables without altering the existing design. For the final project, it is usually better to complete half a project where everything works, instead of a large mess where nothing works. One final word of advice: Back up your work. Always keep a backup copy of your project on a different disk. Two or three copies are even better. Disks are cheap. 2
Page 1: Database Management Systems Project
Page 5 and 6: Date Total Due Down Payment Finance
Page 7 and 8: Project Descriptions 8. Design the
Page 9 and 10: Customer Phone Subdivision Proposal
Page 11 and 12: Audio Video Components Customer Dat
Page 13 and 14: Big Chemical, Inc. (2005) Project D
Page 15 and 16: Employee Access Rights Employee Sec
Page 17 and 18: Big Teeth Reality TV (2005) Applica
Page 19 and 20: Episode Title Episode Air Date Cont
Page 21 and 22: Cerulean Bee (2005) Customer Contac
Page 23 and 24: Project Cost Analysis Project Event
Page 25 and 26: Orange Blossom Nursery (2007) Proje
Page 27 and 28: Delivery Date Delivery Time Contact
Page 29 and 30: Project Descriptions items. The Ora
Page 31 and 32: Project Descriptions Shows A show i
Page 33 and 34: Project Descriptions expenses is ge
Page 35 and 36: Joe’s Chops (2007) Project Descri
Page 37 and 38: Finish Date Vehicle VIN Overhaul de
Page 39 and 40: Rational Room Reservations (2010) P
Page 41 and 42: EID Last Name, First Name Departmen
Page 43 and 44: Exercises 1. Create the feasibility
Page 45 and 46: Item Order ID Date Vendor Phone Del
Page 47 and 48: Destination Address City, State, Po
Page 49 and 50: On the Hoof Dairy (2010) Project De
Page 51 and 52: Cow Birth weight Treatment Date Wei

Database Projects/5e - Professor Jerry Post

Create successful ePaper yourself

Delete template?

Save as template?