Implementer's Guide: Simplification of example 1

In running simulations of example 1 scenario 2 some unforeseen complexities 
emerged. In short, the cancellation of the process could occur in two separate 
ways as written: 
- by the signal in the 'Handle new found issue' sub-process triggering the 
interrupting event sub-process named 'Repairs aborted' ; and 
- by the inter-trigger-time on the Repairs aborted start event (and to 
completely specify this it is necessary to also add trigger count and 
probability parameters).

In the interests of ensuring this first example is not too complex we decided 
on the call of 14 Feb 13 to remove the sub-process meaning just the second 
means of aborting remains. There are several corollaries to this decision, 
which will be described in the section named 'Conclusions and further 
investigations' for the first example: 

- 'Where' (in the process flow) the repair is aborted is no longer defined for 
process instances that do not add additional issues to be repaired (it was 
never defined for other instances) ; and 
- 'When' the repair is aborted is not the subject of this simulation scenario, 
which confines itself to control parameters only, but in the interests of not 
leaving it undefined setting the inter trigger time to 0 indicates it should 
happen straight after the process start.

Original issue reported on code.google.com by tstephen...@gmail.com on 14 Feb 2013 at 5:22

SimonRinguette / bpswg

Implementer's Guide: Simplification of example 1 #134