To promote consistency in the contributed content, please read these style and composition notes for use cases. Thank you.

...

The use cases documented here should be for product implementations where a data receipt of some kind is neededutilized. 

The Kantara Receipt Specification describes a data structure and output format.

The implementation use cases describe, from the perspective of the Actors, how the Actors succeed or fail to accomplish their objectives with respect to the "System".

Use Case Writing Guidance

A use case is a description of the possible sequences of interactions between the system under discussion and its external actors, related to a particular goal.

• The 'system' in our case is the assured process operated by the organization.
• (To be discussed in DG): The main stakeholder should be either the 'owner'/operator of the assured process; or, the 'customer' of that assured process.
• The main goal should be to establish an identity, bind it to the entity, and to result in one or more assured identifiers (bullets a, b, c above).
• The use case is intended to describe the functional behaviour of the system.

The remainder of the content on this page is a longer description about use case writing and suggestions for content and process.

Page Contents

...

...