...
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 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
...
Description
...
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.
...
Preconditions
...
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
...
Post-conditions
...
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
...
Assumptions
...
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
Epic Status
Jira server ONAP JIRA columns key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 approval,m2 approval,m3 approval,m4 approval,rc0 approval,status maximumIssues 20 jqlQuery key = REQ-716 serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Jira server ONAP JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions maximumIssues 100 jqlQuery "Epic Link" = REQ-716 and project != "REQ" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
JIRA Relelationships and Sequencing
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
...
End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
...
Test Cases and Status
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
...