TSC subcommittee purpose:
The use case subcommittee is responsible for developing use cases required for ONAP releases. This includes basic flows, VNFs and 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.