It seems to me that this IS an andromda bpm4struts modelling issue. Please excuse the silly question if this is not the case, but I will try to explain what I mean.
If I model a normal use case with an activity diagram, the generated result should be a complete page. A use case fragment, on the other hand, represents only a single div. Also, I must specify which fragments are to be included on what use case page. To model this, I imagine two types of use case stereotype: FrontEndUseCase and FrontEndUSeCaseFragment. The FrontEndUseCase instance might then model dependencies to included FrontEndUseCaseFragments. Is this crazy shit? _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3765#3765 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
