Requirements Subcommittee Members
The Requirements subcommittee is responsible for bringing 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 mission of the Requirements Subcommittee is:
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.
The Requirements subcommittee is open to all interested participants, and all meetings are open. Requirements subcommittee is contribution-driven.
We will request people to develop proposals/presentations to discuss during meetings and via email
The Requirements subcommittee will develop and maintain 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 Requirements subcommittee will provide its proposal for the 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.
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.
onap-requirements-sub@lists.onap.org
Bi-weekly Monday - 2 PM UTC
Topics for discussion:
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
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.
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
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86