|
If you
right click a use case and select new class diagram then the new diagram will be
created in the use case view under the selected use case and not in the logical
view.
The
mapping should be performed through use case realisations (a use case maps
to a use case realisation in the logical view). That is the preferred way
to do it. A use case should be purely analysis and should be abstract from
the logical view of the system. This way it is possible for Analysts to
work on the use case view with little knowledge of the logical system beneath
it. The designers can then realise the Analyst's use cases in the design
model.
This mapping can be done from usecase view also
by right clicking a use case and selcting a class diagram .
Anyway this class diagram will be created in
logical view.
----- Original Message -----
Sent: Thursday, October 04, 2001 3:18
AM
Subject: RE: (ROSE) UseCase View To
Logical View Mapping
......yes traceability is important whether one
uses iterative approach or not. Occasionally, the usecase view may
contain some business usecases that might be redundant - so in
such a case, only relevant usecases are realized !.... and hence
traceability is still maintained.
T.C.Balachandra
The point of the Use case realisation is to
provide a mapping from use cases in the use case view to the design model
in the logical view. This mapping provides traceability which is
important whether an iterative approach is being used or
not.
Usecase realistion view may be used if
u r following iterative model..i,e which helps u to know on which use
cases the work has been performed.Other wise usecase diagram in usecase
view and usecase realistion in logical view are same.
----- Original Message -----
To:
Sent: Wednesday, October 03, 2001
3:18 PM
Subject: RE: (ROSE) UseCase View
To Logical View Mapping
Through use case realizations. Each use
case has a corresponding use case realization. A use case
realization exists in the logical view and demonstrates the design
elements that participate in use case realization. It is a use
case with a stereotype of use case realization. Each use
case realization should have a minimum of three diagrams under
it: Participating classes, Dependencies and Basic
Flow. The use case realizations may also have one or more
alternative flow diagrams. The participating classes diagram is
a class diagam showing the classes from the design model that provide
the functionality to realize the use case. The dependencies
diagram is a class diagram that shows the use case realization, the
use case it realizes and relates them using a realizes
relationship. This diagram is used for the traceability between
the use case and its realization. The basic flow diagram is a
sequence diagram showing how the dynamic relationship between the
participating classes in the use case realization. It shows the
functionality required by the use case. One or more Alternative
flow diagrams may be used to show any other scenarios the may occur
for the use case. These diagrams will also be sequence
diagrams.
Hi,
What is
the mapping or how is the mapping fro the Use Case View to the
Logical View done?
Rgds,
Ameeta
___________________________________________________________________________
This
email is confidential and intended solely for the use of the
individual to whom it is addressed. Any views or opinions
presented are
solely those of the author and do not necessarily
represent those of
SchlumbergerSema.
If you are not the
intended recipient, be advised that you have received this
email in
error and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited.
If you have
received this email in error please notify the SchlumbergerSema
Helpdesk by telephone on +44 (0) 121 627
5600.
___________________________________________________________________________
|
