The package is the main organizational model element within
ArgoUML. In the UML metamodel it is a sub-class of both
ArgoUML also implements the UML
ArgoUML also implements some less common aspects of UML
model management. In particular the relationship UML 1.4
Generalization and the sub-class
Permission for use between
The details tabs that are active for packages are as follows.
Standard tab. See Section 13.4, “Documentation Tab”.
Standard tab. The editable
field defines the bounding box for the package on the
Standard tab. In the UML metamodel,
Package has the following standard tagged
derived (from the
true, meaning the package
is redundant—it can be formally derived from other
false meaning it
Derived packages still have their value in analysis to introduce useful names or concepts, and in design to avoid re-computation.
Navigate up through the package structure.
This creates a new package within the package (which appears on no diagram), navigating immediately to the properties tab for that package.
This creates a new Datatype (see Section 16.3, “Datatype”) for the selected package, navigating immediately to the properties tab for that datatype.
This creates a new Enumeration (see Section 16.4, “Enumeration”) for the selected package, navigating immediately to the properties tab for that enumeration.
This creates a new Stereotype (see Section 16.6, “Stereotype”) for the selected package, navigating immediately to the properties tab for that stereotype.
New Tag Definition
This creates a new tag definition (see Section 16.7, “Tag Definition”) within the package (which appears on no diagram), navigating immediately to the properties tab for that tagdefinition.
Deletes the package from the model.
This is a deletion from the model
not just the diagram. To delete
a package from the diagram, but keep it within the
model, use the main menu
Text box. The name of the package. The name of a package, like all packages, is by convention all lower case, not containing any punctuation marks.
By default a new package has no name defined.
The package will appear with the name
Drop down selector. Records the namespace for the package. This is the package hierarchy.
Radio box, with four entries
package. Indicates whether the
package is visible outside the package.
Check box, with entries
Abstract is used to
declare that this package cannot be instantiated,
but must always be specialized.
The meaning of
Leaf indicates that this
package can have no further subpackages.
Root indicates that it is
the top level package.
Text area. Lists any package that generalizes this package.
Button 1 double click navigates to the generalization and opens its property tab.
Text box. Lists any specialized package (i.e. for which this package is a generalization.
button 1 double click navigates to the generalization and opens its property tab.
Text area. A listing of all the packages, classes, interfaces, datatypes, actors, use cases, associations, generalizations, stereotypes, etc. within the package.
Button 1 double click on any item listed here navigates to that model element.
Text Area. A listing of all imported elements, i.e. elements that are owned by a different package, but are explicitely made visible in this package.
Button 1 double click on any item listed here navigates to that model element. Button 2 gives a pop up menu with the following entries.
Add. The “Add/Remove
Imported Elements” window opens. In this
window it is possible to build a list of imported
Removes the import.