Issue 5542: To promote "flow" is overly simplistic (uml-eai-ftf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: To promote "flow" is overly simplistic, as an activity is a transformation (even in its earliest IDEF0 definition). A transformation occurs when all signals and conditions are present, generating state(s) that conform to defined constraints. I prefer "state transition" vs.. flow. Resolution: Revised Text: Actions taken: July 18, 2002: received issue Discussion: End of Annotations:===== X-Sender: linda@emerald.omg.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 23 Jul 2002 13:10:13 -0400 To: Juergen Boldt From: "Scott Nieman" (by way of Linda Heaton ) Subject: FW: ptc/02-02-02 UML Profile and Interchange Models for Enterprise Application Integration (EAI) Specification Here it is............. Correction, OMI was released by webMethods just recently. Scott -----Original Message----- From: Scott Nieman [mailto:scott@ebmachines.com] Sent: Thursday, July 18, 2002 2:17 PM To: issues@omg.org Subject: ptc/02-02-02 UML Profile and Interchange Models for Enterprise Application Integration (EAI) Specification UML Profile and Interchange Models for Enterprise Application Integration (EAI) Specification I understand that the submission deadline was July 1, 2002, but I want to know if you are interested in my comments regarding this specification. I have a number of them including: 5) To promote "flow" is overly simplistic, as an activity is a transformation (even in its earliest IDEF0 definition). A transformation occurs when all signals and conditions are present, generating state(s) that conform to defined constraints. I prefer "state transition" vs.. flow