Reference no: EM133142592

Working through ambiguity and trying to figure out what makes sense is part of the usefulness of this assignment. You aren't replicating an exact procedure, you do need to deal with things that can be interpreted in multiple ways, and make judgement calls. The confusion is where the learning happens.

For submission, you can simply write out the results in an Excel spreadsheet, similar to the in-class example. If you want to drawn an ER diagram, draw.io is also a good choice.

Note: For part 4, we basically want to know: info on the customer and what they spent for each purchase. You can IGNORE THE AVERAGE part of that (it makes things more complex) - just list the customers along with their purchases.

Note 2: For part 3, you can assume that the Supplied Customer is Elite Demolition. List the data for their orders.

Note 3: For normalizing and creating an ER diagram, think about this question, "if someone orders 3 of one product, where does that value for quantity go?"

Note 4: The notes data is intended to be kept. How this is stored is a bit more ambiguous, on purpose. Determine it as best as you can. As a hint, in a real database, this would likely apply - the notes is an added description about a 'thing'. The DB contains many things, many/all of these things may have a note about them. Each note can be attached to one 'thing'. If this makes 0 sense, please ignore it, this part is relatively small; this is just for people who are comfortable with things and want to get it close to perfect.

Note 5: Example of flattening data. Put everything back together so each row has all data.