Project Name:
- Proposed name for the project: Usecase UI
- Proposed name for the repository: usecase-ui
Description:
This project provides Graphical User Interface (GUI) to implement following use cases:
Scope of vCPE Usecase:
- 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.
- Service & VNF Lifecycle Management
- Instantiate
- Terminate
- Upgrade
- Downgrade
- Service & VNF Lifecycle Management
- Use inventory systesm to determine currently defined inventory for core and edge services.
- Support end-user self-service management UI of provisioned vCPE elements.
Scope of Usecase VoLTE:
- Call service orchestration system to configure services and VNFs in the core and at the edge.
- Service & Lifecycle Management
- instantiate
- terminate
- Service & Lifecycle Management
- Provide manual scaling in/out when there is lower/higher demand.
Architecture Alignment:
- An alignment between the below projects should be agreed on:
- ONAP Portal
- SDC
- SO
- A&AI
- Usecase UI sits between SDC and SO, processing the model from SDC and performing orchestration of network components by calling SO's APIs.
- Usecase UI fetches inventory data from A&AI.
- Usecase UI will provide an HTTP(s) web GUI and interface with other systems using standard protocols like REST over HTTP(s).
Resources:
- Tao Shen (VoLTE) <shentao@chinamobile.com>
- Amichai Hemli <ah0398@intl.att.com>
- Jimmy Forsyth <jf2512@att.com>
- Manoop Talasila <talasila@research.att.com>
Committers/Maintainers:
- Amichai Hemli ah0398@intl.att.com AT&T
- Tao Shen shentao@chinamobile.com CMCC
Other Information:
...
- https://gerrit.onap.org/r/#/admin/projects/vid
- https://gerrit.onap.org/r/#/admin/projects/portal
- https://gerrit.onap.org/r/#/admin/projects/ecompsdkos
...
This checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are Product Backlog Epics entered in Jira? |
| ||||||||||||
| Are Product Backlog Stories entered in Jira? |
| Create a Backlog item | ||||||||||||
| Are Product Backlog Stories linked to Product Backlog Epics? | Product Backlog | Work in a Sprint | ||||||||||||
| Are Product Backlog Stories prioritized? | Prioritize a Backlog item | |||||||||||||
| Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | Estimate a Backlog item | |||||||||||||
| Is the project team ready to create a 2 weeks Sprint in Jira? | Create a Sprint | |||||||||||||
| Are Team Members willing to create Tasks and associate them with Stories in Jira? | Create a Backlog item | |||||||||||||
| Release Management | Is there a Release Planning Template available and completed in wiki? | Release Planning Template | ||||||||||||
| Have all the "Release Components Name" been defined in Resources and Repositories for your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description) | Resources and Repositories | |||||||||||||
| Have all the "Resources committed to the Release" been defined in Resources and Repositories for your project? This includes First and Last names, LFID, Email Address and Location for PTL, Project Manager, Committers and Contributors. | Resources and Repositories | |||||||||||||
| Have new developers made themself familiar on the Onboarding Process? | Onboarding | |||||||||||||
| Is the project team aware of the Release milestone? Any misses will required TSC exception. | ||||||||||||||
| Integration and Testing | Has the Integration Team defined the vendor equipment list? | Link to evidence | ||||||||||||
| Has the Integration Team defined the End 2 End Release Test Case? | Link to evidence | |||||||||||||
| Development | Is the Project Team committed to develop Unit Test? | |||||||||||||
| Has the Project Team put in place an Automated Unit Test infrastructure? | ||||||||||||||
| Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case? | ||||||||||||||
| Is the Project Team committed to perform Scrum ceremonies? | Scrum Overview | |||||||||||||
| Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)? | Continuous Integration | |||||||||||||
| Has the Project Team a clear understanding on the Code Coverage expectations? | ||||||||||||||
| Does the Project Team understand the Free and Open Source Software (FOSS) process? | Free and Open Source Software | |||||||||||||
| Is the Project Team willing to fill out accordingly the FOSS table? | Fill out sub-pages for each project under Free and Open Source Software | |||||||||||||
| Is the Project Team willing to comply to the Commit Process? | Commit Messages | |||||||||||||
| Does the Project Team understand the purpose of Code Review? | Code Review | |||||||||||||
| Is the Project Team aware of the Coding Guidelines? | Development Practices (Jave Coding Style) | |||||||||||||