e them available for enterprise-wide composition. From a top-down view, SDC supports product managers who compose new products from existing services/resources in the SDC catalog or acquire new resource capabilities from internal or external developers. The components of SDC are shown in Figure 7.5. The SDC "Design Studio" consists of a portal and back-end tooling for onboarding, iterative modeling, and validation of the network cloud assets. The design studio includes a set of basic model templates that each project can further configure and extend with additional parameters, parameter value ranges, and validation rules. The configured project-specific templates are used by the design studio graphical user interface (GUI) (as drop-down menu or rule-based validation) to validate the designs. This ensures the models contain the necessary information and valid values based on the type of model and the project requirements. SDC provides access to modeling tools that can be used to create executable process definitions that will be used by the various network cloud components. Processes can be created with standard process modeling tools such as BPMN tools. The processes created are stored in the process reposi- tory and asset models in the catalog may refer to them. The models in the master reference catalog can be translated to any industry-standard or required proprietary format by the distribution studio. The modeling process does not result in any instantia- tion in the run-time environment until the MSO receives a request to do SO. SDC will integrate with third-party suppliers, leveraging models for their management functions as needed for onboarding, configuration, analysis, and cataloging of software assets along with their entitlement and license models as part of the design studio. 7.3.2 DATA REPOSITORIES SDC Data Repositories maintain the design artifacts and expose content to the designers, testers, and distributors. The repositories include the following: 1. Master reference catalog is the data store of 