Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
muti-level, muti-entrances and exits,
List non-functional requirements for the system...
no man service, car pay when leave, show number of available parking lots.
Estimate the scale of the system you are going to design...
100 car, 50 motocycle, 20 bicycles
Define what APIs are expected from the system...
POST- /parking/enter/T01234
{
ticket_number: T01234
car_type: 1
time_stamp: 13/02/2024 12:13:14 (dd/mm/yy HH:MM:SS)
}
GET - /parking/leave/T01234
body
{
ticket_number: T01234
car_type: 1
time_stamp: 13-02-2024-12:13:14
}
response
{
duration: 00/00/00 02:03:14 (dd/mm/yy HH:MM:SS)
price: 12.00
}
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...
erDiagram
CUSTOMER }|..|{ TICKET: has
TICKET }|..|{ ENTER_TIME: has
TICKET }|..|{ CAR_TYPE: has
TICKET }|..|{ SERVICE: insert
SERVICE }|..|{ EXIT_TIME:has
PRICE }|..|{ CAR_TYPE:has
PRICE }|..|{ UNIT_PRICE:has
SERVICE}|..|{ PRICE:get
SERVICE }|..|{ CUSTOMER:show_price
CUSTOMER}|..|{ SERVICE: pay
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...
flowchart TD
B[Customer] -- enter ---> C{parking_server}
C -- give ticket ---> B
C -- store customer info --> D[Database]
B -- request leave --->C
D -- retrive customer info --> C
C -- show price --->B
B -- make payment ---> C
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...
Customer->>+Service: "Enter parking"
Service->>-Customer: "Give Ticket"
Customer->>+Service: "insert ticket'
Service->>-Customer: "show price"
Customer->>+Service: "make payment"
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...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?