Ticket Requests Database Design Exercise Requirements KCIC has seasonal company tickets (currently 4 per event) to a variety of local sports games We need a way to systematically track requests made for these tickets by our employees, to better account for and appropriately allocate them We dont have explicit limits on the number of requests that can be made, but we do need to allow people to prioritize their own requests, and to automatically shift employees with numerous requests awards of tickets to a lower priority We will need users to be able to enter their own requests directly, and our internal social team needs reporting on the requests over time for the purposes of doling out the tickets Exercises Questions Design elements What would be your recommended database model (sketch it out in the program of your choice) How would you handle potentially scaling to accommodate other kinds of events and or other new similar employee perks What would be your recommended front end for users interacting with this database What would your recommended reporting solution(s) be for this data Administrations concerns How would you handle allocating permissions for this database How would you best ensure that there is maximum up time for this database Hypothetical future development Say we want to integrate this into our company sites Admin Panel what would be your approach if tasked to oversee that migration Say our clients become aware of this functionality and want us to build it out for them, moving it to a large scale implementation as an actual product service what would change in your database design model and approach to administrating it

The Answer is in the image, click to view ...

Answered step by step

Verified Expert Solution

Link Copied!

Question

1 Approved Answer

Posted on Sep 05, 2024

Ticket Requests Database Design Exercise Requirements: KCIC has seasonal company tickets (currently 4 per event) to a variety of local sports games. We need a

Ticket Requests Database Design Exercise

Requirements:

KCIC has seasonal company tickets (currently 4 per event) to a variety of local sports games. We need a way to systematically track requests made for these tickets by our employees, to better account for and appropriately allocate them.

We dont have explicit limits on the number of requests that can be made, but we do need to allow people to prioritize their own requests, and to automatically shift employees with numerous requests/awards of tickets to a lower priority. We will need users to be able to enter their own requests directly, and our internal social team needs reporting on the requests over time for the purposes of doling out the tickets.

Exercises/Questions:

Design elements:
- What would be your recommended database model? (sketch it out in the program of your choice)
- How would you handle potentially scaling to accommodate other kinds of events and/or other new similar employee perks?
- What would be your recommended front end for users interacting with this database?
- What would your recommended reporting solution(s) be for this data?

Administrations concerns:
- How would you handle allocating permissions for this database?
- How would you best ensure that there is maximum up-time for this database?

Hypothetical future development:
- Say we want to integrate this into our company sites Admin Panel - what would be your approach if tasked to oversee that migration?
- Say our clients become aware of this functionality and want us to build it out for them, moving it to a large-scale implementation as an actual product/service - what would change in your database design & model and approach to administrating it?