P, BSS, OSS, and the network cloud. This agreement is a behavioral contract to permit both the detailed business analysis and the construction of software to run in parallel. The software development teams focus on building service-independent software within a com- mon operations framework for runtime automation, while the business teams can focus on tackling unique characteristics of the business needs by defining metadata models to feed the execution envi- ronment. The metadata model content itself is the glue between design time and runtime execution frameworks, and the result is that the service-specific metadata models drive the common service- independent software for runtime execution. The metadata model is managed through a design environment (SDC) that guides a series of designers through third-party resource onboarding, service creation, verification, and distribution. The modular nature of the SDC metadata model provides a catalog of patterns that can be reused in future services. This provides a rich forward-engineering approach to quickly extend resource functions to manageable services and sellable products, further realizing benefits in time to market. SDC is the ONAP component that supports metadata model design. Many different models of metadata exist to address different business and technology domains. SDC integrates various tools supporting multiple types of data input (e.g., YANG, HEAT, TOSCA, YAML, Business Process Management Notation [BPMN]/BPEL, etc.). It automates the formation of this metadata format to drive end-to-end runtime execution. SDC provides a cohesive and collaborative environment for design, test, certification, version control, and distribution of metadata models across the resource, service, product, and offer development lifecycle. In SDC, the resource metadata is created in the description of the network cloud infrastructure and the configuration data attributes to support the service implementations on that network cloud. Subsequently, the resource metadata descriptions