Versions Compared

Old Version 1

changes.mady.by.user Alla.Goldner

Saved on

compared with

New Version Current

changes.mady.by.user Byung-Woo Jun

Saved on

Key

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

Requirements Subcommittee Members

The use case Requirements subcommittee is responsible for developing use cases required for ONAP releases. This includes basic flows, VNFs and requirements, including alignment with use cases focused on VNF Requirements, along with a set of required guidelines for ONAPbringing functional and non-functional requirements required for ONAP releases. It will be used as an input for developing functional architecture and detailed software architecture per release. The use case  

The mission of the Requirements Subcommittee is:

      • Act as the ONAP Product Owners 
      • Recommend Prioritization to the TSC
      • Create the consolidated ONAP Backlog coming from the different streamlines (outside/internal + EAUG)
      • Act as TCC (Technical Community Coordinator) for 5G and Edge topics

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 use case 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 use case Requirements subcommittee operates on a rough consensus basis.  If the subcommittee is unable to reach consensus on what use case requirement to offer, the subcommittee will refer the matter to the TSC.

subcommittees approach.pptx


Mailing list Moderators

Alla.GoldnerRamki Krishnan 

Membership List

Participation

The use case Requirements subcommittee is open to all interested participants, and all meetings are open. Use case 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 use case Requirements subcommittee will develop and maintain use case functional and non-functional descriptions and any related explanatory material for ONAP releases by the Template to be fulfilled per each requirement .

Midway through a release, the use case Requirements subcommittee will provide its proposal for the use cases requirements to be supported for the next release, including prioritization proposal for the submitted requirements.

For achieving this, requirements subcommittee will work closely with the EUAG and create a consolidated priorities list.

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

  • Use Case Evaluation Process
    • Use Case Goals & Selection Criteria

    • Requirements proposals are presented by the requirements owners
      • This will include requirements coming from Modelling, Seccom, Closed Loop subcommittees 
    • EUAG priorities are presented by EUAG
    • Based on all submitted requirements and priorities discussions, the Requirements subcommittee will create a priorities proposal for the upcoming release and present it to the TSC for discussion and approval as a scope of the next upcoming Release

    Meeting logistics

    Mailing List

     onap-requirements-usecasesub@listssub@lists.onap.org 

    Meeting Information

    Every Monday - 7:00am PDT, 10:00am EDT, 10:00pm China TimeBi-weekly Monday - 2 PM UTC

    Topics for discussion:

    1. M[x]-GATES, Score Cards, PJM, Status on Milestones
    2. Architecture , Requirements – TSC Bridging
    3. Steering Key Topics for discussion & investigation
    4. Testing – Evolution – Integration/Regression Dev-Test
    5. PTL cameos
    6. Release Content & Next Release ContentFunctional requirements proposed for Release X
    7. Non-functional requirements proposed for Release X
    8. Input from EUAG
    9. Overall prioritization proposal for the TSC
    10. Conferences Preparation, Reports, Review & Discussion
    11. Use Case Reports & Status
    12. Cross-U/C Interactions Steering topics
      Requirements status reports

    This would be done under assumption that different use cases/functional requirements tracks for covering their detailed work continue.

     While:

  • 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.
  • 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.
  • STEERING –Steering Key Topics for discussion & investigation. Identifying what we need to be investigating.
  • 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.
  • 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.
    • 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.

    a detailed architecture work over flow definition and different modules functional split is done by the architecture subcommittee.

     WHILE

    1. CONFERENCES – Discussion about Preparation and review of topics and presentations and logistics. Then after the conference discussion of Reports, Readouts, Review, and Retrospectives.
    2. U/C REQUIREMENTS STATUS – Use Case FUNCTIONAL AND NON-FUNCTIONAL Reports & Status
    3. Cross 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.
    Use Case Subcommittee Meeting Minutes

    Requirements subcommittee meeting minutes

    Additionally, an optional usecase realization meetings information can be found under Use Case Realization Meeting Register MoM. The following topics are being discussed there typically: cross-dependencies, requirements documentation, coordination with PTLs, some specifics of SDO/open source collaboration e.g. ORAN etc.

    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