This example illustrates a formal verification of using a Message Sequence Chart (MSC) as a property to verify the behaviour implemented in a BPEL process.

This example expands on Test 2 by adding a concurrent execution structure to the bpel process.
Now the behaviour specifies that either GetVehicleRecords or GetVehicleInsuranceRecords may occur first.

To perform the verification:

1  In LTSA WS-Engineer switch to the Design tab 
2. Drag-and-drop both the pito.bpel and pito-msc.xml on to the tab page.
3. Switch the property to use as "Specification".
4. Click Verify and note that a violation occurs at the getvehiclerecords invocation action.

The violation occurs because the behaviour specified in the MSC states that either getvehiclerecords or getvehicleinsurancerecords invocation actions can occur as a first step.

How to resolve the violation:

- Iteration 3 presents a solution to this violation. 
