Summary

Criteria used to select use cases

  • Demonstrates merged ONAP architecture
  • Demonstrates services planned for 2018 can be orchestrated and managed by ONAP
  • Demonstrate integration of both commercial and open source VNFs and components
  • Enhances the platform consistent with ONAP mission and needs of planned and future services
  • The scope can be realized and dependencies met in a YE2017 release

Process

  • TSC sub-committee submitted 9 new cases
  • Identified common platform requirements that enable the most use cases
  • Combined similar use cases into 2 new proposed use cases in addition to the vFW that is currently available as demonstration.


The light gray font in the table below represent sub-functional requirements, bundled under a higher level requirement.


Use Cases

  • No labels

7 Comments

  1. Oliver Spatscheck

    Not sure I agree with the separation of functional/non functional requirements. E.g. change management is none functional in my mind.

  2. user-67d6f

    Out of AAA, only Audit listed partially, IMO, Authentication and authorisation are missing.  

  3. jin xin

    what does the gray font mean?

    1. user-67d6f

      i think these functionalities  (marked gray) are not required for the 3 use cases listed

      wiki got updated (as they are sub functionalities)

  4. Vincent Colas

    Can we add open loop service and/or resource assurance features to the list?

  5. Avinash S

    Scalability. Framework scalability could be a potential addition. 

  6. Steven Wright

    ETE platform use cases will need to be aligned with VNF level uses cases associated with VNF Requirements