VNFRQTS-23 requires the VNFRQTS project to agree on a "standard" format for requirements for the ONAP Amsterdam release. This task is assigned for resolution in Sprint 2. There are a number of aspects top this task - Key words, processes and tooling
Key Words
Processes
Use Cases for Requirements
- Requirements as text in a .hmtl formatted VNF Requirements deliverable for use in RFPs - EPIC - VNFRQTS-6
- Requirements as table for conformance mapping - User Story - VNFRQTS-27
- Correlate VNF Requirements and VNF test cases for validation - EPIC - VNFRQTS-8
- Subsets of the requirements apply for particular conformance mapping activities beyond complete VNFS e.g.
- VNF Requirements impacting the VNF Package definition - User Story - VNFRQTS-28
- VNF Requiremenst for configurable parameters - User Story - VNFRQTS-28
Requirement identifiers
Requirements should be uniquely identified.
Requirement attributes
Attributes may be required to support subsetting the list of requirements.
Once identified, VNF Requirements are not expected to be very dynamic, but there may be some changes required between ONAP releases.
A VNF Requirement version attribute may be required to accommodate this.
Some VNF Requirements may be forward looking ie anticipated to apply in future releases.
Some VNF Requirements may be optional
Tooling
The VNF Requirements "master" in the .rst files in the vnfrqts/requirements repo.
The documentation projects Jenkins job builds the .html onto the http://onap.readthedocs.io website
Tooling is needed to extract just the requirements sentence from the table format. This is expected to require the VNF requirements to be tagged appropriately in the ,rst source files