Tag Info

New answers tagged

0

Alistair Cockburn (The Use Case Guru) recommends to separate by different concerns called "design scopes" and "goal levels" as shown in Stack Overflow: UML Use case: Waiting for another use case to finish. See also Wikipedia: Use case for introductory signposts book Cockburn, Alistair. Writing Effective Use Cases. Addison-Wesley, 2001 (draft version #3 ...


2

The scope of a use case diagram is typically per-system. One of the symbols used on a diagram is called the "system boundary box". This is simply a box drawn around use cases and labeled with the system name. If further detail is needed, the same notation can be used to provide subsystems within a system by drawing a box around the use cases that are part of ...


4

I don't think that "be notified" should be something that is even on a use case diagram. Each use case is a sequence of steps or actions. What appears on a use case diagram is just a summary of what the full use case is, since it doesn't capture all of the steps, preconditions and postconditions, minimal guarantees, triggers, or any of the other information ...



Top 50 recent answers are included