Hi all,
I would like to reopen the discussion...
My problem is that now I want to call from a Action State within use case A to another use case B, and then come back to A use case, and within the same Action State. The problem is as always... in the middle of a use case (for example making a purchase order) I want to search for a Customer and then continue with the customer code withtin the purchase order use case.
My idea is as follows:
-for those use cases that are called within another use cases, they will be stereotyped as something like "ComponentUseCase". They must have one initital state and one final state. (on this way you ensure that if parameter is returned, you will always know their numbers and types)
-the calls to this use cases can be done within an activity diagram with the SubAction State, which allows to link to another use case, or maybe with a tagged value and a standard Action State. (this way the same "ComponentUseCase" can be called several times within the same action state)
-Links will be done as follows: when a "ComponentUseCase" case is modelled the action State A recevies a form with the output paramters of the "ComponentUseCase".
The State A send a varible to specify where it has to return back. The "ComponentUseCase" is executed and the forwards taking into account the variable that was received from use case A (on this way the same compent can be use from diferent use cases).
any ideas or comments??
Carlos
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
