Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When introducing significant changes to the VNF Requirements project or changes that may require discussion.  It recommended that a Proposal be created.  The wiki page will be the place to collaborate and track changes as the proposal is reviewed, revised, and ultimately accepted or rejected.

Please follow these steps when creating a proposal.

  1. Copy the Proposal Template and create a page under the Proposals section of the VNF Requirements Wiki.
  2. Update the content of your proposal and set the status to Draft
  3. Create a JIRA ticket in the VNF Requirements project announcing the ticket, and put a reference to the ticket on the Proposals page
    1. Project: VNF Requirements
    2. Issue Type: Task
    3. Summary: Proposal Review:Title of Proposal
    4. Description: Link to proposal

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

...

  •  ONAP VNF Guidelines

...

  •  ONAP VNF Requirements

...

  • Mapping VNF use cases and with E2E Release A use cases

...

  • ONAP VNF Requirements Test Descriptions 

VNF Guidelines Document Outline

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

VNF Requirements Document Outline

  1. Introduction
  2. VNF Design
  3. VNF Resiliency
  4. VNF Security
  5. VNF Modularity
  6. Devops
  7. Heat Guidelines
  8. TOSCA 
  9. ONAP Service Design Time Requirements on VNFs
  10. Configuration Management
  11. Monitoring & Management
  12. Data Record Formats

EPIC statement structure for requirements

For each requirement adopt a standardized numbering scheme, and format

...

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 )