From 325a13f082d011fac3e607b353a51d4ce625b064 Mon Sep 17 00:00:00 2001 From: "Bozawglanian, Hagop (hb755d)" Date: Fri, 13 Apr 2018 20:39:38 +0000 Subject: VNFRQTS - Fixing Scope in Chapter 3 Adding list of requirement targets. Issue-ID: VNFRQTS-103 Change-Id: Ib032bf13c0c13d3d668dc7cf63350244b8f6eeac Signed-off-by: Bozawglanian, Hagop (hb755d) --- docs/Chapter3.rst | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'docs') diff --git a/docs/Chapter3.rst b/docs/Chapter3.rst index f6101f3..81e13b9 100644 --- a/docs/Chapter3.rst +++ b/docs/Chapter3.rst @@ -10,6 +10,15 @@ and OpenECOMP requirements. - Requirements are identified as either MUST, MUST NOT, SHOULD, SHOULD NOT, or MAY as defined in RFC 2119. +- Requirements should be targeted to a restricted set of nouns related + to VNFs and within the control of the VNF provider. The current list + of VNF Requirement targets is: + + - The VNF + - The VNFC + - The VNF Provider + - The VNF Heat + - The VNF Package - Chapter 4 contains the VNF/PNF requirements involving the design and development of VNFs/PNFs. These requirements help VNFs/PNFs operate efficiently within a cloud environment. Requirements cover design, -- cgit