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.

Jack Skellington is a proud parent of three Trick-or-Treat aged children. Jack is also a CPA and looks for any opportunity to use their Accounting Information Systems knowledge on a new problem. This year Jack hopes to construct a database to record Halloween candy collected. The Skellington family hopes to use the database to optimize routes on future Halloween nights. The database should record of each individual Trick-or-Treat event that takes place. The system should work as follows:

• Think of each time someone says Trick-or-Treat as an individual transaction. You can even pretend that a receipt is given (Jack is a CPA after all) that lists the following information.
• A Trick-or-Treat event listed in the database involves a single child. A Trick-or-Treat event must be associated with a child to be added to the database. Each child will Trick-or-Treat many times. A child can be added to the database without a Trick-or-Treat event.
• A Trick-or-Treat event must take place at a specific location. A Trick-or-Treat event must be associated with a location to be added to the database. location can be the site of multiple Trick-or-Treat events. A location can be added to the database without a Trick-or-Treat event.
• A Trick-or-Treat event can result in many pieces of candy. Unfortunately, not all Trick-or-Treat events are associated with candy. Some houses are mean and give out toothbrushes or other non-candy items. Non-candy items are considered tricks and NOT recorded in the database. Each candy can be involved in multiple Trick-or-Treat events. Candy can be added to the database without a Trick-or-Treat event