Versions Compared

Key

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

...

VNF Requirements are the foundation of the project and as such have the most stringent content standards.   The requirements form the basis of the specifications that a VNF provider must adhere to in order to successfully deploy and operate a VNF on the ONAP platform.  When considering the content for your requirement in the first place (incomplete or out of place)

  This project makes use of an Sphinx extension called sphinxcontrib-needs to enable a number of useful features both internal to the project and enable sharing of structured data/information between projects.

...

Requirements should be single sentences  using an RFC 2119 keyword { MUST | MUST NOT | SHOULD | SHOULD NOT | MAY }. The keyword should be bold.

The Subject of the Requirements sentence should be limited to { VNF | VNF Package | VNFC | VDU } – Does not match Table values

Requirements should be individually numbered. Format initially will be R-xxxxx

...