Hi,
I am
kind new in RUP model, so I will quote from RUP not from
my experience. Actually I am taking a test project from requirements
to the implementation and I am in the analysis phase.
From the Analyse Model
description:
"Normally, "analysis classes" will evolve directly into
elements in the Design Model: some become design classes, others become design
subsystems. The goal of Analysis is to identify a preliminary mapping of
required behavior onto modeling elements in the system. The goal of Design is to
transform this preliminary (and somewhat idealized) mapping into a set of model
elements which can be implemented. As a result, there is a refinement in detail
and precision as one moves from Analysis through Design. As a result, the
"analysis classes" are often quite fluid, changeable, and evolve greatly before
they solidify in the Design activities.
"
From
the same source i exctracted that the Analyse Model is used when you target
diferent environment with separate design architecture, when you want to train
new team members, or if the system is very big and lasts
long.
Hope
it helps,
Dan
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Keysers, Wonne
Sent: Friday, January 25, 2002 10:03 AM
To: '[EMAIL PROTECTED]'
Subject: (ROSE) Analysis -> designHi,
When opening the RUP model which comes with rose, there is an
Analysis Model and Design Model package.
Question: what should reside in each of those packages?During analysis, resulting objects are still at rather high level of abstraction. (boundary, entity or control) When going from analysis, do we re-use the analysis classes or do we create new ones?
The second option is the easiest one, but then the analysis diagrams, which are a nice documentation of the overall functionality of the system, are lost.
Anyone?
Thanks
Wonne
