Getting back to the main question on this thread, whether to model or
not, Ken Steel had also written that "[t]he only people who resort to
modelling in my experience are those incapable of implementing. How many
models have you seen that are even close to being sufficiently detailed
and correct to be used in practice? Certainly, to the casual observer,
formal modelling can look like feverish activity. But how useful is the
end result? Most of it ends up in dusty archives or waste paper
baskets."
Modeling kind of reminds me of flowcharts. When I look at the
RosettaNet PIPs, they use a lot of real estate to show a UML diagram
explaining the "Business Process Flow," which could have been
economically rendered in English in a sentence or two.
But I'm unsophisticated in these matters; can someone illustrate the
usefulness of modeling business processes, especially as it relates to
the development of XML/EDI standards? I think Leonard & Catharine were
attempting to do this, but I'm still not convinced. What ever became of
the modeling efforts in X12's SITG before that group was disbanded? If
modeling is useful, does it necessarily mean that flowcharts are the
best way to illustrate models?
William J. Kammerer
FORESIGHT Corp.
4950 Blazer Memorial Pkwy.
Dublin, OH USA 43017-3305
(614) 791-1600
Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"Commerce for a New World"
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
