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

Info

Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.

Overview

Scope

What is this release trying to address?

Describe the problem being solved by this release

The Usecase-UI New Delhi release has following primary objectives:

1. It provides generative AI interaction functions based on large models
2. Provides a large model adaptation layer that can be configured to integrate with different large model services
3. Deliver large model evaluation functionality to evaluate different models
4. Provide end-to-end use cases for the use and testing of large models

Requirements

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

N/A

Minimum Viable Product

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

• It provides generative AI interaction functions based on large models
• Provides a large model adaptation layer that can be configured to integrate with different large model services
• Deliver large model evaluation functionality to evaluate different models
• Provide end-to-end use cases for the use and testing of large models

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

N/A

Stories

N/A

Bugs

N/A

Longer term roadmap

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

Release Deliverables

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.

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

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.

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.

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.

N/A

Platform Maturity

Please fill out the centralized wiki page:N/A

• API Incoming Dependencies

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.