Hi Feng, Whether something is a requirement or a recommendation would not depend on whether it uses VFC or not. The document is a requirements document, so having requirments in the chapter headings would not preclude the chapter from having requirments with various degrees of testability etc. This seems like the sort of evaluation that would need to be made on a requirement-by-requirement basis.
best regards Steven Wright, MBA, PhD, JD. [Tech Integration] AT&T Services Inc. 1057 Lenox Park Blvd NE, STE 4D28 Atlanta, GA 30319 P: 470.415.3156 [email protected]<mailto:[email protected]> www.linkedin.com/in/drstevenawright/<http://www.linkedin.com/in/drstevenawright/> From: [email protected] [mailto:[email protected]] Sent: Tuesday, July 18, 2017 9:51 PM To: WRIGHT, STEVEN A <[email protected]> Cc: [email protected] Subject: [onap-discuss] [VNFRQTS] Some thoughts about VNF Development Requirements, we probably could make it as recommendations? Hi Steven, In VNF Requirements Deliverables<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Document-2BOutlines-2Bfor-2BVNF-2BRequirements-2BDeliverables-3Fsrc-3Dcontextnavpagetreemode&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=PVu8DKytqBISpqDc36NHSA&m=k30tUQ2VmOoeix0eYKqlTtXY2EZv9ufOXU8AonXoBtM&s=JtcZVtcZrIQ_a8tH-jdNEu2WGbp3hb9WhOYBIlX27Eo&e=> page, I think it would be better if we changed chapter 2 (VNF Development Requirements) as below to VNF Developement Recommendations. Suppose customers use ONAP to manage VNFs through the path of VF-C. In this case most of vnf requirements listed in VNF Requirements for OpenECOMP are not necessary as long as customers' VNFs could be managed and monitored by ONAP successfully. 2. VNF Development Requirements a. VNF Design b. VNF Resiliency c. VNF Security d. VNF Modularity BR Feng yuanxing
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
