Hi Raghavan, I agree with your suggestion and It will be much easier to track each function individually by justing relating them.
As 5G use case is tracking the sub-use cases in this way, I think it could also work for our use case. Thanks a lot for your advice. Best, Lin 发件人: "[email protected]" <[email protected]> 日期: 2019年10月10日 星期四 03:50 收件人: LinMeng <[email protected]>, David McBride <[email protected]> 抄送: Alla Goldner <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, Henry Yu <[email protected]>, Henry Yu <[email protected]>, Gaurav agrawal <[email protected]>, "[email protected]" <[email protected]>, Borislav Glozman <[email protected]>, Jim Baker <[email protected]> 主题: RE: [Onap-usecasesub] Agenda for the next week's meeting Hi Lin & all, I propose that we keep the JIRA REQ-141 & REQ-37 independent and have them linked through ‘relates to’ option in JIRA instead of merging them to make things easier. I say this because there are some fundamental differences in architecture/goals between Multi-domain optical service use-case and the CCVPN extension proposal and we would like to have them tracked individually from a functional requirement standpoint. While we agree there are synergies between the use-cases, I suggest that we follow the approach similar to 5G where each of the sub use-cases are managed & tracked independently under the broader 5G umbrella. Thanks, Raghavan From: [email protected] <[email protected]> On Behalf Of LinMeng Sent: Wednesday, October 9, 2019 3:16 AM To: David McBride <[email protected]> Cc: Alla Goldner <[email protected]>; [email protected]; [email protected]; Provencher, Denise <[email protected]>; Miao, Xin <[email protected]>; Henry Yu <[email protected]>; Henry Yu <[email protected]>; Gaurav agrawal <[email protected]>; [email protected]; Borislav Glozman <[email protected]>; Jim Baker <[email protected]> Subject: Re: [Onap-usecasesub] Agenda for the next week's meeting Hi David, May I ask how to combine two REQs or how to do extension work on one REQ due to two REQs are required to be merged into one use case? For example: REQ-141 is CCVPN for Frankfurt, REQ-37 is multidomain optical service, Multidomain optical service now is asked to be merged into CCVPN use case. What should I do to involve REQ-37 into REQ-141? Best, Lin 发件人: Alla Goldner <[email protected]> 日期: 2019年10月4日 星期五 00:36 收件人: "[email protected]" <[email protected]>, Ramki Krishnan <[email protected]>, "[email protected]" <[email protected]>, LinMeng <[email protected]>, Borislav Glozman <[email protected]>, Srini <[email protected]> 抄送: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> 主题: Agenda for the next week's meeting Hi, Here is agenda for our next Monday’s (07/10/2019) meeting. The most important to understand what the status of the following use cases/functional requirements towards Frankfurt Release: Edge Automation – where it stands – Ramki, we need your inputs Report on progress of Network slicing discussions – we need a report of what is the current status Multidomain optical service (supposed to be merged with CCVPN) – what is the current status HPA – are there any finalized plans for Frankfurt? We didn’t get any report during the f2f meeting on this Please also double check https://wiki.onap.org/display/DW/ONAP+Frankfurt+Release+Architecture+Requirements and see if your requirement is missing/not approved. We need to resolve all inconsistencies urgently. Owners – please bring your information. Best regards, Alla This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19160): https://lists.onap.org/g/onap-discuss/message/19160 Mute This Topic: https://lists.onap.org/mt/34472562/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
