Project Common Name: ArchNav

Project Overview:

Project description:

• The ONAP Architecture Navigator provides a dashboard for viewing and drilling down into the ONAP's architecture structure.    

Scope:

• In Scope: 

• Out of Scope: 

• Features / functionality being developed: 

  • 1st release content:

  • 2nd release content:

  • 3rd release content:

• New interface/API specifications proposed: 

Architecture Alignment:

• Architectural Fit

  • How does this project fit into the rest of the ONAP Architecture?

  • Architecture diagram of your project: 

  • What upstream ONAP projects does this project depend on? 

  • What downstream ONAP projects are expected to leverage this project?

  • Project & Component Overlay:  

• Interoperability  

  • SDO specifications supported: 

  • APIs/Interfaces:

  • Information/data models:

  • If there is an existing ONAP project that does something similar to this project explain why this being a new stand-alone project?

• Other Dependencies

  • Upstream open source projects: 

  • Non ONAP APIs/Interfaces:

  • Specific IDE integration requirements:

  • Integration Testing: 

  • etc.

Community Alignment:

• Vendor Neutrality: 

• Seed code Location (if any):  

• If "In-House" please answer the the following questions:

  • How long before the seed-code could be made available to the community in a public repository? 

  • Has contribution of the code already been approved by your executive leadership and IPR counsel?

  • Have all proprietary trademarks, logos, product names and internal company secrets been removed from the code base already?

• Would any waivers to ONAP policies (including IPR) be required by this project? 

• Plan for providing education to onboard the ONAP developer community : 

Jira Information:

Release Components: (add/delete rows as necessary)

Resources committed to the project: (add/delete rows as necessary)