Versions Compared

Old Version 15

changes.mady.by.user Yan Yang

Saved on

compared with

New Version 16

changes.mady.by.user Yan Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


2 Integration with other projects(VF-C will consume the interfaces these projects provided ):

Functionality Requirement

Requirement Description

Priority
OOM IntegrationIntegration with OOM to deploy VF-CHigh
A&AI IntegrationImprove integration with A&AI(Virtual resource created by VF-C save to A&AI )High
OF Integration Plan to integration with OF when do resource grantingMedia


3 Non-functional Requirement

Reference  ONAP R2 proposals for Non-functional requirements

Non-functional Requirement

Requirement Description

Priority
Community S3P requirementsRequirements abou S3P
Follow naming conventions on APIs
  • Document improvement
  • each API should use the same naming convention for names, types, constants, collections
    • ex. camel case vs all capital letters vs all small letters
    • ex. using dashes vs underscores for separation of types & constants & names
    • ex. use short vs long name of variables (ex. vnfId vs vnfInstanceId vf instId )
  • non supported features should not be visible on API
High