For any contributors who would like to edit the VNF Requirements document.

The enhanced toolkit that we are proposing has been developed to help users edit the VNF Requirements documents in a quicker fashion, as well as adding more functional capabilities of the this project. Outlined in this document are the added tools we are proposing:

Current Process Flow

1. All Requirements manually maintained within RST files.

   1. For example:
      

      **Resource Description**
      -------------------------
      * R-77707 The VNF provider **MUST** include a Manifest File that contains a list of all the components in the VNF package.
      * R-66070 The VNF Package **MUST** include VNF Identification Data to uniquely identify the resource for a given VNF provider. The identification data must include: an identifier for the VNF, the name of the VNF as was given by the VNF provider, VNF description, VNF provider, and version.
      * R-69565 The VNF Package **MUST** include documentation describing VNF Management APIs. The document must include information and tools for:
      
      

2. No additional information about individual requirements is maintained.

   1. For example:
      
      1. Release
      2. Testable
      3. etc.
         
         

3. Requirements must be manually updated in multiple locations within the RST files.

   1. Requirements must be managed within the proper Chapter and Section, AS WELL AS within the Appendix.

Proposed Process Flow

1. All Requirements are maintained as JSON Formatted in one document.

   1. For example:

      "R-01334": {
              "description": "The VNF **MUST** conform to the NETCONF RFC 5717, Partial Lock Remote Procedure Call.",
      
              "id": "R-01334",
      
              "section": "Configuration Management",
      
              "type": "VNF",
      
              "testable": "Yes",
      
              "created/modified": "Amsterdam",
      
              "release enforced": "Amsterdam",
      
              "level of enforcement": "MUST"
      
          }
      
      

2. Metadata Retained for each Requirement

   1. Current fields within metadata:
      1. description
      2. id
      3. section
      4. type
      5. testable
      6. created/modified
      7. release enforced
      8. level of enforcement
         
         

3. RST ↔JSON Linking to simplify number of locations that need to be managed

   1. For example:
      

      **Resource Description**
      -------------------------------------------
      
      R-77707
      R-66070
      R-69565