Rusty,
Actually, looking at the RUP, I do not quite see it that way... Please see
inline.
I hope this helps clarify a bit of what is happening...
/Charles
| -----Original Message-----
| From: Williamson, Rusty [mailto:[EMAIL PROTECTED]]
| Sent: Tuesday, November 21, 2000 13:52
| To: 'Couball, James'; 'Rose Forum'
| Subject: RE: (ROSE) Use Case Activity Diagram Location...
|
|
|
| James,
|
| So its true, the convention Rational now supports says to
| place a) activity
| diagrams detailing use case scenarios (external view of what
| the system
| does), and b) activity diagrams detailing analysis classes
| and/or design
| classes collaborations (internal view of how the system does it)
| both together in the Logical View, under Use Case
| Realizations. Effectively
| you only use case diagrams go into the use-case model.
Not quite... You can and should place the activity diagrams in the use case
view, especially when it comes to your point (a) above. I do not usually
use activity diagrams in the logical view as I find that using
collaborations and sequence diagrams better fit my needs when trying to
wrangle classes out of the use cases.
You can look in the RUP under "Artifacts -> Requirements Set -> Use Case ->
Guidelines -> Activity Diagram".
Personally, I would also surmise that you could place sequence diagrams in
the use case view iff they are _requirements_. For example, in the telecom
industry, some specifications actually come as sequence diagrams. It then
makes sense to include these (and to actually have a reusable library...) in
the use case view as they are part of the "Requirements Set" of artifacts as
described in RUP. This may not be indicated as such in RUP, but let's not
forget that that process is flexible... If you chose to do so, I would be
careful to only use _objects_ in those sequence diagrams and to resist the
urge to create classes for these objects. The classes should be defined as
part of the Use Case Analysis.
| Wow, it would seem to me that this arrangement would be very
| awkward. If
| you follow RUP (at least as I understand it) you have system
| analysts and
| use case specifiers collecting requirements from end-users
| and customers to
| construct the use-case model. So now when this group wants
| to diagram the
| scenarios outlined in the written use cases in activity
| diagrams, instead of
| just right clicking on the use case in the use case model
| and selecting this
| option (as they could before) this group must now leave the
| use-case model
| and go over and check out the design or analysis model to create this
| diagram. Basically they'll be consulting the written version in the
| use-case model while diagramming it in completely different
| view and model.
If you look at my comments above, this would not be as awkward as you may
think. You should be careful, however, that these use case specifiers do
not try to define your system architecture by creating sequence diagrams
using actual classes!
The Analyst would then do her analysis work in the logical view under either
an "Analysis Model" or a "Design Model" (my personal preference (i.e., not
from RUP) as to which really depends on the size of the project and as to
whether there is a need to keep the analysis model separate). At this
point, user case realizations are created to link to the use case model.
The sequence diagrams can then be created an evolved to actually result in
the creation of classes. These classes can then be assigned to the objects
in the sequence (and collaboration) diagrams and further refined as need be.
You can look in the RUP under "Artifacts -> Analysis & Design Set ->
Use-Case Realization -> Guidelines",.
| Now presumably developers are working in the analysis or design model
| determining the key abstractions and, working out
| collaborating analysis or
| design classes to realize the use cases. This being the
| case, the model
| would be checked out to them and they would have to give up
| control (check
| it in) to allow the other team to check it out and created
| and/or updated
| these use case activity diagrams.
This is an issue of model partitioning for team development. Of course, you
will want to architect your software in such a way as to reduce contention
on model elements inside of Rose. As you know, this is accomplished by
proper packaging.
By moving the use case realizations and the analysis (and design) models out
of the use case view, this leaves the use case designer free to work on the
use cases. It also leaves the analyst free to work on the use case
realizations at the same time. If you had the sequence diagrams as part of
the use cases, these two workers would also face a contention problem.
Also, by correctly separating the analysis and design model, you can have
your designers and analysts work in parallel.
As you can see, this does make sense.
| Furthermore, if you're in the use-case model reading a
| complex use case
| scenario and want to know if it has been laid out in an
| activity diagram,
| you can't just right click on the use case and see if it's
| listed in the
| context menu (as you could before), now you must go over to
| another model
| and search for it.
I think that this is just a question of habit. As I mentioned above, and as
stated in the RUP, activity diagrams do belong with the use case. However,
one would have to look at the use case realization (i.e., the
"implementation" of the use case in the logical view) to see sequence and
collaborations diagrams describing the actual classes that take part in the
use case.
| Weird. And once you place these two different types of diagrams --
| "'external' view of 'what' the system does" and "'internal'
| view of 'how'
| the system does it" -- in the same model, how do you
| separate them? How do
| you attach them both to their related use case realization?
|
| You know everything I consult tells me just the opposite and
| we supposedly
| have the latest version of RUP available at this time. Can
| you possibly
| tell me where it states that all activity diagrams go in the
| Logical View,
| or that no activity diagrams go in the use-case view? I
| would really like
| to know the reasoning behind separating the written use case
| scenarios from
| their diagramed representations and placing these in
| different views and
| models. We really want to follow the latest RUP conventions
| -- but I need
| to figure out how it is suppose to work.
|
| Thanks,
| Rusty
| ------------------------------------------------------------
| Rusty Williamson
| > Sr. Systems Architect
| GERS Retail Systems
| http://www.gers.com/
| The Object Workshop
| http://home.san.rr.com/williamson/
| Home Page
| http://www.znet.com/~rusty/
| ------------------------------------------------------------
|
|
|
|
| -----Original Message-----
| From: Couball, James [mailto:[EMAIL PROTECTED]]
| Sent: Tuesday, November 21, 2000 8:33 AM
| To: 'Williamson, Rusty'; 'Rose Forum'
| Subject: RE: (ROSE) Use Case Activity Diagram Location...
|
|
| Rusty,
|
| Rational has indeed changed their mind about where these
| diagrams go. This
| advice is echoed in RUP. I think I agree with the notion of
| placing them in
| the logical view.
|
| However, I took the class you mentioned a couple of weeks ago and the
| materials were updated to indicate this... if you only
| recently took the
| class I would try to get updated materials.
|
| Sincerely,
| James.
|
| -----Original Message-----
| From: Williamson, Rusty [mailto:[EMAIL PROTECTED]]
| Sent: Monday, November 20, 2000 5:10 PM
| To: 'Rose Forum'
| Subject: (ROSE) Use Case Activity Diagram Location...
|
|
|
| Hello,
|
| We recently took the Rational OOA&D class which was very
| good, however, it
| did leave one point of confusion regarding secondary
| diagrams (activity,
| sequence and statechart diagrams) for use cases. These
| diagrams show the
| dynamic aspects of use cases (basically more detail
| regarding the primary
| and secondary scenarios found in the written use case) -- in
| other words
| they show an external view of 'what' the system does and
| would seem to me to
| be part of the use-case model. In fact the course material
| indicates that
| they are part of the use-case model and, the course CD
| contains an example
| which also shows these diagrams as part of the use-case
| model. On top of
| this, in Rose, if you right click on a use case, it offers
| the option to
| create these and, if you take this option, it also places
| them within the
| use-case model under the related use case.
|
| However (and here's the point of confusion), several
| students asked the
| instructor where these diagrams belonged and she
| specifically told them that
| 'now' the convention was to place these diagrams in the
| Logical View under
| the use case realizations.
|
| Does anyone know anything about this? Are we mistaken, or
| does Rational now
| say to place these diagrams with the use case realizations
| in the Logical
| View?
|
| Thanks!
| Rusty
| ------------------------------------------------------------
| Rusty Williamson
| > Sr. Systems Architect
| GERS Retail Systems
| http://www.gers.com/
| The Object Workshop
| http://home.san.rr.com/williamson/
| Home Page
| http://www.znet.com/~rusty/
| ------------------------------------------------------------
|
|
|
| *************************************************************
| ***********
| * 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
*
*************************************************************************
************************************************************************
* 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
*
*************************************************************************
