Use Case Template

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 XXX)

• 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.

Business Case Template

The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. A compelling business case adequately captures both the quantifiable and unquantifiable characteristics of a proposed project. In the contrast to Use-Case, which carries a flavour of solutions, Business-Case depict a Task or Requirements only. How this Task will be realised, via interaction between a user and a system or without it, with what system or systems, and so on is unknown and may not be assumed in the Business- Case.

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

• Case Reference/Name/ID

• A work name/reference, origins/background/current state.

• Description/Needs

• A general description of the Cloud Client/Consumer/User that highlights a compelling need for Authorisation in order to access resources in Clouds.

• Execution Context

• A description of execution environment that includes both business and technology rules, policies, regulations, priorities and definition of implementation platforms if identified.

• Goals & Objectives

• A description of business needs/goals/objectives that lead to a work.

• Value proposition

• Desired business outcomes, outcomes roadmap, business benefits (by outcome), quantified benefits value, costs/ROI financial scenarios, risks/costs of not proceeding, project risks (to project, benefits and business). The most important elements of Value Proposition should match Goals & Objectives. That is, for some cases, the Value Proposition section may be optional.

• Focus or Categories Covered

• A problem/solution scope, assumptions/constraints, options identified/evaluated, size, scale and complexity assessment.

• Actors

• If known, a description of entities operating in the Business Case.

  • Deliverables

• If different from outcomes, deliverables and benefits planned, organizational areas impacted (internally and externally), key stakeholders, dependencies.

  • Principle Diagram of the Case

• Workload

• Optional. An approach, phase/stage definitions (project (change) activities, technical delivery activities, workload estimate/breakdown, work plan and schedule, critical path).

• Required resources

• Optional. A work leadership team, project governance team, team resources, funding.

• Commitments

• Optional. Work controls, reporting processes, deliverables schedule, financial budget/schedule.