Слайд 2
Where Are We? Team-based modeling Controlled Units Virtual Path Maps Reuse Version Control
Add-Ins Model Integrator
Слайд 3
Team-Based Modeling Rational Rose supports Controlled evolution of the
model. Partitioning of models into architecturally significant units. Reuse of architecturally
significant model elements.
Слайд 4
Controlled Evolution Rose supports architecture-based modeling through the use
of UML packages and subsystems. Rose helps users work on
low-level design details without affecting the work of others. Specification of architecture-level functionality (interfaces) can be separated from specification of implementation. Rose helps users avoid creating inappropriate dependencies between architectural units. Show Access Violations report supports this.
Слайд 5
Partitioning In Rose, UML packages/subsystems can be maintained as
separate files called controlled units.
Слайд 6
Where Are We? Team-based modeling Controlled Units Virtual Path Maps Reuse Version Control
Add-Ins Model Integrator
Слайд 7
Controlled Units A package is the smallest element that
can be a controlled unit. In the UML, a package
is represented by a file folder.
Package
Слайд 8
Controlled Units A controlled unit is a model element
that can be placed under version control. The following model
elements can be
controlled units Model file itself (.mdl file) Logical View and Use-Case View packages (.cat file) Component View packages (.sub file) Deployment View diagram (.prc file) Model properties (.prp file)
Слайд 9
Controlled Units A controlled unit can be loaded or
unloaded. In Rose, a controlled unit is represented in