Transaction Summary

After completing the actor transaction diagram(s), create a Transaction Summary to synthesize the diagrams into a single list of transactions for which payloads and metadata need to be specified (see Chapter 3).

The framework for summarizing the Transactions needed to support the Use Case is simply a list. The list enumerates the set of Transactions and tells if the initiation of the Transaction is Required or Optional for the Sender and if receiving the Transaction is Required or Optional for the Message Receiver.

For Example: The Event Notification via the Direct Standard® has just 1 transaction:

Transaction Type: send-notification

This transaction is:

• Required for Message Sender

• Required for Message Receiver

Tx #	Transaction Name	Requirements for Sender	Requirements for Receiver