Structured Use Case Model

The Structured Use Case Model pattern creates elements and a Use Case diagram of a structured Use Case model where common text is factored out using the Include relationship and special functionality is removed and modeled using the Extend relationship. Specialized functionality is also modeled using the Generalization relationship

Figure 1. Shows a Use Case Diagram that has bees structured by the use of the Include, Extend and Generalization relationships
Discussion
The purpose is to have a model that represents the value that Actors (user roles) want to derive from the system. The structured model enables Business Analysts to factor out common text and to common functionality.

The pattern is typically used after some analysis has been completed and there is an understanding of a simpler Use Case Model. The structured model will help an implementation team by removing any redundancies and specialized text and behavior.

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the System Boundary to suit the initiative.
Change the name of the Actors and Use Cases to suit the initiative.
Add descriptions to describe the value the Use Case offers.

The following is a list of some of the next steps available when applying the pattern.
·	Use the Scenario Builder to define the detailed steps in one or more Use Cases.
Generate a behavioral diagram that describes the detailed steps visually.
Create trace relationships between the Use Case and Requirements.
Create Realization relationships between the Use Case and Components that implement them.

Useful Workspace Layouts Design | Use Case Modeling, Requirements
Reference
The following help topics will assist you learn about how to work with this pattern.
Use Case Diagram
System Boundary
Use Case
Actor

The following are some of the tools that will be helpful when working with this pattern.
Scenario Builder
The Scenario Builder is a productive and unique tool and editor that allows the analyst to work with the text of Use Cases and Scenarios directly inside the model. Many analysts will be familiar with creating long and voluminous Word Processor documents describing the details of Use Cases. With the Scenario Builder the descriptions and steps of Scenarios can be entered directly into the repository and linked to other elements. Alternate and Exception paths can be defined including branch and re-entry points. Diagrams representing the steps in a scenario can be generated and automatically synchronized. For more details see the Scenario Builder help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.