Понятно, или все в отпуске, или жарко, или не покупаетесь на провокацию
Не реально. На Use Case Professionals
я опубликовал ответ. На всякий случай повторю часть комментариев
Hi, gays. Tell me exactly is the UC good enough?
UC 01: Make the order
The employee made the order, received a receipt with the bar code
1. The employee is logged in the system.
2. The system provided a menu to place your order.
The main flow:
1. While the employee chooses the desired dish
2. The system displays the dish and the price in the order list, counting the total cost of the order
3. The employee confirms the order
4. The system saves the order and prints a receipt
1. The system displays a screen with the original menu of dishes
2. The system ends the session
3. Order is stored in a "proposed" state
1/ There is your outstanding order
2/ Reorder during the day
3/ Remove the chosen dish
4/ Change the number of meals
5/ The chosen dish is over
6/ Cancel the order
Т.е. я взял исходный текст ВИ пропустил его через гугл-переводчик и чуть подправив опубликовал
а вот ответ
Great example, Edward, Perhaps we can pitch in and critique Edward's example and eventually come up with a "good" use case. Rather than suggest suggestions, let's point out issues, and once we agree on the issues, then Edward might offer ways to correct the issues.
Allow me to begin:
Often when I work with people who have a first language other than English, we have to be really careful to make sure that the intentions of the author and the understanding of the reader is consistent. Some of my questions are about the vocabulary used, which, while grammatically correct, may be inconsistently understood.
The title "Make an Order" is too vague; the word "make" could imply constructing, assembling, or placing an order.
The description didn't tell me much. It wasn't until I read the alternative flows that I figured out that the order has something to do with ordering food.
Why is the actor an "employee"? That's a pretty vague term. What is the role? Does the system care that only an employee can order food?
Precondition 2: At first I thought that the word "menu" constrains the design of the system, but the word "menu" in a food ordering system might be exactly right.
What is the state of the "order" prior to the start of the use case?
1. Why is the word "while" in the first sentence? Why did you use the word "dish"?
2. "counting" implies incrementing the number of items ordered. Did you mean "calculating", to add the cost of the dish to the current order giving a new total cost?
3. Could the employee order more than one item?
4. This is 2 requirements: Do they have to be done in this order? Does it have to save it, or could it transmit it somewhere else?
Alt flows: Do these have the same preconditions as the main flow?
Post conditions: I still don't understand the context of this use case: an employee at a cash register at McDonalds? Taking orders for room service in hotel? A restaurant? Over the phone? Could the diner or meal preparer order a dish?
Re-ordering during the day....not sure what "re-order" implies?
Thanks Edward, this was a good start!
Правда, много интересного?