Yes, I understand that. I am referring to the workflow found in a business tier. This seems to be a really good place for Spring, particularly with its ability to inject cross-cutting advise into the workflow with its AspectJ api. For example, in the current system I am working on a FX transaction message comes onto a queue. There's a listener which acquires all of the new xml-based messages. The xml msg is transformed into a pojo that goes through a validation process (currently handled by Spring) in the validation process a new FX transaction record my be flagged for repair. In this case that record is sent to a repair queue. Once the repair admin class gets notified of a repairable transaction it has to decide what type of repair. Some repairs can be made automatically by the system (ie., calculate a derived rate from two amounts when the rate is missing), or it will need to go to a screen where manual intervention is required. In my model, the auto repair and t he manual repair are two different use cases. One of them needs a UI screen and the other doesn't. How should I model the use case for the auto repair, which doesn't require the UI screen? In addition, during the auto repair, if the source of the transaction is X vs Y then the system needs to auto generate an email notification to X-support. The email notification is an <<extended>> use case of auto repair.
This is a very simple workflow, but it illustrates a scenario where there's a mix of buisness tier logic making decisions about the state and transaction of objects (in this case the FX Transaction object). This workflow should be modeled in the same way the Struts presentation modeling is done - using a Use Case for each major step of the workflow and a related activity diagram to model the transitions, decisions, and guard conditions. The semantics different lies in what you stereotype the Use Case as, maybe <<WorkflowUseCase>>, and the primary class that will handle it, maybe WorkflowActivityHandler (Workflow to indicate its part of a larger picture, Activity as in the fact that the composite of actions in the activity diag constitutes an Activity, and Handler, well that's the best I could think of). Any ideas about where this type of functionality would lie, or if it should be a seperate cartridge? Joe Gaber _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=941#941 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
