Sample Document - Testing - may be deleted

You can find a template for scenarios and subordinate use cases at the end of this document. Change the status of each scenario and use case appropriately, indicating the meeting date when the decision was made:

• accepted: accepted to be solved in UMA V1 and its associated compliant applications and implementations
• deferred: likely in the correct problem space but deferred for later consideration in future versions
• rejected: not considered to be in the UMA problem space

Scenario: Sharing a Single Resource with a Vendor

Submitted by: Eve Maler
Status: pending

(Provide description of the scenario with all nontechnical particulars, noting requirements, constraints, and other observations. Avoid diagrams.)

Use Case: Separate Resource Host, Relationship Manager, and Recipient

Submitted by: Eve Maler
Status: pending

(Provide description of a use case matching this scenario with all technical particulars, such as the topological configuration of protocol endpoint entities, potential wireframes, listings and assessments of technical issues, and anything else helpful.)

Scenario: (unique-title)

Submitted by: (participant-name)
Status: pending (change to accepted/deferred/rejected and note the date the decision was made)

(Provide description of the scenario with all nontechnical particulars, noting requirements, constraints, and other observations. Avoid diagrams.)

Use Case: (unique-title)

Submitted by: (participant-name)
Status: pending (change to accepted/deferred/rejected and note the date the decision was made)

(Provide description of a use case matching this scenario with all technical particulars, such as the topological configuration of protocol endpoint entities, potential wireframes, listings and assessments of technical issues, and anything else helpful.)