Chapter 16. Use Case Diagram Artifact Reference

Table of Contents

16.1. Introduction
16.1.1. ArgoUML Limitations Concerning Use Case Diagrams
16.2. Actor
16.2.1. Actor Details Tabs
16.2.2. Actor Property Toolbar
16.2.3. Property Fields For Actor
16.3. Use Case
16.3.1. Use Case Details Tabs
16.3.2. Use Case Property Toolbar
16.3.3. Property Fields For Use Case
16.4. Extension Point
16.4.1. Extension Point Details Tabs
16.4.2. Extension Point Property Toolbar
16.4.3. Property Fields For Extension Point
16.5. Association
16.6. Association End
16.7. Dependency
16.8. Generalization
16.8.1. Generalization Details Tabs
16.8.2. Generalization Property Toolbar
16.8.3. Property Fields For Generalization
16.9. Extend
16.9.1. Extend Details Tabs
16.9.2. Extend Property Toolbar
16.9.3. Property Fields For Extend
16.10. Include
16.10.1. Include Details Tabs
16.10.2. Include Property Toolbar
16.10.3. Property Fields For Include

16.1. Introduction

This chapter describes each artifact that can be created within a use case diagram. Note that some sub-artifacts of artifacts on the diagram may not actually themselves appear on the diagram.

There is a close relationship between this material and the properties tab of the details pane (see Section 12.3, “Properties Tab”). That section covers properties in general, in this chapter they are linked to specific artifacts.

Figure 16.1, “Possible artifacts on a use case diagram.” shows a use case diagram with all possible artifacts displayed.

Figure 16.1. Possible artifacts on a use case diagram.

Possible artifacts on a use case diagram.

16.1.1. ArgoUML Limitations Concerning Use Case Diagrams

Use case diagrams are now well supported within ArgoUML. There still are some minor limitations though. One is that extension points may be shown in a separate compartment on the use case, but this is not retained after saving and reloading.

[Note]Note

Earlier versions of ArgoUML (0.9 and earlier) implemented extend and include relationships by using a stereotyped dependency relationship. Although such diagrams will show correctly on the diagram, they will not link correctly to the use cases, and should be replaced by proper extend and include relationships using the current system.