• 1 Overview
• 2 Scope
  • 2.1 What is this release trying to address?
  • 2.2 Use Cases
  • 2.3 Requirements
  • 2.4 Minimum Viable Product
  • 2.5 Functionalities
    • 2.5.1 Epics
    • 2.5.2 Stories
  • 2.6 Longer term roadmap
• 3 Release Deliverables
• 4 Sub-Components
• 5 Architecture
  • 5.1 High level architecture diagram
  • 5.2 Platform Maturity
  • 5.3 API Incoming Dependencies
  • 5.4 API Outgoing Dependencies
  • 5.5 Third Party Products Dependencies
• 6 Testing and Integration Plans
• 7 Gaps
• 8 Known Defects and Issues
• 9 Risks
• 10 Resources
• 11 Release Milestone
• 12 Team Internal Milestone
• 13 Documentation, Training
• 14 Other Information
  • 14.1 Vendor Neutral
  • 14.2 Free and Open Source Software

Overview

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

Indicate where your project fit within the ONAP Archiecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.Image Removed

Image Added

Platform Maturity

Please fill out the centralized wiki page: Honolulu Release Platform Maturity

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

Usecase UI Honolulu- Functional Test Cases

Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

Known Defects and Issues

Provide a link toward the list of all known project bugs.N/A

Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Resources

Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:usecase-ui

Release Milestone

The milestones are defined at the Release Level and Planning: Honolulu and all the supporting project agreed to comply with these dates.

...

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

Please refer to Honolulu Documentation

Other Information

• Vendor Neutral

...

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.