The version number is printed at the bottom the page with the ISBN, just before the Table of Contents, as seen below:
The image above indicates version 2.1. The original version, which became available on Amazon.com October 31, 2011, is 2.0. A minor revision, version 2.1, became available on Amazon November 15, 2011.
Changes in Version 2.1
The following table lists the changes from v2.0 to v2.1:
| Page | Para | v2.0 | v2.1 | |
| 28 | 4 | and | an | |
| 38 | 4 | activities | subprocesses | |
| 38 | 4 | activity | subprocess | |
| 41 | 2 | out signifies | out, signifies | |
| 41 | 3 | case). | case. | |
| 62 | 4 | end state identified | end state | |
| 62 | activity | activity identified in Step 2 | ||
| 67 | 4 | diagram, one end event per end state. | diagram, with one top-level end event per process end state. | |
| 67 | 5 | Expand top-level subprocesses in | Expand each top-level subprocess in a | |
| 75 | 2 | implies the message flow source and target participants are the same participant… which is not allowed by the specification. | suggests the message flow source and target participants are the same participant… which is not allowed and makes no sense. | |
| 80 | 1 | Level 1 palette | Level 1 or Level 2 palette | |
| 2 | Use a single start event and remove the ambiguity. | In a subprocess, always use a single start event, removing the ambiguity. | ||
| 82 | 2 | and | along with | |
| 91 | 1 | in addition, a | in addition, upon occurrence of the trigger, a | |
| 105 | 5 | end event to boundary event | end event to a boundary event | |
| 108 | 5 | process to announce | process or system to announce | |
| 111 | 3 | unlinke a regular subprocess, it has | it has | |
| 3 | active inside a running process level, | active while the process level is running, | ||
| 125 | 2 | two factors: whether | two factors: 1) whether | |
| 2 | and the | and 2) the | ||
| 3 | or normal and exception flow exits from | or | ||
| 129 | 1 | support transactions | support for transactions | |
| 136 | 4 | detail elements and attributes not included in the Analytic conformance class. | details omitted in most models and not represented in the notation. | |
| 150 | 5 | it is possible that a “Ref” element or attribute may | some “Ref” elements or attributes will | |
| 151 | 1 | value by QName | value referenced by QName | |
| 158 | 2 | XPath), is implied | XPath) is implied | |
| 4 | recommended the export | recommended if the export | ||
| 162 | 7 | processType signifies | processType, signifies | |
| 169 | 5 | specify | specific | |
| 182 | 1 | has id and name | has id and name and belongs to a process | |
| 4 | complicates the serialization | makes the serialization more verbose | ||
| 220 | 5 | indicating a physical item | indicating data or a physical item | |
| 5 | an element | an element or complex type |
Errata in Version 2.1
These may be corrected in a future revision. Please contact bruce@methodandstyle.com with any errors you find.
- P.vi, para 2. Should say “The approach rests…”
- P.xi, para 4. Should say “Some of the shapes…”
- p4, para 7. Should say “The diagram should not violate the rules…”
- p5, para 7. Should say “and the like, not in the diagram…”
- p7, para 5. Should say “In the world…”
- p9, para 2. Should say “overall structure of the model…”
- p9, para 4. Should say “may be able to comprehend…”
- p11, para 2. Should say “functions rather than actions…”
- p67, para 5, item 4. Should say “in a child-level diagram…”
- P206 – R1200… These include task, userTask, serviceTask, sendTask, receiveTask, callActivity, subProcess[@triggeredByEvent=false()],…
- P206 – R1300… @triggeredByEvent=false(). Actually this rule is redundant to R1200 – delete it.
- P206 – R1303… @isForCompensation=true()
- P207 – R1500… @parallelMultiple=true()
- P207 – R1600… @parallelMultiple=true()
- P207 – R1624… @cancelActivity=false()