Issue 9515: figure 12-4 page 85 (spem-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: The representation of "Example of Activity Diagram" is weird. It mixes data flow and control flow. Between two activities there should be a plain arrow if one comes after the other, and not a dashed arrow going from the 1st activity to an artifact and then another dashed arrow going from the artifact to the second activity. The fact that one activity comes after another is a control flow, the fact that a part from that one artifact is passing from one to the other is different. Because of this confusion, the strangest thing happens: synchronization bars are showed to synchronize activities with artifacts! This has no meaning. Only plain arroaw should leave and arrive to synchronization bars. They would go to or from activities, showing that two activities happen concurrently. The flow of data between the activities (artifacts and dashed arrows are something different) Resolution: Revised Text: Actions taken: March 29, 2006: received issue Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Wed, 29 Mar 2006 13:38:59 -0500 To: Juergen Boldt From: Linda Heaton Subject: Re: Fwd: OMG Document formal/05-01-06 X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id k2TIURqW027747 Software Process Engineering Metamodel (SPEM), v1.1 At 01:36 PM 3/29/2006, you wrote: hmm I guess so what spec is that? -Juergen At 01:34 PM 3/29/2006, you wrote: issue? From: Nicolas Anquetil Organization: Universidade Católica de Brasília To: linda@omg.org Subject: OMG Document formal/05-01-06 Date: Wed, 29 Mar 2006 15:24:11 -0300 User-Agent: KMail/1.8.2 X-OriginalArrivalTime: 29 Mar 2006 18:21:16.0811 (UTC) FILETIME=[91B2B5B0:01C6535D] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id k2TIDACD027505 Hi, just thought I will drop you a note about figure 12-4 page 85 in the PDF file 05-01-06.pdf: The representation of "Example of Activity Diagram" is weird. It mixes data flow and control flow. Between two activities there should be a plain arrow if one comes after the other, and not a dashed arrow going from the 1st activity to an artifact and then another dashed arrow going from the artifact to the second activity. The fact that one activity comes after another is a control flow, the fact that a part from that one artifact is passing from one to the other is different. Because of this confusion, the strangest thing happens: synchronization bars are showed to synchronize activities with artifacts! This has no meaning. Only plain arroaw should leave and arrive to synchronization bars. They would go to or from activities, showing that two activities happen concurrently. The flow of data between the activities (artifacts and dashed arrows are something different) nicolas -- Dr. Nicolas Anquetil UCB - Universidade Católica de Brasília http://www.ucb.br/ucbtic/mgcti/paginapessoalprof/Nicolas/index.html Linda Heaton Sr. Technical Editor Object Management Group 140 Kendrick Street Building A, Suite 300 Needham, MA 02494 linda@omg.org Juergen Boldt Director, Member Services 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org Linda Heaton Sr. Technical Editor Object Management Group 140 Kendrick Street Building A, Suite 300 Needham, MA 02494 linda@omg.org