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
*
*************************************************************************

Reply via email to