...
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
...
...
...
...
...
...
...
Mandar Sawant (Old) → Fiachra Corcoran (New)
...
...
...
...
Multi-VIM /
Cloud
...
...
...
...
...
...
...
...
...
...
...
...
Weitao Gao (Old) →
user-67d6f (New)
...
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
Rel I Project REQ Tickets
Jira server ONAP Jira columnIds issuekey,summary,assignee,reporter,status columns key,summary,assignee,reporter,status maximumIssues 1000 jqlQuery key = REQ-716 or ("Epic Link" = REQ-716 and project = REQ) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Story Tickets
Epic Status
arch reviewJira server ONAP JIRA columns key,summary,type,created,updated,assignee,
tsc reporter,
scope priority,
t-shirt size,m1 approval,m2 approval,m3 approval,m4 approval,rc0 approval,statusstatus,
20resolution,subtasks,fixversions maximumIssues
key 100 jqlQuery
446 "Epic Link" = REQ- 716 and project != "REQ" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Rel J Project REQ
...
Tickets
Jira server ONAP JIRAJira columnIds issuekey,summary,assignee,reporter,customfield_10701,customfield_10702,customfield_10703,status columns key,summary,assignee,reporter,integration test plan status,integration test status,integration test time to completeIntegration Test Plan Status,Integration Test Status,Integration Test Time to Complete,status maximumIssues 1000 jqlQuery key = REQ-994 or ("Epic Link" = REQ-716 994 and project = REQ ) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Backlog Tickets for Rel J
Jira server ONAP JIRAJira columnIds issuekey,summary,issuetype,created,updated,assignee,reporter,priority,status,resolution,subtasks columns key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions maximumIssues 100 jqlQuery "Epic Link" = REQ-446 and project != "REQ" POLICY-3777 or "Epic Link" = POLICY-2952 serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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
...
NOT YET TESTED
...
COMPLETE
Function Description
TOSCA Defined Control Loops: Architecture and Design
How to run the Front-End GUI
Investigation of Clamp Common Parameter Handling and Validation.
Investigation of CLAMP for Tosca Control Loop Integration - In Progress
JIRA Relelationships and Sequencing
Persistence Policy Models using JPA/JDBC/Eclipselink/MariaDB
Rough wireframe for TOSCA CL Monitoring GUI
The CLAMP Kubernetes Participant
TOSCA based Control Loops with the existing CLAMP code in the Policy Framework
TOSCA Control Loops: Scratchpad Page
TESTING
Roadmap
Reference
...