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

Compare with Current View Page History

« Previous Version 5 Next »

TSC subcommittee name:

Use case Subcommittee (UC)

Membership

Alla Goldner alla.goldner@amdocs.com

Brian Freeman bf1936@att.com

Vivien Yang vivien.yang@intel.com

Yoav Kluger yoav.kluger@amdocs.com

Zhaoxing Meng mailto:meng.zhaoxing1@zte.com.cn


Meeting logistics:

Kickoff meeting: Monday, June 19, 1500 UTC

Meeting Information:

Every other Monday - 7:00am PDT, 10:00am EDT, 10:00pm China Time

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 available: https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86

Participating in UC meetings

  • Use case 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

TSC subcommittee purpose:

The use case 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 ONAP. It will be used as an input for developing functional architecture and detailed software architecture per release.

The use case subcommittee will not make decisions regarding Release’s functional architecture or internal functioning of projects. It is a support group for the TSC Chair and the TSC

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

TSC subcommittee expected deliverables:

The use case subcommittee will develop and maintain use case descriptions and any related explanatory material for ONAP releases.

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

TSC subcommittee starting participants:

The use case subcommittee is open to all interested participants, and meetings are open.

  • No labels