Use Cases - Finding Use Cases - Subject
6 important questions on Use Cases - Finding Use Cases - Subject
What is the Subject of a Use Case?
When you first attack a problem, the Subject would be the entire system.
But what is the Subject in large projects?
If your project is large and uses a divide-and-conquer approach, such as decomposition, each subsystem would become a Subject when the work is at the subsystem level.
From the perspective of each subsystem, however, any other communicating subsystem would be an Actor (an external source or sink of information, events, or data).
Therefore, in one model, a model element may be a Subject, but in a different model, the same element may be an Actor, depending on what you are concentrating on for your System of Interest.
Why is the right actor a box ?
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
How do we represent the Subject?
What is an other name for the Subject and why?
As more than one system can offer up the same
Use Case, a Use Case can appear within multiple System Boundaries.
In Fig. 12.10, we show a metamodel diagram indicating the relationship between Subjects and Use Cases.
What can we conclude from this?
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding