The VNF Requirements Project maintains repos for the source documentation of various deliverable:
Repo | Published for | Description | EPIC supported |
---|---|---|---|
/guidelines | External audience | This is aspirational, forward looking, narrative text for use in prototype RFP text. | VNFRQTS-6 |
/requirements | External Audience | This is narrative text for use in prototype RFP text. | VNFRQTS-6 |
/epics | Internal Audience | Formalized requirements descriptions e.g. "As a ROLE I need SOMETHING so that SOME PURPOSE IS REALIZED" | see Project Charter |
/usecases | Internal audience | This is a template structure providing a context for specific requirements. This illustrates behavior, sequences of operation, variants, error conditions, etc. There may be multiple use cases associated with a single requirement. Documents VNF specific use cases in support of ONAP E2E use cases. | see Project Charter |
/testcases | Internal Audience | This expands the use case template structure to supply the additional fields necessary to describe a test scenario. There may be multiple test case descriptions associated with a single use case | VNFRQTS-8 |
VNF Guidelines Document Outline
- Introduction
- VNF Context
- VNF Characteristics
- Summary
VNF Requirements Document Outline
- Introduction
- VNF Design
- VNF Resiliency
- VNF Security
- VNF Modularity
- Devops
- Heat Guidelines
- TOSCA
- ONAP Service Design Time Requirements on VNFs
- Configuration Management
- Monitoring & Management
- Data Record Formats
EPIC statement structure for requirements
Reqt # | Requirement text |
---|---|
xxx | As a ROLE I need SOMETHING so that SOME PURPOSE IS REALIZED |
Use Case Template
The