Rose top-level model views

Rational Rose® required the use of the following views in every model: use case, logical, component, and deployment. While all Rose models import using this model organization structure, you are not required to keep your models organized in the same way within Rational® Software Architect or Rational Software Modeler.

The top-level model views are often referred to as the 4+1 or 3+1 view of UML diagrams. In Rose, each view represents a different way to look at the same system you are modeling, but from different levels of abstraction.

Compared to Rose, you have more freedom to organize your model at a higher level. Upon import, each use case, logical, component, and deployment view will appear in Software Architect and Software Modeler, but as top-level packages. Software Architect and Software Modeler give you the flexibility to capture architectural views as separate models, or as actual diagrams in the models that they are views of; for example, you can model the use-case view as a diagram in the use-case model file.

Related concepts
Model-driven development
UML modeling and visual editing
Transformations
Multiple model approach versus Rose controlled units
Model property sets and UML 2.0 profiles
Terms of use | Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.