Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Use Case Toolbox
The Use Case Toolbox is used to model the system functionality from the perspective of a system user; Use Case objects are used to build the Use Case models, which describe the functionality of the system to be built, the requirements, the constraints and how the user interacts with the system.
Sequence diagrams can be associated with Use Cases to capture work flow and system behavior.
Use Case Toolbox pages
Image |
Detail |
See also |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
A system user is called an Actor and is drawn as a stick figure, although this could represent another computer system or similar. A Use Case element defines a discrete piece of functionality the system provides for the user to either perform some piece of work or generate something of value using the system. Examples of Use Cases are: login, open account, transfer funds, check balance and logout; each of these implies some purposeful and discrete functionality the system is to provide to a user. A Test Case describes what must be set up in order to test a particular feature. The connectors available include:
The Basic Use Case icon adds the Basic Use Case Pattern to your diagram as a starting point for developing the diagram (drag the icon onto the diagram to open the Add Pattern <name> to Diagram dialog and click on the OK button).
|
|
Notes
• | To add an element to the currently-open diagram, click on the appropriate icon and drag it into position on the diagram; set an element name and other properties as prompted |
• | To add a relationship, click on the appropriate icon, then click on the start element in the diagram and drag to the end element |
Learn more