...
- Proposed name for the project:
projectnameUsecase UI - Proposed name for the repository:
reponame
Project description:
- Provide high level description of intended project and intended use case(s) and benefit, if needed.
Scope:
- usecase-ui
Project description:
- Usecase UI?ONAP????????????????????????????????Usecase UI???????????????????????????????????????
- ?????????????????????ONAP??????????????ONAP????????????ONAP??????????????????ONAP?????????????????????
Scope:
- The Designer Role:
- Service design (SDC????)
- VNF onboarding (SDC????)
- Policy design (Policy Framework????)
- The Operator Role:
- Service LCM (VID?????)
- Inventory for services and resources (AAI????)
- Monitor (??DCAE?API?????????)
- Alarm correlation (Holmes????)
- Performance (??DCAE?API?????????)
- The user Role:
- Provide model-based vCPE instance orchestration interface.
- Consume and interpret standard ONAP vCPE models.
- Call service orchestration systems to configure services and VNFs in the core and at the edge.
- Use inventory systesm to determine currently defined inventory for core and edge services.
- End-user self-service management UI of provisioned vCPE elements
- Describe the functionality to be provided by the project. Please provide the full intended scope of the project; not just what is intended for the project's first release.
- Specify any interface/API specification proposed,
- Identity a list of features and functionality will be developed.
- Identify what is in or out of scope. During the development phase, it helps reduce discussion
- .
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
- How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
- Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing
- etc.
...