| Newsgroups |
gmane.comp.java.open-symphony.devel |
| Message-ID |
<[email protected]> |
The OSWorkflow has a basic linear model defined (initial
step->action->result->step->actions->result->next step). It seems to be
missing some objects that could complete the model (final state, concurrent
states). A few years back, I put together an XML-driven state-chart system
and used the UML v1.1 statechart object model for all my objects and their
relationships. That model was very successful, because we were able to
grow into it. We did the simple stuff first, and simply added in
relationships to new objects as we got more sophisticated. For example,
they define pseudostates (initial, final, history), concurrent states,
simple states, transitions, etc.
It seems as if you are considering a v3.0. It might be worthwhile to
consider the UML activity model (or statechart model) for the baseline
workflow objects.
http://www.omg.org/cgi-bin/apps/doc?formal/03-03-01.pdf
"NOTICE - This e-mail message may contain privileged, confidential, or
proprietary information intended only for the use of the intended
recipient. If you are not the intended recipient of this e-mail, you are
hereby notified that any use, dissemination, distribution or reproduction
of this e-mail is prohibited. If you have received this e-mail in error,
please notify Bombardier Aerospace immediately and delete this e-mail and
all attachments from your computer system. Any views expressed in this
e-mail are those of the individual sender and may not necessarily reflect
the views of Bombardier Aerospace."
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5