Scribd
Upload
245 views4 pages

Elevator Problem

The document describes the logic required to control elevators in a building with multiple floors. Elevators have buttons for each floor that illuminate when pressed. Floors have up and down buttons that illuminate when pressed. When not in use, elevators remain at their current floor with doors closed. The document also provides an overview of use case diagrams, class diagrams, state diagrams, sequence diagrams, and collaboration diagrams and how they apply to modeling the elevator control system.

Uploaded by

Chaithanya Kumar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
245 views4 pages

Elevator Problem

The document describes the logic required to control elevators in a building with multiple floors. Elevators have buttons for each floor that illuminate when pressed. Floors have up and down buttons that illuminate when pressed. When not in use, elevators remain at their current floor with doors closed. The document also provides an overview of use case diagrams, class diagrams, state diagrams, sequence diagrams, and collaboration diagrams and how they apply to modeling the elevator control system.

Uploaded by

Chaithanya Kumar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Elevator Problem A product is to be installed to control elevators in a building with m floors.

The problem concerns the logic required to move elevators between floors according to the following constraints:

Each elevator has a set of m buttons, one for each floor. These illuminate when pressed and cause the elevator to visit the corresponding floor. The illumination is canceled when the elevator visits the corresponding floor. Each floor, except the first floor and top floor has two buttons, one to request and up-elevator and one to request a down-elevator. These buttons illuminate when pressed. The illumination is canceled when an elevator visits the floor and then moves in the desired direction. When an elevator has no requests, it remains at its current floor with its doors closed.

Use Case Diagram Use case description:

A generalized description of how a system will be used. Provides an overview of the intended functionality of the system. Understandable by laymen as well as professionals.

The Use Case Diagram is usually accompanied by a Use Case Detail (or Spec) that takes this format: Use Case Detail: Overdrawn Report Used By: Bank Manager Inputs: Details what information flows from the user to the system for this particular Use Case. theBranchSortCode - The Sort Code of the branch for which the report is required. theOverdraftPeriod - how long an Account has been overdrawn before it is forms part of the report. Outputs: Details what information flows from the system to the external environment, in this case the printer! overdraftReport (to branchPrinter) - structured as follows: customer name; current overdraft; period overdrawn (days); Printed for all accounts that have been overdrawn for a period greater than theOverdraftPeriod, and which have not already been reported (on another report) in the last 30 days. Pre-Conditions: What validity checks or constraints apply on the inputs (or the internal system as a whole, in some cases). theBranchSortCode - must be a branch sort code held within the system. theOverdraftPeriod - must be a number between 0 and 100 days.

Post-Condition: What changes does the Use Case make to the internal system state. Updates the reportedOnDate field of overdrawn accounts. Class Diagram Class diagrams show the static structure of the object, their internal structure, and their relationships.

Detailed Class Diagram

State Diagram A state diagram shows the sequences of states an object goes through during it's life cycle in response to stimuli, together with its responses and actions. The design phase should produce detailed class diagrams, collaboration diagrams, sequence diagrams, state diagrams, and activity diagram. However, the elevator problem is too simple for an activity diagram. Thus, we are not using an activity diagram for the elevator problem. Sequence Diagram

A sequence diagram and collaboration diagram conveys similar information but expressed in different ways. A Sequence diagram shows the explicit sequence of messages suitable for modeling a real-time system, whereas a collobration diagram shows the relationships between objects.

Sequence Diagram for Serving Elevator Button

Sequence Diagram for Serving Door Button Collaboration Diagram

Describes the set of interactions between classes or types Shows the relationships among objects

Collabration Digaram for Serving Elevator Button

You might also like