The package is the main organizational artifact within ArgoUML. In
the UML metamodel it is a sub-class of both Namespace
and GeneralizableElement.
![[Note]](images/note.png) | Note |
|---|---|
ArgoUML also implements the UML | |
ArgoUML also implements some less common aspects of UML model
management. In particular the relationship UML 1.3 defines as
Generalization and the sub-class dependency
Permission for use between packages.
The details tabs that are active for packages are as follows.
ToDoItemStandard tab.
PropertiesSee Section 17.2.2, “Package Property Toolbar” and Section 17.2.3, “Property Fields For Package” below.
DocumentationStandard tab. See Section 12.5, “Documentation Tab”.
StyleStandard tab. The
Bounds:field defines the bounding box for the package on the diagram.SourceStandard tab. This contains a template package declaration appropriate to the entire package. In the future this would be part of the code generation activity.
ConstraintsStandard tab. ArgoUML only supports constraints on Classes and Features (Attributes, Operations, Receptions, and Methods), so this tab is grayed out.
Tagged ValuesStandard tab. In the UML metamodel,
Packagehas the following standard tagged values defined.derived(from the superclass,ModelElement). Valuestrue, meaning the package is redundant—it can be formally derived from other elements, orfalsemeaning it cannot.Note Derived packages still have their value in analysis to introduce useful names or concepts, and in design to avoid re-computation.
Go upNavigate up through the package structure.
Add PackageThis creates a new package within the package (which appears on no diagram), navigating immediately to the properties tab for that package.
Delete PackageDeletes the package from the model.
![[Warning]](images/warning.png)
Warning 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
Remove From Diagram(or press the Delete key).
NameText box. The name of the package. The name of a package, like all packages, is by convention all lower case, not containing any periods.
Note By default a new package has no name defined. The package will appear with the name
(anon Package)in the explorer.StereotypeDrop down selector. Package is provided by default with the UML standard stereotypes for package (
facade,framework,stub).Navigate Stereotype
icon. If a
stereotype has been selected, this will navigate to the
stereotype property panel (see Section 17.4, “Stereotype”).NamespaceDrop down selector. Records the namespace for the package. This is the package hierarchy.
VisibilityRadio box, with three entries
public,protectedandprivate. Indicates whether the package is visible outside the package.ModifiersCheck box, with entries
abstract,leafandroot.Abstractis used to declare that this package cannot be instantiated, but must always be specialized.![[Tip]](images/tip.png)
Tip The meaning of
abstractapplied to a package if not that clear. It might mean that the package contains interfaces or abstract classes without realizations. This is probably better handled through stereotyping of the package (for example«facade»).Leafindicates that this package can have no further subpackages.Rootindicates that it is the top level package.Tip Within ArgoUML
Rootonly meaningfully applies to the Model, since all packages sit within the model. This could be used to emphasize that the Model is at the top level.
GeneralizationsText area. Lists any package that generalizes this package.
Button 1 double click navigates to the generalization and opens its property tab.
SpecializationsText 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.
Owned ElementsText area. A listing of all the packages, classes, interfaces, datatypes, actors, use cases, associations, generalizations and stereotypes within the package.
Button 1 double click on any item listed here navigates to that artifact.