Hi Jie,
that is also my opinion.
About "reverse engineering", you will have to do that manually.
Lars
-----Original Message-----
From: Jie Zhao [mailto:[EMAIL PROTECTED]]
Sent: 9. februar 2001 14:52
To: 'Lars Hauschultz '; Jie Zhao; 'Rose Forum (E-mail) '
Subject: RE: (ROSE) When should the subsystems be identifed
Thanks, Lars.
The subsystems identified during the system design activity(specifically
architecture design) will have clearly specified interfaces, which the
subsystems have to realise, implement. Basically, the interfaces represent
responsiblities of the subsystem, and in another words, they could be the
source information to the identification of use cases of the subsystem if
you want to do the use case model of the subsystem. After all the interfaces
of the subsystems provide the key information for other systems to know
whether they can be reused or not.
BTW, any ideas about reverse engineering a clas dagram into a use case
diagram?
Jie
-----Original Message-----
From: Lars Hauschultz
To: 'Jie Zhao'; Rose Forum (E-mail)
Sent: 09/02/2001 12:46
Subject: RE: (ROSE) When should the subsystems be identifed
Hi Jie,
for the time being, we are working on a project, where the subsystems
have
been identified already at the inception/requirement level. In this case
it
was pretty obvious, because the subsystems are separated geographically.
Also, the choice of which functions to implement in which subsystem has
a
strong impact on the functional behaviour of the entire system. So, here
I
would say: If identifying subsystems leads to changes in the system
behaviour, you should model subsystem behaviour up front.
If subsystems emerge during the design process, they will be modelled
automatically by the class specifications. If a specific subsystem use
case
model is needed, e.g. if the subsystem is to be used as part of other
systems as well, one would have to "reverse engineer" the class design
to
use cases.
Lars Hauschultz.
-----Original Message-----
From: Jie Zhao [mailto:[EMAIL PROTECTED]]
Sent: 9. februar 2001 12:09
To: '[EMAIL PROTECTED] '; '[EMAIL PROTECTED] '
Subject: RE: (ROSE) When should the subsystems be identifed
Thanks for you all to give your thoughts.
The original question I asked was when we should identify the subsystems
of
a large supersystem. I would say at the very early stage, probably early
iterations in the inception phase. And if this is the case is there any
systematic approach/methodology to guide the activity?
Jie
-----Original Message-----
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: 09/02/2001 10:55
Subject: AW: (ROSE) When should the subsystems be identifed
In my opinion a Use Case is the description of a (relativ) small
process, e.g. UC_GiveAccountInfo. This UC can depend on other UCs, e.g.
UC_Login. The dependencies between them you show in a use case diagram.
UML 1.3 "UML Semantics 2 - Part 3 Behaviour - Use Case - Associations":
extend
a collection of Extend relationships to UseCases that the UseCase
extends
extensionPoint
defines a collection of ExtensionPoints where the UseCase may be
extended
include
a collection of Include relationshops to UseCases the the UseCase
includes.
I hope this helps
Mit freundlichen Grüßen
Jan Matèrne
RZF NRW
Sachgebiet 314-P Software-Entwicklungs-Methoden
Fiscus AFG NW 42 SoftwareEntwicklungsUmgebung
Internet: [EMAIL PROTECTED]
-----Ursprüngliche Nachricht-----
Von: Teguh Raharjo [SMTP:[EMAIL PROTECTED]]
Gesendet am: Freitag, 9. Februar 2001 11:44
An: 'Jie Zhao'; '[EMAIL PROTECTED]'
Betreff: RE: (ROSE) When should the subsystems be identifed
As I know from the "Building Web Application with UML" book by
Jim Conallen,
we can divide the system into packages.
A use case model is often divided into packages, each of which owns a
set of
use case or even other packages.
example :
I assume that if we have a large system (ex. Accounting Information
System),
we can divide it into :
- GL package, AP package, AR package, etc
Each package may contain use case.
But I don't know whether the use case can be break down into
smaller
(detailed) use case. Refer to the UML concept we can't break down use
case
(it is not like DFD).
please corrent my assumption and give your idea ...
thanks
teguh
-----Original Message-----
From: Jie Zhao [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
]
Sent: Friday, February 09, 2001 4:57 PM
To: '[EMAIL PROTECTED]'
Subject: (ROSE) When should the subsystems be identifed
From my knowledge gained from Rational OOAD Course, subsystems
will not be
identified until doing architecture design after finishing use case
analysis. My questions are:
1. If it is a quite large system, should/Could the subsystems be
recognised
and the supersystem can be divided into a number of subordinate
subsystems.
Then start to identify the actors, use cases for the supersystem and
individual subsystem respectively.
2. If the subsystems are found during architecture design as I
have learnt
from OOAD course, do we need to identify the actors and use cases for
each
subsystem before we start to design the subsystem, or as the OOAD course
suggested what we should do is to identify the subsystem elements within
the
subsystem and distribute the subsystem behavior to subsystem elements.
Any thoughts, thanks!
Jie
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
<http://www.rational.com/support>
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
<http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl>
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
<http://www.rational.com/support>
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
<http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl>
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
