Child pages
  • Scenario and Use Case Template - 2
Skip to end of metadata
Go to start of metadata

Abstract

This document is a product of the XXX Work Group. It records the scenarios and use cases governing the development of XXX and guiding associated implementations and deployments.

Status


This document is currently under active development. Its latest version can always be found here. See the GI:Change History at the end of this document for its revision number.

Editors

John Doe
Jane Doe

Intellectual Property Notice

The XXX Work Group operates under Option ABC and the publication of this document is governed by the policies outlined in this option.


Table of Contents


Introduction and Instructions

This document is a product of the XXX Work Group. It records the scenarios and use cases governing the development of XXX and guiding associated implementations and deployments.

Please use the GI:scenario template near the end of this document in adding new scenarios and subordinate use cases. Change the status keyword in each scenario and use case title as appropriate, linking to the meeting minutes page explaining the status change:

  • Pending: Initial status when first submitted
  • Accepted: Needs to be accounted for in UMA V1 and/or its associated compliant implementations
  • Deferred: Relevant to the problem space; may be considered in future versions
  • Rejected: Out of scope

Edit the descriptions of technical issues and scope questions to reflect (or point to) group decisions about how to handle them.


Scenario: unique-title (Pending)

Submitted by: participant-name

(Provide description of the scenario with all nontechnical particulars, noting requirements, constraints, and other observations. Avoid diagrams if they're technical. Sample user experience drawings could be useful.)

Use Case: unique-title (Pending)

Submitted by: participant-name

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

Issue: unique-title

(Provide technical commentary on the issues brought up by this use case.)


Change History

Version Date Comment
Current Version (v. 3) Jun 02, 2010 11:22 Kantara Initiative Staff:
Migration of unmigrated content due to installation of a new plugin
v. 2 Jun 02, 2010 11:22 Kantara Initiative Staff:
Migrated to Confluence 4.0
v. 1 Jun 02, 2010 11:22 Kantara Initiative Staff
  • No labels