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

Compare with Current View Page History

« Previous Version 6 Next »

Project Name:

  • Proposed name for the project: Usecase UI
  • Proposed name for the repository: usecase-ui

Project description:

  • Usecase UI is the ONAP subsystem that provides perfect Graphical User Interface (GUI) for operators and end-users from the point of view of use cases. As a whole project, Usecase UI not only provides service design and run-time management for operators, but also provides self-service management for end-users.
  • This project targets combing all GUI requirements which operators and end-users need ONAP to support for users, coordinating GUI parts of each ONAP subsystem?improving GUI functionalities for use case. All GUI functionalities of ONAP system can be well showed to satisfy the requirements from different customers.

Scope:

  • The Designer Role:
    • Service design (implement by SDC)
    • VNF onboarding (implement by SDC)
    • Policy design (implement by Policy Framework)
  • The Operator Role:
    • Service LCM (implement by VID)
    • Inventory for services and resources (implement by A&AI)
    • Monitor
    • Alarm correlation (implement by Holmes)
    • Performance
  • 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.

Architecture Alignment:


  • How does this project fit into the rest of the ONAP Architecture?
    • Usecase Ui is one of the key functional GUI blocks in the ONAP Architecture
  • What other ONAP projects does this project depend on?
    • Portal Platform
    • DCAE
    • A&AI
    • VID
    • SO
    • SDC
    • Policy Framework
  • How does this align with external standards/specifications?
    • Usecase UI will use provide an HTTP(s) web GUI and will interface with other systems using standard protocols like REST over HTTP(s).
  • Are there dependencies with other open source projects?
    • N/A

Resources:

  • Primary Contact Person: Tao Shen (China Mobile), Amichai Hemli (AT&T)
  • Names, gerrit IDs, and company affiliations of the committers

    NameGerrit IDCompanyEmailTime Zone
    Tao Shen
    CMCCshentao@chinamobile.comBeijing, China. UTC +8
    Amichai Hemli
    AT&Tah0398@intl.att.com
  • Names and affiliations of any other contributors

    NameGerrit IDCompanyEmailTime Zone
    Jimmy Forsyth
    AT&Tjf2512@att.com
    Yoav Kluger
    Amdocsyoav.kluger@amdocs.com
    Manoop Talasila
    AT&Ttalasila@research.att.com
  • Project Roles (include RACI chart, if applicable)

Other Information:

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name: usecase-ui
  • JIRA project prefix: usecase-ui

Repo name: usecase-ui
Lifecycle State:
Primary Contact: Tao Shen (China Mobile), Amichai Hemli (AT&T)
Project Lead: Tao Shen (China Mobile), Amichai Hemli (AT&T)
mailing list tag [Should match Jira Project Prefix] 
Committers: please refer to the above table

*Link to TSC approval: 
Link to approval of additional submitters: 


  • No labels