System requirements


Functional:

List functional requirements for the system (Ask the chat bot for hints if stuck.)...

User should be able to purchase tickets

User should be able to see which movies are available


Non-Functional:

List non-functional requirements for the system...

High consistency so that tickets are not oversold

Highly scalable to handle a lot of users for popular movies or concerts

Secure transactions for purchasing tickets



Capacity estimation

Estimate the scale of the system you are going to design...

A lot of peak users when the movie tickets become available to handle




API design

Define what APIs are expected from the system...

REST API

POST /ticket/{ticketID}

GET /ticket/{ticketID}/price

GET /movie/list

GET /movie/{movieID}




Database design

Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...






High-level design

You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...








Request flows

Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...






Detailed component design

Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...






Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...






Failure scenarios/bottlenecks

Try to discuss as many failure scenarios/bottlenecks as possible.






Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?