Loading...
Determine the different ways the system will be used. This includes main functions the system needs to perform and who will use it.
The Items must have an id, cost, and quantity. They need to be able to be bought(vended), restocked, and their price must be allowed to be changed.
The Vending Machine must have a list of all the items and the user's balance. It must be able to buy an item, checkBalance and UpdateBalance.
Based on the requirements and use cases, identify the main objects of the system...
The Vending Machine
The Items in the Vending Machine
Determine how these objects will interact with each other to fulfill the use cases...
The Vending Machine will maintain a list of item objects
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...
Consider using design patterns (e.g., Factory, Singleton, Observer, Strategy) that fit the problem...
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.
public class Car { ... } // ExampleCheck and explain whether your design adheres to solid principles (Ask interviewer what SOLID principle is if you can not recall it.)...
Explain how your design can handle changes in scale and whether it would be easily to extend with new functionalities...
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...
Critically examine your design for any flaws or areas for future improvement...