Is This Content Helpful?
We're glad to know this article was helpful.
A UML model that contains feature dataset, geometric networks, stand-alone feature classes and other types of classes can become very large.
To manage the model, use the following UML package hierarchy:
[define tables here]
[define domains here]
[define feature classes here]
[define subtypes of feature class A here]
For example, this would be the hierarchy of a land base model:
Domains [a package – no stereotype]
BuildingHeight [a domain]
Tables [a package – no stereotype]
Owners [a table]
Landbase [a package w/stereotype feature dataset]
Buildings [a feature class]
BuildingSubtypes [a package – no stereotype]
School [subtypes of buildings]
Visio attaches the package name as a prefix to the class. In the example above, the School class will be displayed as BuildingSubtypes::School in diagrams outside of the BuildingSubtypes package.