Doubt in the Representation of Use Cases

Question

Doubt in the Representation of Use Cases

Navigation

#1 by (1 votes)

1

From the link Difficulty of Abstraction in Use Cases , I made the following interpretation:

"Only the attendant can confirm the sending of the request, but for this it is necessary to have the order finish, which can only be done by the pizzaiolo. order is required that the customer make the payment and in turn it is necessary to make the request by it ". Is this reading shown in the diagram correct? If it is correct, this confuses me a lot because the function of the Use Case Diagram is to represent the goals of each actor, and should not represent those goals in a sequence of steps to be done as in the Activity Diagram, but we can see in this example that there is a flow to be followed.

uml

asked by anonymous 10.08.2016 / 23:38

1 answer

Problems in Java project with CDI (Weld) + Hibernate + PrimeFaces Call method within URL in Laravel

score 1 · Accepted Answer

The diagram documents what the system does from a user's point of view. It describes the main features of the system and the interaction of these features with users of the same system. In this type of diagram it is not necessary to go into the technical details that say how the system does the actions (Language, DBMS etc).

In this case, everything that the Customer User can do is represented, which is to register, to order and to pay. The Attendant user can only confirm the sending of the request. The Pizzaiolo User can consult request and finish order.

The entire flow of the system is represented, but also the actions of each actor, and can be analyzed both individually and together, so the representation is correct. The activity diagram is different from this, because it includes a logic to represent the flow of activities, it is usually closer to an algorithm.

In Summary: Use Case Diagram is a representation in a System User's View, with simple explanations and no technical detailing. Activity Diagram, is a representation of the flow, containing logic, next to an algorithmic representation of the system.