odules that will increase feature development velocity. Formal information models will allow the separation of network service definition from the network design from a vendor-specific implementa- tion. This will allow vendor devices to change without impacting the network design abstraction layer or the network service abstraction layer. The network abstraction layer can change from a switch to a router to an optical multiplexor, without impacting the network service layer. Control of NFV will permit new processes for software validation by using virtual routers/switches in the network. Building the Network of the Future PMO Service Delivery Process - Simple Features Service Network Business Systems Systems Definition Needs Configuration Requirement Design Document Document Document Document Development Deploy Service UAT/ORT Ready FMO Service Delivery Process - Simple Features Service Network Agile Business Definition Tools Needs Configuration Framework Test Yang Templates Yang Templates Files Compile Field Emulation Service Templates Verification Ready FIGURE 6.2 Service delivery. The present mode of operation (PMO) shown in Figure 6.2 follows the waterfall development process where each function is handled by a different organization. Design specification documents are created in the first five steps from the individual organization's perspective, basically translating the preceding organization's requirements into the current organization's terminology and require- ments. This method entails many pair-wise and then group-wide reviews of the different documents, and can create a lot of misinterpretation. The execution steps of development, test, deployment, operational readiness testing phases are also serially executed to get to a service-ready status. Along each of these "execution" steps, interpretation of the documents and clarification or changes to the developed service are iterated until all agree that the service is ready. The future mode of operations (FMO) introduces a new paradigm, which drasticall