This is just a template to be used by all Use Cases for tracking progress of the Use Case within a release

All data in this template is just shown as an example and should be replaced with relevant data for that Use Case


For updates on scaling status go to the Scaling Use Case Tracking Page for the Casablanca Release

Use Case Key Information

Prior Project Base Wiki

Requirements Jira

Architecture S/C info


This section describes Business Drivers needs.

Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")

Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").

Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").

Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case).

Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)

Development Status

List of PTLs:Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 

Use Case Diagram

Use cases define how different users interact with a system under design.  Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).

Use Case Diagram Example.png

Use Case Functional Definitions


Use Case Title

Title of the Use Case

Actors (and System Components)

The list of Actors and System Components that participate in the Use Case


Short overview of the Use Case

Points of Contact

Authors and maintainers of the Use Case.

Use Case Lead, Key Use Case members and code contributors.


A list of conditions that are assumed to be true before the Use Case is invoked

Includes description of Information Consumed

Triggers / Begins when

Describes the trigger for beginning the Use Case

Steps / Flows (success)

Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes)

Interaction diagrams may be included or referenced


The expected results of the execution of the Use Case

Includes description of Information Produced

Alternate / Exception Paths

Description of any exceptions or special process that could occur during Use Case

Related Use Cases

List of the Use Cases referenced by this Use Case


Describes any assumptions that are made for this use case

Tools / References / Artifacts

List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability.

List of any associated diagrams or modelling artifacts associated with the Use Case


Current Status

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links

End to End flow to be Tested

**This should be a summary level Sequence diagram done in Gliffy** 

Summary SeqDia Template fff

Test Cases and Status

#Test CaseStatus
1There should be a test case for each item in the sequence diagram


2create additional requirements as needed for each discreet step


3Test cases should cover entire Use Case


 Test Cases should include enough detail for testing team to implement the test



  1. FYI - Scott Blandford and Seshu Kumar Mudiganti - I have raised a risk for Casablanca because I don't see an epic/user story from SO regarding creating Dmaap-based API for doing scale out. See Casablanca Risks.

  2. Pamela Dragosh and Gervais-Martial Ngueko, This is a template wiki page for all Use Cases to utilize for tracking.  Could you please update the Scaling Tracking page with the modifications you made here?

    1. Sorry, I revert back the modification I made on this page, Scaling Tracking page already contained the epic/user story link, so no update needed there.