You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The VNF Requirements Project maintains repos for  the source documentation of various deliverable:


RepoPublished forDescriptionEPIC supportedDeliverable document Title(s) 
/guidelinesExternal audienceThis includes objectives and motivations for the VNF Requirements work as well as  aspirational, forward looking, narrative text for use in prototype RFP text.VNFRQTS-6
  •  ONAP VNF Guidelines
/requirementsExternal AudienceThis is narrative text for use in prototype RFP text. VNFRQTS-6
  •  ONAP VNF Requirements
/epicsInternal AudienceFormalized requirements descriptions e.g. "As a ROLE I need SOMETHING so that SOME PURPOSE IS REALIZED"see Project Charter
/usecasesInternal audienceThis 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
  • Mapping VNF use cases and with E2E Release A use cases
/testcasesInternal AudienceThis 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 caseVNFRQTS-8
  • ONAP VNF Requirements Test Descriptions 


VNF Guidelines Document Outline - Wenyo Guan

  1. Introduction 
  2. VNF Context
  3. VNF Characteristics
  4. Summary

VNF Requirements Document Outline - Herb Patten

  1. Introduction
    1. Overview of the document, use of the requirements for
  2. VNF Development Requirements
    1. VNF Design
    2. VNF Resiliency
    3. VNF Security
    4. VNF Modularity
    5. Devops
  3. Infrastructure Requirements
    1. OpenStack Heat Guidelines
    2. TOSCA
  4. ONAP Management Requirements
    1. Service Design
    2. Configuration Management
    3. Monitoring & Management
  5. Appendix
    1. Data Record Formats

EPIC statement structure for requirements

For each requirement adopt a standardized numbering scheme, and format

Reqt #Requirement text
xxxAs a ROLE I need SOMETHING so that SOME PURPOSE IS REALIZED


Use Case Template

For each use case adopt a standardized format

  1. Title
  2. Requirement #
  3. summary
  4. Actors (VNF, Operator, ONAP Platform etc.)
  5. Preconditions
  6. Operational sequence ( e.g. Message Sequence chart + text explanations) 
  7. Post conditions

Test Case Description Template

  1. Title
  2. Requirement #
  3. Use Case #
  4. summary
  5. ONAP Actors (VNF, Operator, ONAP Platform components etc.)
  6. Preconditions ( ONAP, VNF states, test equipment/ data patterns, measurements) 
  7. Operational sequence ( e.g. Message Sequence chart + text explanations) 
  8. Post conditions (any post processing of the measurements, any cleanup of the ONAP configuration, reset of the test equipment etc.)
  9. Test Result decision ( measurement  decision criteria )
  • No labels