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.
| Child pages (Children Display) |
|---|
Membership
Mailing list Moderators Alla.Goldner, Ramki Krishnan, Gildas Lanilis Gmail
Alla Goldner alla.goldner@amdocs.com
Anatoly Andrianov anatoly.andrianov@nokia.com
Andrei Kojukhov andreik@amdocs.com
Alex Vul alex.vul@intel.com
Avi Chapnick avich@amdocs.com
Brian Freeman bf1936@att.com
Chengli Wang wangchengli@chinamobile.com
Damon Li damonl@vmware.com
Eric Debeau eric.debeau@orange.com
Ethan Lynn ethanlynnl@vmware.com
Yuangxing Feng feng.yuanxing@zte.com.cn
Gil BULLARD wb5674@att.com
Helen Chen helen.chen@huawei.com
Hui Deng denghui12@huawei.com
Jianguo Zeng zengjianguo@huawei.com
Jimmy Forsyth James Forsyth
Jinhua Fu fu.jinhua@zte.com.cn
Joe Zhang zhang.zhou1@zte.com.cn
Jon Taylor jon.taylor@amdocs.com
John Zannos jaazannos@gmail.com
Kang Xi kang.xi@huawei.com
Lingli Deng denglingli@chinamobile.com
Liron Shtraichman lironsh@amdocs.com
Li zi li.zi30@zte.com.cn
Lv Bo lv.bo163@zte.com.cn
Maopeng Zhang zhang.maopeng1@zte.com.cn
Mark Pond mpond@amdocs.com
Mazin Gilbert mazin@research.att.com
Nagesha Subramanya nagesha.subramanya@nokia.com
Nir Rapaport Nir.Rapaport@amdocs.com
Oleg Kaplan oleg.kaplan@amdocs.com
Marc Volovic Marc.Volovic@amdocs.com
Avi Ziv Avi.Ziv@amdocs.com
Gautam Shah GAUTAMS@amdocs.com
Steven Blimkie Steven.Blimkie@amdocs.com
Tian Lee <TianL@amdocs.com>
Oliver Spatscheck spatsch@research.att.com
Sumit Verdi sverdi@vmware.com
Timo Perala timo.perala@nokia.com
Tomer Oster tomer.oster@amdocs.com
Vimal Begwani Begwani@att.com
Vivien Yang vivien.yang@intel.com
Xinhui Li lxinhui@vmware.com
Yoav Kluger yoav.kluger@amdocs.com
Yang Xu yang.xu3@huawei.com
Yan Yang yangyanyj@chinamobile.com
Yunlong Ying ying.yunlong@zte.com.cn
Yosi Ben-Tsur yosi.bentsur@amdocs.com
Zhaoxing Meng meng.zhaoxing1@zte.com.cn
Wenyao Guan guanwenyao@chinamobile.com
Yuan Liu liuyuanyjy@chinamobile.com
Tao Shen shentao@chinamobile.com
Victor Gao victor.gao@huawei.com
Xin Jin saw.jin@huawei.com
Seshu Kumar seshu.kumar.m@huawei.com
Guirong Wang wangguirong@boco.com.cn
Xiaodong Ning ningxiaodong2017@boco.com.cn
Hu Dong donghu@raisecom.com
Yannan Han hanyanan@raisecom.com
jamil chawki jamil.chawki@orange.com
Michal Pawlowski michal.pawlowski1@orange.com
Jacopo Pianigiani jpianigiani@juniper.net
Luman Wang wanglm.bri@chinatelecom.cn
Sujing Zhang zhang.sujing@zte.com.cn
Catherine Lefevre cl664y@att.com
Christophe Closset ChrisC
Gervais-Martial Ngueko Gervais-Martial Ngueko
Pamela Dragosh Pamela Dragosh
Randa Maher rx196w@att.com
Dan Timoney dtimoney@att.com
Amir Levy amir@gigaspaces.com
DeWayne Filppi DeWayne@gigaspaces.com
Arthur Berezin arthur@gigaspaces.com
Nati Shalom natis@gigaspaces.com
Huabing Zhao zhao.huabing@zte.com.cn
Heliu Zhong zhognheliu@boco.com.cn
Yuanwei Yang yangyuanwei@boco.com.cn
Jingbo Liu liujingbo@boco.com.cn
zhangxiong Zhou zhouzhangxiong@boco.com.cn
Michael O'Brien frank.obrien@amdocs.com
Anbing Zhang zhanganbing@chinamobile.com
Ying LI liying@chinamobile.com
Shasha Guo guoshasha@chinamobile.com
Evgeniy Zhukov evgeniy.zhukov@netcracker.com
Susana Sabater susana.sabater@vodafone.com
Davide Cherubini davide.cherubini@vodafone.com
Sergio Pozo sergio.pozo@vodafone.com
Vladimir Yanover vyanover@cisco.com
Pasi Vaananen pvaanane@redhat.com
Ramki Krishnan ramkik@vmware.com
Lee Cowdrey leeco@amdocs.com
Meeting logistics
Mailing List
onap-usecasesub@lists.onap.org
Meeting Information
Every 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
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86
| Child pages (Children Display) |
|---|
Participation
The use case subcommittee is open to all interested participants, and all meetings are open. 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
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.
Process
- Use case subcommittee discuses new use cases
- For every use case, Use case subcommittee describes ONAP Platform capabilities desired for the implementation, produces use case flow diagrams, breaks use case into platform requirements (functional and non-functional), provides its view on the foreseen modules introductions/modifications and suggests potential PNFs / VNFs
- Use case and Architecture subcommittees jointly review platform requirements required by the new use case and/or by the release
- Use case subcommittee gets feedback from the potentially effected projects including integration team on feasibility and development time estimation
- Architecture subcommittee evaluates impact of the platform requirements on the architecture and makes updates as required.
- Iterate back to step 2.
- Architecture, Use Case, and Modeling subcommittees discuss and select key platform requirements for the release
- TSC approves the selected key platform requirements for the release.
- In case a new modules or a new functionality to existing modules or a new APIs introduction is foreseen, architecture subcommittee defines the new/modified ONAP flows and the interfaces principles, based on the approved platform requirements.
- Projects define their extended functionality and their external APIs, following those principles
- Detailed per-component flows are defined by the projects and projects write their user stories / implement them; Integration team continuously works with Use case subcommittee to accompany the requirements development, review epics/user stories, answer questions, etc. Use case subcommittee behaves as system engineers for the platform requirements through test start date
- Integration team defines the gating platform requirements based on step 8 and finalizes the PNFs / VNFs selection, with the help of use case subcommittee, architecture subcommittee, PTLs of a different ONAP projects
- TSC approves the gating platform requirements
- Integration project leads (coordinates) effort to get the gating platform requirements tested, repaired, and verified, and the results are documented
- Use case subcommittee along with the Integration team decides which new and complete use cases can be showcased following new platform capabilities introduction
- The defined functional extensions should be as generic as possible to allow re-use of it by additional use cases.