Domain Objects :-
) Pattern- It will follow
Elevator - Here is the State
1. Floor Button(will contain the list of floor
buttons in elevator)
2. elevator Request it will contain the elevator
requests in ascending order if direction is UP
otherwise it will contain in descending order
if direction is DOWN.
3. Current Direction(UP or DOWN)
4. current Floor
5. current State(Running/Idle/Maintenance etc)
Here is the behavior
6. run(...) :- It will process the elevator Request
till it is empty. if list is not empty, it will set its
state to Running , set the direction based on
comparison of it current Floor and any
request in elevator Request and print
running . Tt will also check the each elevator
Request in list elevator Requests in
sequential order and check if it is equal to
get current Floor(). If yes print "Reached
Floor" + current Floor. Else make the state
as Stopped
7. set Current Floor() :- Whenever elevator
reach to any floor , it will call this method to
set the current Floor.
8. Open Door()
9. close Door()
10. reset()
Button -
1. Floor Button (Button inside elevator to place
elevator request)
2. Direction Button(Button outside elevator to
call elevator)
Elevator Request
1. Floor Number
2. direction
3. time
Controller/Business Objects :-
Elevator Controller - For handling http request
and delegate it to Elevator Request Manager
1. process Elevator Request(..)
2. process Floor Request(..)
Elevator Schedule Manager - To place the
request we can use different kind of strategies
like time based, direction based etc. Here i will
use Direction Based Strategy. Here is the
Direction Based Strategy
1. process Request(...
factory pattern to create the one of the child
object of strategy based on parameter(can
be configured in property file)
Direction Based Strategy -
1. It will check the current State of elevator,
2. If Elev is in Idle state, it will place the floor
Request in list named as Elevator Request.
Else call Elevator Request Manager to place
the request in set(Tree based) pending
Requests
3. If Elev is in Running state, it will get the
current Direction . If it matches with Elevator
Request direction and current floor is less
than Elevator Request floor it will place the
request in floor Request list. Else call
Elevator Request Manager to place the
request in set pending Requests I have
chosen the Tree Set so that request can be
stored in in order of time and does not
contain duplicate entries
4. Process Request(...)
Elevator Request Manager- This will place the
Elevator Request in some data structure like list.
Here we wil two classes Downward Elevator
Request Manager and Upward Elevator Request
Manager
1. process Request(...)
2. process Pending Request(...) This method
will start the thread that will keep on running.
This will again use the Direction Based
Strategy. This will poll the pending Requests
to pick the requests in the same direction
until the last request in that direction. Once
all the requests are picked , it will remove the
requests from pending Requests and put it in
elevator Request and call run method on
elevator. To pick the move direction , it will
pick the direction from first request under
pending Requests(it already contains the
request in time order)