...

ONAP/VNFRQTS  VNF Requirement Discussion  

EPIC statement structure for requirements

For each requirement adopt a standardized numbering scheme, and format

...

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

The Subject of the Requirements sentence should be limited to { VNF | VNF Package | VNFC | VDU }

Requirements should be individually numbered. 

The .rst formatting of the requirements should be such that the documentation can extract a complete set of requirements as a table in an appendix. 

EPIC statements 

The  Project Charter also mentions the development of "EPIC statements". The ONAP JIRA wiki uses the term User Story Syntax  for the same structure:

see discussion in ONAP/VNFRQTS  VNF Requirement Discussion  

EPIC statements a standalone deliverable beyond the JIRA wiki are not going to be produced in the Amsterdam release.

Use of EPIC Statements/ Suer Story Syntax  as context in the VNFRQTS Requrimenst deliverable is optional in the Amsterdam release. ie it may be used to provide some explanatory context for the requirements statements, but it is not systematcially applied in the Amsterdam release.

...

Use Case Template

For each use case adopt a standardized format

...