...

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

Overview

Scope

What is this release trying to address?

Describe the problem being solved by this release

The Usecase-UI Istanbul release has following primary objectives:

1. IBN module:  Usecase UI will support kinds of service of intent management, such as creation, delete, deactivationvia adding a new “Intent-based Services” page
2. IBN module:  Usecase UI will support the monitoring of intent-instance via adding a new monitoring page
3. E2E Slicing: Usecase UI will support the binding of intent-instance and slicing business ID

2. UUI enhancement and new  features:

• Remove GPLv3 from the dockers built by the ONAP community   Image AddedUSECASEUI-494 - usecase UI dockers contain GPLv3 开放
•  Upgrade postgresql   Image AddedUSECASEUI-405 - 2 components in one Docker 处理中
• PACKAGES UPGRADES IN DIRECT DEPENDENCIES  Image AddedUSECASEUI-574 - PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR ISTANBUL 开放
• Add test code for UUI  Image AddedUSECASEUI-584 - Add test code for uui-server DELIVERED

Requirements

Describe the use case this release is targeted for (better if reference to customer requirements).

Smart Intent Guarantee based on IBN - R9 Intent Instance

Minimum Viable Product

...

Usecase-UI will include the necessary subcomponents supporting the primary objectives: supporting the use cases and meeting platform maturity goals.

1. UUI BE Component  for supporting Intent-instance Monitoring and Intent management enhancement, as well as supporting an api for binding the intend-instance and business id
2. UUI FE Component  for supporting Intent-instance Monitoring and Intent management enhancement
3. UUI NLP Component for supporting the smart operator intent translation based on IBN

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics

Stories

Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

...

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

...

Indicate where your project fit within the ONAP Architecture 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 Added

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 Added

Platform Maturity

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

• API Incoming Dependencies

...

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

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

• API Outgoing Dependencies

API this project is delivering to other projects.

...

API Name

...

API Description

...

API Definition Date

...

API Delivery date

...

API Definition link (i.e.swagger)

...

API Outgoing Dependencies

None

Third Party Products Dependencies

None

• Testing and Integration Plans

Usecase UI Honolulu- Functional Test Cases

• Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

...

Name

...

Description

...

Version

...

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

• 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.

• 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

Please refer to Frankfurt Defect Status

...

It is not expected to have a detailed project plan.

• Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

...