Purpose
  • To extract behavior in business use cases that need to be considered as abstract business use cases. Examples of such behavior are common behavior, optional behavior, and behavior that is to be developed in later iterations.
  • To find new abstract business actors that define roles that are shared by several business actors.
Steps
Input Artifacts: Resulting Artifacts:
Worker: Business-Process Analyst
Tool Mentors: Using Rational Rose™ to Structure the Use-Case Model

Establish Include-Relationships Between Business Use Cases To top of page

If you find that there are large portions in a workflow than can be factored out as an inclusion to simplify the original business use case, those parts can form a new business use case that is included in the original business use cases.

You should briefly describe every relationship you define.

See also Guidelines: Business Use-Case Model and Guidelines: Include-Relationship in the Business Use-Case Model.

Establish Extend-Relationships Between Business Use Cases To top of page

If you find major parts of a workflow that form an option to the normal workflow, you can factor that part out to a new business use case that is an extension to the original business use case.

Make sure that the workflow of the original business use case is still complete and understandable in and of itself.

See also Guidelines: Business Use-Case Model and Guidelines: Extend-Relationship in the Business Use-Case Model.

Establish Generalizations Between Business Use Cases To top of page

If you find workflows that structure, purpose, and behavior, you can show that in the business use-case model with use-case-generalization.

See also Guidelines: Business Use-Case Model and Guidelines: Use-Case Generalization in the Business Use-Case Model.

Establish Generalizations Between Business Actors To top of page

If two business actors interact with the same business use case in exactly the same way, they play the same role with respect to that business use case. To clarify this situation you can create a new business actor for this common role. The original business actors inherit this new business actor.

See also Guidelines: Actor-Generalization in the Business Use-Case Model.

Evaluate Your Results To top of page

You should continuously evaluate the structure of your business use-case model to make sure it is understandable to your stakeholders.

See checkpoints for business actor, business use case and business use-case model in Activity: Review the Business Use-Case Model.

Display Rational Unified Process using frames

 

© Rational Software Corporation 1998 Rational Unified Process 5.1 (build 43)