![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Extension Points in Rhapsody Topic Summary: Created On: 18-May-2006 10:43 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Just wondered how people might be using Rhapsody for use case extensions?
In brief, one use case may extend another -- you put an <<extends>> dependency between the use case that is doing the extending and the use case that is being extended; you mark an extension point in the sequence of operations in the use case that is being extended; you show a sequence of operations that do the extension in the use case that is doing the extension. See Cockburn and others. In Rhapsody the support is: a) You can draw <<extends>> on use case diagrams. b) You can list extension points in use cases (but the list doesn't seem to do anything more than allow text input). But what I don't see is anything explicit in sequence diagrams to mark an extension point (where an extending use case can hook in) or to indicate what extension point a sequence is intended to hook. I imagine that what I could do is c) Put a condition mark in a sequence diagram with a name that matches the name of an extension point d) Put a text comment at the top of a sequence diagram that is doing the extending, referencing the name of the extension point. But it's all rather informal. Are there better ways? |
|
![]() |
Telelogic Rhapsody
» Rhapsody Category » Rhapsody
»
Extension Points in Rhapsody
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.