| vandy wrote
Adrian,
Please can you explain in more detail about the Use Case Model Survey. Also, my other question is how do you manage use case diagrams when the actor has a lot of use cases to deal with. I know packaging is one way but were wondering if there is any others.
Thanks.
Vandy |
Hi Vandy,
The Use Case Model Survey describes (at high-level) all the significant/main use cases for a given project. It will contain the Use Case Diagram(s) and it will have a short textual description of each use case (not the details). This type of document provides high-level executives and new project members with a quick and easy to understand overview of the features supported by the given system.
On your other questions, if the same actor truly interacts with many use cases, then braking down your model into packages by logical functional areas is probably a good solution. Another thing to consider when an actor uses many, many use cases is whether your actor is too generic.
Example:
- If you are modeling use cases for a financial services company don't just have an actor called "Customer" but, in addition, have other types of actors (aka roles) such as: Retail Banking Customer", "Auto Insurance Customer", "Life Insurance Customer".
- All these specialized actors can inherit from the more generic "Customer" actor which can be shown to interact with the use cases which apply to all types of customers such as: "Update Contact Information", "Request Catalog of Services".
- Then, each specialized actor would interact with the Use Cases for the given domain: "File Auto Claim" use case for the "Life Insurance Customer", "Deposit Funds" use case for the "Retail Banking Customer".
Remember that there is rarely a one to one mapping between the job titles in an organization and the actors in the use case model.
- Adrian