The package is the main organizational model element 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.4
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.
Standard-Register.
PropertiesSee Section 18.2.2, “ Package Property Toolbar ” and Section 18.2.3, “ Property Fields For Package ” below.
DocumentationStandard tab. See Section 13.4, “ Documentation Tab ”.
PresentationStandard tab. The editable
Boundsfield defines the bounding box for the package on the diagram.StereotypeStandard tab.
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.
New PackageThis creates a new package within the package (which appears on no diagram), navigating immediately to the properties tab for that package.
New DatatypeThis creates a new Datatype (see Section 16.3, “ Datatype ”) for the selected package, navigating immediately to the properties tab for that datatype.
New EnumerationThis creates a new Enumeration (see Section 16.4, “ Enumeration ”) for the selected package, navigating immediately to the properties tab for that enumeration.
New StereotypeThis creates a new Stereotype (see Section 16.6, “ Stereotype ”) for the selected package, navigating immediately to the properties tab for that stereotype.
New Tag DefinitionThis 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.
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 punctuation marks.
Note By default a new package has no name defined. The package will appear with the name
(Unnamed Package)in the explorer.NamespaceDrop down selector. Records the namespace for the package. This is the package hierarchy.
VisibilityRadio box, with four entries
public,private,protected, andpackage. 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, stereotypes, etc. within the package.
Button 1 double click on any item listed here navigates to that model element.
Imported ElementsText 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 elements.Remove. Removes the import.