Use Case Template (Normative)

DRAFT CONDITION (last updated 2010/10/11, Matt Rutkowski)

Developed for all use case submissions to be normative for comparison/comment and inclusion in the Use Case document:

• Description/User Story

• A general description of the use case in consumer language that highlights a compelling need for one or more aspects of Identity Management.

• Goal or Desired Outcome

• A general description of the intended outcome of the use case including any artifacts created.

• Categories Covered

• A listing of the Identity Management categories covered by the use case (as identified in section 2.2 [http://docs.oasis-open.org/id-cloud/IDCloud-usecases/v1.0/cn01/IDCloud-usecases-v1.0-cn01.html#_Toc324801996])

• Applicable Deployment and Service Models

• A listing of the cloud deployment and service models covered by the use case (as identified in section XXX)
• These categories include:
  • Cloud Deployment Models
    • Private
    • Public
    • Community
    • Hybrid
  • Service Models
    • Software-as-a-Service (SaaS)
    • Platform-as-a-Service (PaaS)
    • Infrastructure-as-a-Service (IaaS)
    • Other (i.e. other “as-a-Service” Models)

• Actors

• A listing of the actors or roles that take part in the use case.

• Systems

• TBD

• Notable Services

• A listing of services (security or otherwise) that contribute to the identity management aspects of the use case.

  • Dependencies

• A listing of any dependencies the use case has as a precondition.

• Assumptions

• A listing of any assumptions made about the use case including its actors, services, environment, etc.

• Process Flow

• A detailed stepwise flow of actions that comprise the use case.