I'm studying use case and activity diagrams and I get confused about the difference between activity diagram and the normal flow specified in the use case specification table, aren't both of them specify the flow of our system ?

Use case specification table

  • 3
    Please post text as text rather than images - images are neither accessible nor searchable. Commented Nov 29, 2021 at 16:02

1 Answer 1


UML does not have strict rules for writing a use case description, and it does not have strict rules for creating activity diagrams. It is up to the analyst or architect to pick a useful level of abstraction and to make a decision about when to draw a diagram and when not. If in your working context (or learning context?) someone gave you the task to create this kind of use case spec table, the "flow of events" could be a candidate for the basis of an activity diagram, which might lead to some overlap, that should be quite obvious.

Whether you actually need to model this flow of event as an activity diagram when you already have a verbal description, or whether you think the verbal description is sufficient, depends mainly on what you choose to put in them. And for choosing, you should ultimately take into account which audience you are adressing with these models.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.