The content of this template is expected to be fill out for M1 Release Planning Milestone.

Overview

Scope

What is this release trying to address?

Scope: The scope of this release will be for the Portal Platform to support the below list: (provided the lead developers names who will be providing status on these committed features in weekly scrums)

Not-in-Scope: Please check Gaps.

Use Cases

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

Portal support top menu for "5G PNF Plug and Play" use case.

Minimum Viable Product

Supporting 5G use case, Internationalization language support, and technology stack upgrade is the MVP for this release.

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.

Requirements for Dublin release - road map

Release Deliverables

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

Sub-Components

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

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

ONAP Dependencies

List the other ONAP projects your depends on. 

Components involved in 5G usecases that requires functional menus on the Portal platform. So, far SDC, VID, AAI are identified.

UsecaseUI for internationalization feature contribution.

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

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.

Open

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

Portal's maturity requirements status is maintained for Dublin release here - Portal R4 Dublin - Integration Test Plans

API Incoming Dependencies

List the API this release is expecting from other releases.
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.