Reference no: EM133388930
Requirements:
1. Construct a UML diagram that provides a conceptual overview for the data described in the scenario below. No need to include any classes that are not described in the simplified example.
2. Construct a set of Data Tables that could be used to collect data described in the scenario below. Each data table should have at least three columns (you can make up attributes) and at least three rows (you can made up data records). No need to include any tables that are not described in the simplified example.
Little Debbie will soon start selling cookies door-to-door to raise funds for a neighborhood after school program. Debbie is currently studying to be a CPA and looks for any opportunity to use their Accounting Information Systems knowledge on a new problem. This year Debbie hopes to construct a database to record all cookie sales transactions in hopes of optimizing a sales route for use in the future. The database should record of each individual "cookie sale" event that takes place. The system should work as follows:
Think of each time someone decides to purchase cookies as an individual transaction referenced as a "cookie sale" event. You can even pretend that an itemized receipt is given (Debbie is a future CPA) that lists the following information.
A "cookie sale" event listed in the database involves a single customer. A "cookie sale" event must be associated with a customer to be added to the database. Each customer may purchase cookies as many times as they want (the cookies are delicious). However, a customer can be added to the database without a "cookie sale" event if they want time to think before ordering.
A "cookie sale" event can result include the purchase of as many cookies as a customer wants to order. However, cookie purchases are limited to the cookie types included in the system (and available as part of the fundraiser). Each cookie type can be involved in multiple "cookie sale" events. Cookie types can be added to the database without an associated "cookie sale" event.
NOTE: This is a simple example that omits other data that might be collected. That is on purpose! I just want you to quickly attempt this short, abbreviated example. Please limit your work to tables that are: 1) explicitly described, or 2) required to enact the described data relationship.