You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »



Development Status

ProjectPTLJIRA Epic / User Story*Requirements
AAI

AAI-1990 - Getting issue details... STATUS AAI-1996 - Getting issue details... STATUS

AAI-BBS Proposals for Dublin Release

CLAMP

CLAMP-270 - Getting issue details... STATUS


DCAE

Vijay Venkatesh Kumar

DCAEGEN2-1057 - Getting issue details... STATUS


External APIMatthieu Geerebaert

EXTAPI-98 - Add notification for serviceInventory API IN PROGRESS

Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications
Modeling

OOF

Policy



SDNC

SO

SO-1392 - Getting issue details... STATUS


UUI

VID

VNFRQTS

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


JIRA Labels

The Epics and Stories generated for the BBS Use Case should use one or more of the following labels:

  • "BBS: Topology Discovery" (Used for issues related to the discovery and synchronization of the Broadband Service elements)
  • "BBS: HSIA Service" (Used for lifecycle issues related to the lifecycle of a HSIA service (creation, activation, deletion)
  • "BBS: Nomadic ONT" (Used for issues related to the registration and re-registration of the ONT; RG Activation)


All labels for BBS stories and epics should be pre-pended with "BBS: "

As more functionality is added to the BBS Use case new labels are expected to be defined.

These labels can be used as filters for looking at the work effort related to BBS.

Testing

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
Showcase VNF/PNFTest EnvironmentIntegration 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 CaseStatus
1There should be a test case for each item in the sequence diagram

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE

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

 FAILED

  • No labels