Colin,
okay, you want to show what is part of the old system (lets call it Sys_A),
what are the new parts in the new system (Sys_B) and perhaps what part will
exist in both systems and what is thrown away (was only in Sys_A but not in
Sys_B).
Packaging will solve the first two things (part of Sys_A and new in Sys_B),
but gives no information of this throw away things.
I think a combination of packaging and stereotyping will help. Use packaging
to show origin from Sys_A or Sys_B, and stereotyp all elements (use case,
actors, classes, ...) with the sematic: exist_only_in_Sys_A,
..._only_in_Sys_B, ...
You can invent stereotypes by yourself (typ it in the stereotype pull down
list and it will exist in that rose model).
Klaus
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im Auftrag von Colin Gourlay
Gesendet am: Mittwoch, 31. Januar 2001 11:35
An: Oppermann, Klaus; Rational Rose Forum (E-mail)
Betreff: RE: (ROSE) Use Case Boundary
Hello Klaus
I do appreciate that packages are another concept. Perhaps if I provide you
with further information you may be able (or someone else) to provide me
with an alternative means of modelling the system.
There is already a (fairly complicated system that I seem to have just
inherited) in place with no documentation whatsoever.
I thought it would be ideal to model this inherited system (an actor would
not be sufficient as my project manager etc requires to know whats going on)
and draw a boundary round this to highlight the separation between what
already exists and the new system being modelled.
It is imperative that this is modelled (cant be reverse engineered) and,
although I know it is not correct, I thought I could put it in a package to
group the inherited system separately from what I am trying to do -
considering I cannot draw a boundary.
Is there a better way of doing what I am trying to achieve?
Thanks in advance
Colin
-----Original Message-----
From: Oppermann, Klaus [mailto:[EMAIL PROTECTED]]
Sent: 31 January 2001 07:26
To: 'Colin Gourlay'
Subject: AW: (ROSE) Use Case Boundary
Colin,
packages are another concept.
System bounderies in use case diagrams shows the border between the things
inside the system (that are the use case or better thr realisation of them)
and the things outside the system (actors, the user in front of the screen
or another system). It's a definition: between use case and actors is the
system border. A UML tool can explicitly draw it and many tools do this.
Rose not; Rose says: per definition it exist, why such I draw it ;-)
Packaging UML-things, like classes oder use case, is a logically grouping
(clustering) of this thing. It's an software organisation aspect which has
normally nothing to do with the system border.
Klaus
-----Ursprüngliche Nachricht-----
Von: Colin Gourlay [mailto:[EMAIL PROTECTED]]
Gesendet am: Dienstag, 30. Januar 2001 17:00
An: Oppermann, Klaus
Betreff: RE: (ROSE) Use Case Boundary
Hello Klaus
That is unfortunate - I'll maybe just put them in packages instead as an
alternative to this.
Thanks for taking the time to respond to my query.
Best Regards
Colin
-----Original Message-----
From: Oppermann, Klaus [mailto:[EMAIL PROTECTED]]
Sent: 30 January 2001 15:51
To: 'Colin Gourlay'; 'Rational Rose Forum (E-mail)'
Subject: AW: (ROSE) Use Case Boundary
So far I know it is not possible in Rose.
Klaus
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im
Auftrag von Colin Gourlay
Gesendet am: Dienstag, 30. Januar 2001 11:15
An: Rational Rose Forum (E-mail)
Betreff: (ROSE) Use Case Boundary
I wish to create a use case boundary within my UML diagram.
I cannot see how to create one. Can anyone please advise.
I am using Rational Rose 2000
Regards
Colin
************************************************************************
* 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
*
*************************************************************************
