Versions Compared

Old Version 5

changes.mady.by.user Alla Goldner

Saved on

compared with

New Version 6

changes.mady.by.user Alla Goldner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Requirements Subcommittee Members

The Requirements subcommittee is responsible for bringing functional and non-functional requirements required for ONAP releases. This excludes at this stage security and close-loop requirements, which are handled by the corresponding subcommittees. It will be used as an input for developing functional architecture and detailed software architecture per release. The Requirements subcommittee will not make decisions regarding Release’s functional architecture or internal functioning of projects or different modules. It is a support group for the TSC Chair and the TSC. The Requirements subcommittee is advisory by nature, and not authoritative. It may provide advice to projects and to the TSC and TSC’s Architecture subcommittee. The Requirements subcommittee operates on a rough consensus basis.  If the subcommittee is unable to reach consensus on what requirement to offer, the subcommittee will refer the matter to the TSC.


Mailing list Moderators

Alla Goldner

ramki krishnan 

Membership List

Participation

The Requirements subcommittee is open to all interested participants, and all meetings are open. Requirements subcommittee is contribution-driven.

  • People can sign up for slots on the agenda

  • We will request people to develop proposals/presentations to discuss during meetings and via email

Deliverables

The Requirements subcommittee will develop and maintain functional and non-functional descriptions and any related explanatory material for ONAP releases.

Midway through a release, the Requirements subcommittee will provide its proposal for the requirements to be supported for the next release.

Requirements subcommittee will not develop full e2e new use cases.

Definition

Functional requirement - ONAP platform functional enrichment, enabling to build a different e2e use cases.

e2e use case - a new e2e functionality enriching ONAP platform, comprising of a different functional requirements. It can be tested e2e.

Process


Meeting logistics

Mailing List

 onap-usecasesub@lists.onap.org 

Meeting Information

Bi-weekly Monday - 7:00am PDT, 10:00am EDT, 10:00pm China Time

Topics for discussion:

  1. Functional requirements proposed for Release X
  2. Non-functional requirements proposed for Release X
  3. Conferences Preparation, Reports, Review & Discussion
  4. Requirements status reports

This would be done under assumption that a detailed architecture work over flow definition and different modules functional split is done by the architecture subcommittee.

 While:

 WHILE

  1. M-GATES – Discussion about the M1-2-3-4 gates. Where we are on Score Cards, PJM type discussion and topics, Status on Milestones. Bringing people together related to Use Case and where we are on the Use Cases.
  2. BRIDGING – tie together Architecture , Requirements, and TSC calls. Identifying those key things that come from those other calls back to what is relevant for Use Cases.
  3. STEERING –Steering Key Topics for discussion & investigation. Identifying what we need to be investigating.
  4. TESTING - Testing and Integration/Regression Dev-Test are key topics that span U/Cs. Tying in integration status, and discussion about where testing and integration needs to evolve. For example a discussion of regression testing and how that will be done, or what developments in automation of integration team means to the U/Cs.
  5. PTL CAMEOS – have a “schedule” of PTLs to make cameo appearances at the U/C (Monday) call and then reach out to the U/C owners to ask what they need to discuss w/ the PTLs and reserve 30min (or the whole meeting) to meet with that PTL discussion U/C topics.
  6. RELEASE CONTENT – the Release and Next Release Content, USE CASES/FUNCTIONAL REQUIREMENTS WISE. What potential new U/Cs are we thinking about for R5 El Alto for example.
  7. CONFERENCES – Discussion about Preparation and review of topics and presentations and logistics. Then after the conference discussion of Reports, Readouts, Review, and Retrospectives.
  8. U/C REQUIREMENTS STATUS – Use Case FUNCTIONAL AND NON-FUNCTIONAL Reports & StatusCross U/C INTERACTIONS and INTERDEPENDENCIES – share the Cross-U/C Interactions finding, and create Steering topics for further investigation by the U/C teams or U/C realization calls.

Requirements subcommittee meeting minutes

IRC

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/655429955

Or iPhone one-tap (US Toll): +16465588656,655429955# or +14086380968,655429955#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 655 429 955

International Numbers

 https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86