Prev Next

Model Views

The top-level Packages in a model (below the Model Root nodes) can be created as Views, which are simply used to structurally partition and extend the model according to specific requirements and modeling techniques, such as Component View or Dynamic View. These Views have the same concept as the Simple UML Views generated as Model Packages; however, unlike the Model Package views, basic Views:

  • Do not have any automatically-generated components
  • Can be created only under a Model Root node
  • Are top-level Packages with different Package icons
  • Are not directly available for Requirements, Analysis or Testing, although you can develop these Views from Simple Views or within Use Case Views

Types of View

There are seven main types of View, as listed here, each identified by a specific Package icon; the types of diagram we mention are suggested content for each View type, but you can add any structures you want to any View.

  • Use Case View - containing Use Case diagrams and Analysis diagrams
  • Dynamic View -containing Activity diagrams, Communication diagrams, Sequence diagrams and StateMachine diagrams
  • Class View - containing Class diagrams, Code Engineering and Data Models
  • Component View - containing Component diagrams
  • Deployment View - containing Deployment diagrams
  • Package View - containing either Package diagrams specifically, or any other Package content raised up to the highest level in the hierarchy; this View has the standard Package icon as used across the model
  • Simple View - to customize your own type of view
Image showing the six kinds of view packages with their icons in Sparx Systems Enterprise Architect.

You can work within the first six standard View types, or devise your own type based on the Simple View.

You can create Views, change the View icon (see the Rename Views Help topic), and perform any operation available for other types of Package, by right-clicking on the selected View and choosing the appropriate context menu option.

Note that if you drag a Package from lower down in the hierarchy to just below the Model Root node, you can treat that Package as a View and change the View icon. Conversely, if you drag a View to a position lower in the hierarchy, the View icon automatically changes to the standard Package icon.

Learn more