> In Rational Unified process each stage of the development results in a
> model. How to move from Domain model to Analysis model to Design model
> using Rational Rose? For example, should we place all the classes
> generated during the Analysis into Use Case View and during Design -
> into Logical View? Or should we start with each model "from scratch",
> with a clean slate?
> Also, how do you resolve names, e.g. you have "Flight" entity in you
> business model and "FlightEJB" bean with Flight interface in your Design
> model? Or you have "Customer" actor and "Customer" entity? What is the
> recommended strategy?
> Michael Misha Shengaout
If I understand correctly, your problem involves structuring your rose
model, and flowing from one model to the other; from the use case model, to
the analysis model, to the design model.
For an example of how to structure and RUP project using Rose, you can
create a new project, and select the RUP template that comes with Rose.
You'll notice is uses something called Realizations (use cases with dashed
lines). Realizations are a mechanism that allows you to maintain
traceability across your models. They allow you to make the "link" between
In a nutshell, using them goes something like this,
You begin by working on your use case model, documenting the requirements of
You prioritize the use cases
You move into the analysis model, and create a Use Case Realization that
traces to a use case in the use case model
You create the business objects, collaborations, state diagrams, etc ..
associated with that use case.
You move into the design model, and create a Use Case Realization that
traces to an analysis model realization.
You create the class diagrams, sequence diagrams, etc ... associated with
that use case.
This whole process allows you maintain traceability in your project. i.e.:
you can trace a design class all the way to the requirement(s) that was
create to fulfill.
You can use traceability to help solve your other problem as well. The
FlightEJB interface can "trace" to the Flight entity. As for having 2
classes with the same name, it's not a problem if you manage it the
Hope this helps,