You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »




Overview

Project Name

Enter the name of the project

Target Release NameEnter the name of the release you are targeting to deliver
Project Lifecycle StateEither Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended.

Scope

What is this release trying to address?

Describe the problem being solved by this release

Requirements

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

Minimum Viable Product

Describe 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



KeySummaryTCreatedUpdatedDueAssigneeReporterPStatusResolution
SANDBOX-241EP: Patients accessing ZOOMEpicMar 15, 2020Mar 16, 2020
UnassignedHind KhalifaMediumOPENUnresolved
SANDBOX-186filtering men shoesEpicMar 11, 2020Mar 18, 2020
Munira AhmedMunira AhmedMediumOPENUnresolved
SANDBOX-178EP: Treatment of CoronavirusEpicMar 11, 2020Mar 11, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-177EP: Coronavirus PreventionEpicMar 11, 2020Mar 16, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-130TeamSnap AccountEpicMar 10, 2020Mar 10, 2020
UnassignedSARRA FALFOULMediumOPENUnresolved
SANDBOX-127Cards paymentsEpicMar 10, 2020Mar 10, 2020
Unassignedtayseer AbdelMediumOPENUnresolved
SANDBOX-126EP: FB profile imagesEpicMar 10, 2020Mar 15, 2020
UnassignedMuhaned MohamedHighOPENUnresolved
SANDBOX-125EP: FEDEXEpicMar 10, 2020Mar 10, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-124CoronavirusEpicMar 09, 2020Mar 10, 2020
UnassignedSohrab KazmiHighestOPENUnresolved
SANDBOX-123EP: Carpet CleanningEpicMar 09, 2020Mar 10, 2020
Wael GorashiWael GorashiMediumOPENUnresolved
SANDBOX-122Uploading a post to my IG profileEpicMar 09, 2020Mar 10, 2020
UnassignedSHAALINI CHANDRASEKARANMediumOPENUnresolved
SANDBOX-121Remote_Chaka PissaEpicMar 09, 2020Mar 10, 2020
UnassignedDafalla HamadMediumOPENUnresolved
SANDBOX-120INSTA-SizingEpicMar 09, 2020Mar 10, 2020
UnassignedMunira AhmedMediumOPENUnresolved
SANDBOX-119(filtering women's shoes)EpicMar 09, 2020Mar 11, 2020
Unassignedhelen zahiMediumOPENUnresolved
SANDBOX-118zoloEpicMar 09, 2020Mar 11, 2020
UnassignedSabri MusaMediumOPENUnresolved
SANDBOX-116Test Epic ZZEpicMar 09, 2020Mar 11, 2020
UnassignedZoheb ZaidiMediumOPENUnresolved
SANDBOX-114Test Epic 3/9EpicMar 09, 2020Mar 09, 2020
UnassignedZoheb ZaidiHighOPENUnresolved


17 issues  Refresh




Stories



KeySummaryTCreatedUpdatedDueAssigneeReporterPStatusResolution
SANDBOX-243zoom team:Creating an account on ZOOM appStoryMar 16, 2020Mar 16, 2020
UnassignedHind KhalifaMediumOPENUnresolved
SANDBOX-242zoom team :download zoom app for patientsStoryMar 16, 2020Mar 16, 2020
Hind KhalifaHind KhalifaMediumOPENUnresolved
SANDBOX-240Mens Shoes- fashionStoryMar 11, 2020Mar 11, 2020
UnassignedSARRA FALFOULMediumOPENUnresolved
SANDBOX-210Diva1 - shoe model- flat shoeStoryMar 11, 2020Mar 17, 2020
Unassignedtayseer AbdelMediumOPENUnresolved
SANDBOX-206Diva1 - shoe model- walkingStoryMar 11, 2020Mar 17, 2020
Unassignedhelen zahiMediumOPENUnresolved
SANDBOX-205Diva1- Men shoes- dress up shoesStoryMar 11, 2020Mar 17, 2020
UnassignedMunira AhmedMediumOPENUnresolved
SANDBOX-204Diva1 - Men's Shoes: TrainersStoryMar 11, 2020Mar 16, 2020
Dafalla HamadDafalla HamadMediumDELIVEREDUnresolved
SANDBOX-200Diva1 - shoe model- bootsStoryMar 11, 2020Mar 17, 2020
UnassignedZoheb ZaidiMediumOPENUnresolved
SANDBOX-196Diva1 - shoe model- high heel shoesStoryMar 11, 2020Mar 17, 2020
UnassignedZoheb ZaidiMediumOPENUnresolved
SANDBOX-195US: 2 Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
Summer GamalSummer GamalMediumCLOSEDDone
SANDBOX-194Diva1 - Men's Shoes-Types of shoesStoryMar 11, 2020Mar 17, 2020
UnassignedDafalla HamadMediumOPENUnresolved
SANDBOX-193US: 2 Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-192US: 2 Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-191US: Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-190US: Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-189US: 2 Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-188Diva1 - shoe model- tennis shoesStoryMar 11, 2020Mar 17, 2020
Unassignedtayseer AbdelMediumOPENUnresolved
SANDBOX-187US: 2 Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumOPENUnresolved
SANDBOX-185US: 2 Coronavirus Prevention Team- Treating the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumIN PROGRESSUnresolved
SANDBOX-183US: Coronavirus Prevention Team- How to Prevent the virusStoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMediumOPENUnresolved


Showing 20 out of 44 issues  Refresh





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.

Deliverable Name

Deliverable Description

To fill outTo fill out

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.

Platform Maturity

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


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

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

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

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

  • 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

To fill outTo fill outTo fill out

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.

Gaps identified

Impact

To fill outTo fill out

  • Known Defects and Issues

Please refer to Frankfurt Defect Status


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

Please update any risk on the centralized wiki page - Frankfurt Risks

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

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

  • Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

Date

Project

Deliverable

To fill outTo fill outTo fill out

  • Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

That includes

  • Team contributions to the specific document related to he project (Config guide, installation guide...).
  • Team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

Note

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


Other Information

  • Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

  • Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

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


Charter Compliance

The project team comply with the ONAP Charter.

  • No labels