- Forum
- General C++ Programming
- Use Case
Use Case
Have I solved this task right Guys
With a use case
You should use the software of the control unit
electric escalator design. The following
Information was in a workshop with the
Customers and the manufacturer of the stairs collected:
The escalator should have a capacity of 1,800
People / h have. She should drive pleasantly and
Start and stop in a reasonable quiet.
In standard operation, the escalator is to be operated automatically and should be in the
Initial state (i.e., not driving). When driving, the escalator should not be loud
Generate noises. After the first calculations, the journey time is from bottom to bottom
above and from top to bottom each tf = 20s.
Occurs in the initial state, a person on the lower contact plate A, so the escalator moves
up. If no other person on the contact plate A while driving, the stop
Stairs after the journey time plus buffer tges = tf + tp = 20s + 10s = 30s. Kick another person
on the contact plate A, then the period until the stop (ts) starts again. Kicks in during the
Driving up a person on contact plate B, this remains unconsidered. The
Contact plates should trigger noticeably when stepped on and react quickly.
For the triggering of the upper contact plate B, the above applies in the reverse direction,
the travel and buffer times are identical when driving up and down.
The staircase has an emergency stop button that stops the stairs for the time tnot = 60s;
After the 60s, the escalators are back in their original condition. In addition, has the
Staircase a service counter with key, with which a technician escalates
Regardless of the standard operation above, steer the stairs up and down
let go and test the emergency.
task:
For the described escalator control, a use case diagram is to be created in UMLNotation. Take advantage of the below-mentioned use cases, supplement
They all necessary elements of a use case diagram and add also the
Relationship types between the use cases. Add further use cases
if it requires modeling.
Use cases:
Downhill
drive up
Trigger the contact plate
Press emergency stop
Test emergency stop
Perform service
Run standard operation
My sketch:
https://s17.directupload.net/images/190212/lxl5elm5.png
With a use case
You should use the software of the control unit
electric escalator design. The following
Information was in a workshop with the
Customers and the manufacturer of the stairs collected:
The escalator should have a capacity of 1,800
People / h have. She should drive pleasantly and
Start and stop in a reasonable quiet.
In standard operation, the escalator is to be operated automatically and should be in the
Initial state (i.e., not driving). When driving, the escalator should not be loud
Generate noises. After the first calculations, the journey time is from bottom to bottom
above and from top to bottom each tf = 20s.
Occurs in the initial state, a person on the lower contact plate A, so the escalator moves
up. If no other person on the contact plate A while driving, the stop
Stairs after the journey time plus buffer tges = tf + tp = 20s + 10s = 30s. Kick another person
on the contact plate A, then the period until the stop (ts) starts again. Kicks in during the
Driving up a person on contact plate B, this remains unconsidered. The
Contact plates should trigger noticeably when stepped on and react quickly.
For the triggering of the upper contact plate B, the above applies in the reverse direction,
the travel and buffer times are identical when driving up and down.
The staircase has an emergency stop button that stops the stairs for the time tnot = 60s;
After the 60s, the escalators are back in their original condition. In addition, has the
Staircase a service counter with key, with which a technician escalates
Regardless of the standard operation above, steer the stairs up and down
let go and test the emergency.
task:
For the described escalator control, a use case diagram is to be created in UMLNotation. Take advantage of the below-mentioned use cases, supplement
They all necessary elements of a use case diagram and add also the
Relationship types between the use cases. Add further use cases
if it requires modeling.
Use cases:
Downhill
drive up
Trigger the contact plate
Press emergency stop
Test emergency stop
Perform service
Run standard operation
My sketch:
https://s17.directupload.net/images/190212/lxl5elm5.png
You are using a truly awesome English translator!
Ouch!!
Ditto!
This just gets ever more painful!
I keep telling my wife this!
| Customers and the manufacturer of the stairs collected: |
| Kick another person on the contact plate |
| Driving up a person on contact plate B |
| Regardless of the standard operation above, steer the stairs up and down |
This just gets ever more painful!
| She should drive pleasantly and start and stop in a reasonable quiet. |
Last edited on
Its the google translatet :)
Is the task a) correctly solved ?
Or are there some mistakes ?
I also solved the b) task now :)
Please look if it s correct
The standard operation of the escalator is to be modeled as a state diagram. That You do not have to look at the service operation (!). Use only the states shown below and avoid unnecessary transitions. Use the UML notation and label the transitions exactly according to the scheme "Event [Condition] / Action".
https://s17.directupload.net/images/190212/32igdd5q.png
Is the task a) correctly solved ?
Or are there some mistakes ?
I also solved the b) task now :)
Please look if it s correct
The standard operation of the escalator is to be modeled as a state diagram. That You do not have to look at the service operation (!). Use only the states shown below and avoid unnecessary transitions. Use the UML notation and label the transitions exactly according to the scheme "Event [Condition] / Action".
https://s17.directupload.net/images/190212/32igdd5q.png
What language do you speak?
No, the translator didn't translate properly. Didn't understand anything.
No, the translator didn't translate properly. Didn't understand anything.
No, you did not correctly solve the problem. Your state machine has no way to get into the Downhill and Drive Up states. Also, there is no transition information listed explaining how to transition from those states back to the Trigger Contact Plate state. So, this implies you don't understand how state machines should be assembled.
More fundamental, however, is the fact that you are confusing use cases with state machines. A state machine represents a system's various states of being (elevator door open, door closed, going up, going down, etc.) and the inputs that cause the system to change state (push button, plate contact, reach next floor, etc.)
A use case is a specific path through the state machine to achieve a specific use (or purpose). I want to go "downhill" from the 5th floor to the 1st floor. I hit the emergency stop button. etc.
So, don't take your use cases and make them states in your state machine. Instead, think about what things have to happen in each use case, and figure out what states you need to carry them out.
More fundamental, however, is the fact that you are confusing use cases with state machines. A state machine represents a system's various states of being (elevator door open, door closed, going up, going down, etc.) and the inputs that cause the system to change state (push button, plate contact, reach next floor, etc.)
A use case is a specific path through the state machine to achieve a specific use (or purpose). I want to go "downhill" from the 5th floor to the 1st floor. I hit the emergency stop button. etc.
So, don't take your use cases and make them states in your state machine. Instead, think about what things have to happen in each use case, and figure out what states you need to carry them out.
Last edited on
Now better Guys ?
https://s17.directupload.net/images/190212/l9gslgd6.png
Should I make also an arrow from to drive up to output state? ( no contact Plate triggered[30seconds]/no one triggered
The same thing for drive down to output state?
https://s17.directupload.net/images/190212/l9gslgd6.png
Should I make also an arrow from to drive up to output state? ( no contact Plate triggered[30seconds]/no one triggered
The same thing for drive down to output state?
Last edited on
This is a much better state machine.
I don't know if it answers the original question, because the translation is so bad, we really don't know what was asked.
I don't really know how the 30 sec. applies, so I don't know if there should be another transition.
The phrase "Start and stop in a reasonable quiet." implies that you probably don't want to go immediately from drive up to drive down. You probably want "slowing" states to ease the comfort on the elevator.
Unfortunately, I don't have time to try to decipher the translated question and do the state machine design myself.
I don't know if it answers the original question, because the translation is so bad, we really don't know what was asked.
I don't really know how the 30 sec. applies, so I don't know if there should be another transition.
The phrase "Start and stop in a reasonable quiet." implies that you probably don't want to go immediately from drive up to drive down. You probably want "slowing" states to ease the comfort on the elevator.
Unfortunately, I don't have time to try to decipher the translated question and do the state machine design myself.
Trying to "translate the translation," here is what I came up with:
Your task is to write software to control an escalator.
The following information was collected in a workshop with the
customers and manufacturer of the escalator:
- The escalator should have a capacity of 1,800 people/hr.
- It should drive pleasantly and start/stop reasonably quietly.
In standard operation, the escalator should operate automatically. It
should begin in the Initial state (i.e., not moving). When moving, the
escalator should not generate noises.
The time to transport a person in either direction is tf=20s.
When in the initial state, if a person steps on the lower contact
plate A, the escalator starts moving up. If no other person steps on
contact plate A while the escalator is moving, it stops after the
transport time (tf) plus a buffer (tp=10s). So the total running time
tges = tf + tp = 20s + 10s = 30s.
If another person steps on contact plate A, then the period until the
escalator stops (ts) begins again. If a person steps on the upper
contact plate (B) while the escalator is going up, then this remains
unconsidered.
The escalator should react quickly when someone steps on the contact plates.
When someone steps on the upper plate B the above applies in the
reverse direction. The travel and buffer times are identical when
driving up and down.
The escalator has an emergency stop button that stops the stairs for tnot = 60s.
After the 60s, the escalator returns to its original state.
In addition, the escalator has a service counter with key, with which
a technician operates the escalator regardless of the standard
operations above. The technician can make the escalator go up, down,
stop, and test the emergency stop.
Your task:
For the described escalator control, create a use case diagram in
UMLNotation. Take advantage of the use cases below. They all
necessary elements. Add the Relationship types between the use
cases. Add further use cases as needed.
Use cases:
Move down
Move up
Trigger the contact plate
Press emergency stop
Test emergency stop
Perform service
Run standard operation.
---------------------
I don't remember much about UML diagrams. This is more like a state machine. The machine's state might consist of:
- the travel state of the escalator (stationary, moving up, moving down).
- emergency button state (pressed, released)
- test command (none, move up, move down, stay still, test emergency button)
I'm not quite sure how to model the plates. Are they input events, or part of the state? In particular, how should you model the case where the escalator is moving up and someone steps on the down plate? What if it's moving up, then someone steps on the down plate, then someone steps on the up plate (all while it's moving up). In general, with a busy escalator, when should you stop transporting people up and start transporting the people waiting to go down?
The events might be:
- press emergency stop
- plate A/plate B pressed.
- various timers expire (moving up/down, emergency stop).
- test command entered.
That's just a first stab at the states and events.
Your task is to write software to control an escalator.
The following information was collected in a workshop with the
customers and manufacturer of the escalator:
- The escalator should have a capacity of 1,800 people/hr.
- It should drive pleasantly and start/stop reasonably quietly.
In standard operation, the escalator should operate automatically. It
should begin in the Initial state (i.e., not moving). When moving, the
escalator should not generate noises.
The time to transport a person in either direction is tf=20s.
When in the initial state, if a person steps on the lower contact
plate A, the escalator starts moving up. If no other person steps on
contact plate A while the escalator is moving, it stops after the
transport time (tf) plus a buffer (tp=10s). So the total running time
tges = tf + tp = 20s + 10s = 30s.
If another person steps on contact plate A, then the period until the
escalator stops (ts) begins again. If a person steps on the upper
contact plate (B) while the escalator is going up, then this remains
unconsidered.
The escalator should react quickly when someone steps on the contact plates.
When someone steps on the upper plate B the above applies in the
reverse direction. The travel and buffer times are identical when
driving up and down.
The escalator has an emergency stop button that stops the stairs for tnot = 60s.
After the 60s, the escalator returns to its original state.
In addition, the escalator has a service counter with key, with which
a technician operates the escalator regardless of the standard
operations above. The technician can make the escalator go up, down,
stop, and test the emergency stop.
Your task:
For the described escalator control, create a use case diagram in
UMLNotation. Take advantage of the use cases below. They all
necessary elements. Add the Relationship types between the use
cases. Add further use cases as needed.
Use cases:
Move down
Move up
Trigger the contact plate
Press emergency stop
Test emergency stop
Perform service
Run standard operation.
---------------------
I don't remember much about UML diagrams. This is more like a state machine. The machine's state might consist of:
- the travel state of the escalator (stationary, moving up, moving down).
- emergency button state (pressed, released)
- test command (none, move up, move down, stay still, test emergency button)
I'm not quite sure how to model the plates. Are they input events, or part of the state? In particular, how should you model the case where the escalator is moving up and someone steps on the down plate? What if it's moving up, then someone steps on the down plate, then someone steps on the up plate (all while it's moving up). In general, with a busy escalator, when should you stop transporting people up and start transporting the people waiting to go down?
The events might be:
- press emergency stop
- plate A/plate B pressed.
- various timers expire (moving up/down, emergency stop).
- test command entered.
That's just a first stab at the states and events.
Topic archived. No new replies allowed.