Requirements

Determine the different ways the system will be used. This includes main functions the system needs to perform and who w

>> System to generate a parking ticket with timestamps and pakring spot number, floor etc printed for vehicle at entry gate

>> Parking attendants to direct vehicle to the assigned parking lot

>> Attendants to mark parking spot as occupied and unoccupied as per vehicle parking and unparking

>> Different type of spots for two wheeler, four wheeler (cars and large four wheelers etc)

>> Different floors avaliable for parking

>> System to display parking full at entry if completely occupied

>> At exit, option for driver to make payent with differnt modes

>> On payment, parking attendants can mark the ticket as paid and slot unoccupied

>> Different types of users: drivers, attendants and admin

Define Core Objects

Based on the requirements and use cases, identify the main objects of the system...

>> User

role

>> Driver inherits User

park

unpark

makePayment

vehicleType

buyPass

>> Attendant

markOccupied

markUnoccupied

generateTicket

openGate

examinePass

issuePass

>> Admin

add/update User

add/update Spot

add/update Floor

add/update Gate

addPaymentModes etc

markOccupied

markUnoccupied

generateTicket

>> gate

type

number

>> spot

status

type

Analyze Relationships

Determine how these objects will interact with each other to fulfill the use cases...

Establish Hierarchy

Design inheritance trees where applicable to promote code reuse and polymorphism. This step involves identifying common attributes and behaviors that can be abstracted into parent classes...

Design Patterns

Consider using design patterns (e.g., Factory, Singleton, Observer, Strategy) that fit the problem...

Define Class Members (write code)

Attributes: For each class, define the attributes (data) it will hold...

Methods: Define the methods (functions) that operate on the attributes. Ensure they align with the object's responsibilities and adhere to the principle of encapsulation.

Adhere to SOLID Guidelines

Check and explain whether your design adheres to solid principles (Ask interviewer what SOLID principle is if you can not recall it.)...

Consider Scalability and Flexibility

Explain how your design can handle changes in scale and whether it would be easily to extend with new functionalities...

Create/Explain your diagram(s)

Try creating a class, flow, state and/or sequence diagram using the diagramming tool. Mermaid flow diagrams can be used to represent system use cases. You can ask the interviewer bot to create a starter diagram if unfamiliar with the tool. Briefly explain your diagrams if necessary...

Future improvements

Critically examine your design for any flaws or areas for future improvement...