dational principles: 1. The architecture will be metadata-driven and policy-driven to ensure flexible ways in which capabilities are used and delivered 2. The architecture shall enable sourcing best-in-class components 3. Common capabilities are "developed" once and "used" many times 4. Core capabilities shall support many services 5. The architecture shall support elastic scaling as needs grow or shrink These capabilities are provided using two major architectural frameworks: (1) a design time framework to design, define, and program the platform (uniform onboarding) and (2) a runtime exe- cution framework to execute the logic programmed in the design time framework (uniform delivery and lifecycle management). Figure 7.1 shows ONAP frameworks. The design time framework component is an integrated development environment with tools, techniques, and repositories for defining/describing network and service assets. The design time framework facilitates reuse; resources and services are described as models, thus improving effi- ciency, especially as more and more models are available for reuse. Assets include models of net- work cloud resources, services, and products. The models include various process specifications and policies (e.g., rule sets) for controlling behavior and process execution. Process specifications are used by ONAP to automatically sequence the instantiation, delivery, and lifecycle management aspects of network cloud-based resources, services, products, and ONAP components themselves. The design time framework supports the development of new capabilities, augmentation of exist- ing capabilities, and operational improvements throughout the lifecycle of a service. SDC, Policy, and Data Collection, Analytics, and Events (DCAE) software development kits (SDKs) allow operations, security, third parties (e.g., vendors), and other experts to continually define/refine new Design Time Framework Runtime Execution Framework Collaborative, catalog-driven "self-service" design Autonomic framework that manages 