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.

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 the getvehiclerecords invocation action must occur as a first step.

How to resolve the violation:

- by changing the sequence of the behaviour specified in the bpel file
  - move the GetVehicleRecords invoke activity in the bpel process before the GetPersonRecords invoke activity.
  - repeat the verification step 4. and notice that there are now no violations.

 
