Examples of the message content that will be associated with each interaction should be defined and linked to the relevant scenario interactions.

Where existing schema is being used, then the messages should be associated with those schemas and verified to ensure the content is valid.

Sample messages in the purchasing example include:

• BuyRequest.xml

• CreditCheckRequest.xml

• CreditCheckResponse.xml

• BuyResponse.xml

Sample messages might start off simple:

<buy:BuyRequest id="1" xmlns:buy=”http://www.example.org/buy” />

And then evolve as the design matures:

<?xml version="1.0" encoding="UTF-8"?>
<buy:buyRequest id="1" xmlns:buy="http://www.example.org/buy"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http:///www.example.org buy.xsd ">
     <buy:customerName>Bill Smith</buy:customerName>
     ...
</buy:buyRequest>

NOTE: The example message content should define a namespace, even if the associated schema does not yet exist. Otherwise, to define a namespace at a later stage will result in a lot of changes being required to the example message contents and message type fields on the interaction links in the scenarios.

Details

When example messages don't currently exist, then they will need to be created and associated with the scenario interactions.

Repo: Store example messages. Enable existing message schema to be located. Define dependencies between example messages and the scenarios in which they are used. Also define dependency between the example messages and their schema.

Input: Scenarios that are missing example messages for their interactions.

Output: Updated scenarios and creation of new example messages (optionally with schema associated where available).