Technical Use Case Framework

How is a technical use case different from a Business Scenario? A Business scenario is talking about the organizations and people who are doing certain work which ultimately will benefit from the technological innovations being described in this Framework. The technical use case tells the story of what the Technical Actors need to do which are performing according to orchestration defined in this Framework.

Each technical use case should be as simple as possible to start, and then build upon it over time, if needed. In general, less complex transactions are simpler to understand and easier to use. Too much complexity makes an IG less likely to be adopted.

The set of technical use cases needs to cover what’s in scope for the Business Scenario. Establishing the set of technical use cases is the first step toward determining the number of Direct transactions that need to be specified. Each technical use case will require one or more Direct transactions. The goal is to develop a comprehensive list of the full set of needed transactions carrying the various payloads. For each message payload pair, metadata will be established to adequately route and pre-process the message.

This is a process that enables the full range of needed transactions and payloads to be specified.

1. Describe the set of technical use cases in detail. (Section Header Detailed Technical Use Case)

   1. Some technical use cases may be identified for context but be marked out of scope.

   2. Summarize the set of technical use cases in a succinct list. (Section Header Summary of Technical Use Case)

2. For each in scope technical use case, you create an actor transaction diagram. (Section Header Actor Transaction Diagrams)

   1. For each Transaction, you indicate the payload to be carried.

3. Summarize the set of transactions into a succinct list. (Section Header Transaction Summary)

Detailed Technical Use Case

Use Case ID	Technical Use Case Name and Description

Summary of Technical Use Case

Note: Shading of rows is used to indicate priority and scope. Rows highlighted in yellow represent high-priority technical use cases, while rows shaded in gray identify use cases that may be out of scope.

Use Case ID	Technical Use Case Name