...
Plan Use Case Discussions for more complicated scenarios like CM changes and SW Update to work through where components should change.
Development Status
DEVELOPMENT IMPACTS
ProjectJIRA Epic / *RequirementsAAIJames AAI Requirement 1APPC Requirement 1APPC Requirement 2- CLAMP Requirement 1
- CLAMP Requirement 2
- CLAMP Requirement 3
| OOF | | Policy | | - POLICY Requirement 1
- POLICY Requirement 2
| SDC | | SDNC | | SO | | VID | | VNFRQTS | Steven Wright
|
|
| CC-SDK | |
|
|
| DCAE | |
|
|
| DMaaP | |
|
|
| External API | |
|
|
| MODELING | |
|
|
Multi-VIM / Cloud | |
|
|
| OOF | |
|
|
| POLICY | |
|
|
| PORTAL | |
|
|
| SDN-C | |
|
|
| SDC | |
|
|
| SO | |
|
|
| VID | Ittay Stern |
|
|
| VNFRQTS | |
|
|
| VNF-SDK | |
|
|
| CDS | |
|
|
List of PTLs: Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
SUPPORTING DOCUMENTS
PRESENTATIONS
Test Cases and Status
| # | Test Case | Status |
|---|
| 1 | There should be a test case for each item in the sequence diagram | |
| 2 | create additional requirements as needed for each discreet step | |
| 3 | Test cases should cover entire Use Case | | Status |
|---|
| colour | Yellow |
|---|
| title | Partially Complete |
|---|
|
|
| 4 | Test Cases should include enough detail for testing team to implement the test | |
...
