Hello

There is still a lot of requirements. How do we intend to prioritize all the 
requirements ?

In addition, I believe that some requirements are overlapping:

Eg for network slicing, I can find the following requirements and it is 
difficult to commit for such requirements

·         Modeling: Enhanced Nested and Shared Service Information Model - 5G / 
E2E Network Slicing modeling

·         Modeling: 5G / ORAN & 3GPP Standards Harmonization

·         5G / 5G Service Modeling: Modeling (exploratory) work for creating a 
5G Service

·         Vertical Industry Oriented On-demand 5G Slice Service

·         Network Slicing

We also have various levels of description:

-          Some requirements are very atomic

-          Some requirements are more global (eg Network Slicing)

I also noticed that some requirements and use-cases are not listed in the right 
table

·         End to End Layer 1 Service Management. Modeling the Optical Service 
should be a use -case

·         Service Resolver should be a feature and not a use-case

If the requirements only impact one project (and Integration), it should be 
managed at the project level (eg Portal, DCAE/Acumos integration, ...

Best Regards

Eric

De : [email protected] [mailto:[email protected]] De la part de 
Catherine LEFEVRE
Envoyé : vendredi 11 octobre 2019 20:58
À : [email protected]
Objet : [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!
Importance : Haute

Dear Frankfurt « Owners »,

Thank you for submitting your use cases and your requirements for the Frankfurt 
release.
We are really excited to kick-off our Frankfurt as soon as possible
https://wiki.onap.org/display/DW/Frankfurt+Release+Requirements

The TSC is currently performing some prioritizations based on your inputs and 
EUAG inputs.

It is essential that we collect your additional inputs not later than Oct 15th, 
2019 end of your day
If we do not get them on time then we will postpone your use case/requirements 
to the Guilin Release.


*        Use Case / requirements should be reviewed by the Architecture Team 
ASAP

*        As you know, we are currently under capacity concerning our Testing 
activities
Therefore a new column has been added "Integration Lead" to identify per use 
case, per requirement.
The Integration Lead will have the following responsibilities:

o   Identify the testers

o   Define the Integration Test Plan for the use case or requirement

o   Develop with his/her testers the automated tests

o   Provide Test Results to the Integration Team



*        Provide project's impact for your use case/requirement. Example: SDC 
(C); SO (C) , AAI(TO)

C= Code Change, TO= Test Only


[cid:[email protected]]


*        Provide the list of Dev committed to impacted PTL per use case, per 
requirement a.k.a these columns should be filled up


[cid:[email protected]]

               Examples

               SDC committed by Ericsson

               SO partially committed by Nokia

               SO will only support REQ-xxx



*        Provide T-Shirt Size - is it a multiple release requirement or not?

*        Provide Company Engagement

If you look at the TSC minutes (Oct. 10th), you will find the list of missing 
items per use case, per requirement.
https://wiki.onap.org/display/DW/TSC+2019-10-10

If your use case/requirement is not listed in the table then the architecture 
did not approve it or have not yet finalized the review.

Please let us know if you have any question concerning our requests.

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs - Network Cloud and SDN Platform Integration
SDN Platform & Systems
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
[email protected]<mailto:[email protected]>

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5471): https://lists.onap.org/g/onap-tsc/message/5471
Mute This Topic: https://lists.onap.org/mt/34502875/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to