Page History

• 1 Overview
• 2 

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.

• 1Overview
• 2Scope
  • 2.11 What is this release trying to address?
  • 2.22 Use Cases
  • 2.33 Requirements
  • 2.44 Minimum Viable Product
  • 2.55 Functionalities
    • 2.5.11 Epics
    • 2.5.22 Stories
  • 2.66 Longer term roadmap
• 33 Release Deliverables
• 44 Sub-Components
• 55 Architecture
  • 5.11 High level architecture diagram
  • 5.22 Platform Maturity
  • 5.33 API Incoming Dependencies
  • 5.44 API Outgoing Dependencies
  • 5.55 Third Party Products Dependencies
• 66 Testing and Integration Plans
• 77 Gaps
• 88 Known Defects and Issues
• 99 Risks
• 1010 Resources
• 1111 Release Milestone
• 1212 Team Internal Milestone
• 1313 Documentation, Training
• 1414 Other Information
  • 14.11 Vendor Neutral
  • 14.22 Free and Open Source Software

...

Upgrade Vulnerable Direct Dependencies: 

Use Cases

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

E2E Network Slicing Use Case in R7 Guilin

Requirements

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

...

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

1. UUI BE Component  for supporting KPI Monitoring and Transporting Slicing
2. UUI FE Component  for supporting KPI Monitoring and Transporting Slicing

...

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

API Incoming Dependencies

...

...