ice, creating a new service pivots to a new model. The service designer selects VNFs from the VNF catalog and customizes them for the service-specific instantiation. The service designer creates chaining rules, service-specific configurations, dimensioning, recipes, and associated policies. Service-specific templates are generated based on this information and are used for the service-specific instantiation. Service Platforms 14.3.2 SERVICE DESIGN METHODOLOGY The traditional waterfall approach for designing services pivots to using the Agile approach with a DevOps model. Design teams partner upfront with all the other organizations, vendors deliver- ing the VNFs are required to deliver software releases in Agile fashion with shorter timeframes for integration and testing in an iterative mode. The high-level design of a virtualized service and the VNFs that comprises the service is documented and the Agile process is used to kick off small scrum teams that then work through the various aspects of the design, network connectivity, inter- working with PNFs, instantiation, control loop scope, etc. This approach enables rolling out service VNFs and capabilities iteratively for testing in the laboratory as well as production environments. A common service design process, common templates to document the design, common templates to provide requirements to partner organizations, and common solutions that apply across all service designs are expected to reduce the overall service design life cycle. As the VNF catalog gets popu- lated and service designers pick their VNFs from the catalog, there should be a further reduction in the service design life cycle. 14.3.3 TESTING METHODOLOGY Figure 14.8 shows the key paradigm shifts required in an SDN/NFV-based architecture. In today's environment, approximately 50% of the testing effort is consumed certifying new hardware plat- forms. By instantiating our network functions on a virtualized cloud platform, the hardware plat- form no longer needs to be tested, and the testing effo