because of the simple reason you don't have decision points in state diagrams, another reason is that in the beginning (when we were still using Poseidon) we also modeled ObjectFlowStates, which you can't have in state diagrams
anyway, I like to think of process logic more in terms of 'activities' rather than 'states', since a front end is action driven, as in interaction, I once made the decision to use activity graphs I remember some other reasons that were mainly practical issues like UML tools not properly supporting features etc.. at the time activity graphs had better support -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2838#2838 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
