Standard tab.

See Section 17.3.2, “Use Case Property Toolbar” and Section 17.3.3, “Property Fields For Use Case” below.

Standard tab. See Section 13.4, “Documentation Tab”.

Standard tab. The Fill color is used for the use case oval.

The Display: Extension Points check box is used to control whether an extension point compartment is displayed.

Standard tab. It would not be usual to provide any code for a use case, since it is primarily a vehicle for capturing requirements about the system under construction, not creating the solution.

Standard tab.

Standard tab. In the UML metamodel, UseCase has the following standard tagged values defined.

Standard tab for a Classifier.

Navigate up through the package structure of the model.

This creates a new use case within the model, (but not within the diagram), and shows immediately the properties tab for that use case.

	Tip
	This method of creating a new use case can be confusing. It is much better to create a new use case on the diagram of your choice.

This creates a new use extension point within the namespace of the current use case, with the current use case as its associated use case, navigating immediately to the properties tab for that extension point.

This creates a new attribute within the current use case, navigating immediately to the properties tab for that attribute.

This creates a new operation within the current use case, navigating immediately to the properties tab for that operation.

This creates a new reception within the current use case, navigating immediately to the properties tab for that reception.

This creates a new stereotype within the current use case, navigating immediately to the properties tab for that stereotype.

This deletes the selected use case from the model.

	Warning
	This is a deletion from the model not just the diagram. To delete a use case from the diagram, but keep it within the model, use the main menu Remove From Diagram (or press the Delete key).

Text box. The name of the use case. Since a use case is a classifier, it would be conventional to Capitalize the first letter (and initial letters of any component words), e.g. RemoteSensor. The name is shown inside the oval representation of the use case on the diagram.

	Note
	ArgoUML does not enforce any naming convention for use cases

Text box with navigation button. Records the namespace for the use case. This is the package hierarchy.

Check box, with entries Abstract Leaf and Root.

Text area. Lists the “depending” ends of the relationship, i.e. the end that makes use of the other end.

Button 1 double click navigates to the dependency and opens its property tab.

Button 2 click shows a pop-up menu with one entry Add... that opens a dialog box where you can add and remove depending modelelements.

Text area. Lists the “supplying” ends of the relationship, i.e. the end supplying what is needed by the other end.

Button 1 double click navigates to the dependency and opens its property tab.

Button 2 click shows a pop-up menu with one entry Add... that opens a dialog box where you can add and remove dependent modelelements.

Text area. Lists use cases which are generalizations of this one. Will be set whenever a generalization is created on the from this Use Case. Button 1 Double Click on a generalization will navigate to that generalization.

Text box. Lists any specialized use case (i.e. for which this use case is a generalization.

Button 1 double click navigates to the generalization and opens its property tab.

Text box. Lists any class that is extended by this use case.

Where an extends relationship has been created, button 1 double click will navigate to that relationship.

Text box. Lists any use case that this use case includes.

Where an include relationship has been created, button 1 Double Click will navigate to that relationship.

Text area. Lists all the attributes (see Section 18.7, “Attribute”) defined for this use case. Button 1 double click navigates to the selected attribute. Button 2 gives a pop up menu with two entries, which allow reordering the attributes.

Text box. Lists any association ends (see Section 18.12, “Association”) of associations connected to this use case.

Button 1 double click navigates to the selected entry.

Text area. Lists all the operations (see Section 18.8, “Operation”) defined on this use case. Button 1 click navigates to the selected operation. Button 2 gives a pop up menu with two entries, which allow reordering the operations.

Text box. If this use case is, or can be extended, this field lists the extension points for the use case.

	Note
	Extension points are listed by their location point rather than their name.

Where an extension point has been created (see below), button 1 Double Click will navigate to that relationship. Button 2 gives a pop up menu with the following entries.