[Work in progress]
Project Commitments
| Project | PTL | Commitment | Notes |
|---|---|---|---|
| AAI | OPEN | ||
| APPC | NA | No requirements | |
| CLAMP | |||
| DCAE | |||
| External API | OPEN | - Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications - TMF 641 action "modify" to modify existing service instance and not recreate it | |
| Modeling | |||
| OOF | |||
| Policy | |||
| SDC | NA | No requirements | |
| SDNC | |||
| SO | |||
| UUI | |||
| VFC | NA | No requirements | |
| VID | |||
| VNFRQTS |
Development Status
| Project | PTL | JIRA Epic / User Story* | Requirements |
|---|---|---|---|
| AAI | |||
| CLAMP | |||
| DCAE | |||
| External API | Matthieu Geerebaert | ||
| Modeling | |||
| OOF | |||
| Policy | |||
| SDNC | |||
| SO | |||
| UUI | |||
| VID | |||
| VNFRQTS |
*Each Requirement should be tracked by its own User Story in JIRA
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
| Showcase VNF/PNF | Test Environment | Integration Team Liaison |
|---|---|---|
End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
Test Cases and Status
| # | Test Case | 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 |
| 4 | Test Cases should include enough detail for testing team to implement the test | FAILED |