Summary: Designing an Elevator System

Now that you’ve completed the elevator system case study, let’s take a moment to reflect on and consolidate what we’ve learned. We’ll revisit the key system requirements, identify the core classes along with their responsibilities and relationships, and highlight the major design principles applied. We’ll also examine how objects interact within the system and walk through the overall workflow to understand how the components come together to achieve the desired functionality.

Key requirements

This section outlines the primary functional requirements that guided the design of the elevator system.

1. The system must support a configurable number of floors (up to 15) and elevator cars (up to 3).

2. Each elevator car must be able to serve all floors and can be in one of four states: moving up, moving down, maintenance, or idle.

3. Elevator doors should only open when the car is idle and must close automatically after a set time.

4. Each floor needs a panel with up/down call buttons and a display showing the car’s floor and direction.

5. Each elevator car must have an internal panel with floor selection buttons, open/close buttons, an emergency-stop button, and a display for floor, direction, and load status.

6. The emergency-stop button must immediately halt the car, keep doors closed, and alert security.

7. Each car must enforce a maximum load (680 kg) and prevent movement if exceeded.

8. To minimize wait times, A central controller must intelligently assign the most suitable car to floor calls.

9. The system must handle ...