Pat,
Is there a particular reason why you are looking at Petri-Nets, rather than
StateCharts?
We looked at Petri-Nets before, and ended up settling on StateCharts for
modeling reasons. Petri-Nets are non-deterministic and so are hard to test
(and debug), whereas StateCharts are deterministic and can be tested.
Granted, we gave up some conceptual power, but we ended up with a system we
could understand and describe to end users.
James
"Pat Lightbody"
<[email protected] To: <[email protected]>
om> cc:
Subject: Re: [Opensymphony-developers] UML v1.5 statechart object model
06/11/2003 06:57
PM
James,
Thanks for the suggestions, we always appreciate new users and new
feedback.
If there are going to be any overall changes, however, we'll probably end
up
implementing a petrinet rather than statecharts or FSMs.
-Pat
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Wednesday, June 11, 2003 3:19 PM
Subject: [Opensymphony-developers] UML v1.5 statechart object model
>
>
> 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
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers
-------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.