[EMAIL PROTECTED] wrote:
how would that work in practice ? I'm not familiar with these elements so I'm wondering what the user will need to do exactly in the diagram/graph will it be possible to make use-case more reusable ? will it define some kind of path between use-cases ? (end of quote) Use case extensions are good for specializing base use cases with optional behavior and cross cutting concerns. The base use case is complete by itself, its the common behavior. The extension use case isnt useable by itself, it adds specialized behavior. Ivar Jacobsen wrote an article last year equating aspects with use case extensions. Its the equivalent of splicing a fragment of an activity diagram into another activity diagram. Im guessing here, but I think the way it could work is by naming an extension point of the base use case with a point in the activity diagram. It could be an activity, or transition, or a decision point whichever is easiest to implement. The extension use case would be spliced into that point, its activity diagrams initial state and final state would be the extension point. An extension use case could be reused to extend different base use cases. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1617#1617 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
