VNFRQTS - R-16560 update from MUST to SHOULD

This should not be must unless we have a Resiliency Impact assessment specification that all is attached to this requirement.

Change-Id: I451161eafb5dcaa94886345b21bc92d7605f2832
Issue-ID: VNFRQTS-186
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>

diff --git a/docs/Chapter4.rst b/docs/Chapter4.rst
index 2d99043..a1ff521 100644 (file)
--- a/docs/Chapter4.rst
+++ b/docs/Chapter4.rst
@@ -214,7 +214,7 @@ Monitoring & Dashboard Requirements
 * R-48917 The VNF **MUST** monitor for and alert on (both sender and receiver) errant, running longer than expected and missing file transfers, so as to minimize the impact due to file transfer errors.
 * R-28168 The VNF **SHOULD** use an appropriately configured logging level that can be changed dynamically, so as to not cause performance degradation of the VNF due to excessive logging.
 * R-87352 The VNF **SHOULD** utilize Cloud health checks, when available from the Network Cloud, from inside the application through APIs to check the network connectivity, dropped packets rate, injection, and auto failover to alternate sites if needed.
-* R-16560 The VNF **MUST** conduct a resiliency impact assessment for all inter/intra-connectivity points in the VNF to provide an overall resiliency rating for the VNF to be incorporated into the software design and development of the VNF.
+* R-16560 The VNF **SHOULD** conduct a resiliency impact assessment for all inter/intra-connectivity points in the VNF to provide an overall resiliency rating for the VNF to be incorporated into the software design and development of the VNF.
 
 c. VNF Security
 ===============