Hi Jie,
When should subsystems be identified? Well during Inception your team should
be focused on defining the why/context/business case for your system by
concentrating on business use case analysis. Spending a lot of energy on
system design here is premature and risky. Partitioning your system into
subsystems really happens during Elaboration. How do you identify a
candidate subsystem? When you find a group of classes that send messages
between themselves, but do not collaborate much with other classes. Or even
better, if a group in your development organization with the mandate to
decrease development costs through reuse already has customizable
components/subsystems to offer you.
<<subsystems will not be identified until doing architecture design after
finishing use case analysis>>
I don't think that really follows the spirit of iterative development. Your
system use cases will probably be only named or very informally described
after Inception. During your Elaboration iterations you will be adding more
detail to your system use cases while you identify the key abstractions
(boundary, control and entity classes), architectural mechanisms (i.e.
persistency, security, distribution and legacy interface) and subsystems
needed to enact them .
-Richard
----- Original Message -----
From: "Jie Zhao" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 09, 2001 4:56 AM
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
> *
> * 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
*
*************************************************************************
