SDC is the OpenECOMP ONAP visual modeling and design tool. It creates internal metadata that describes assets used by all OpenECOMP ONAP components, both at design time and run time.
...
The definitions of assets include Information Artifacts and Deployment Artifacts. Information Artifacts are provided by the vendor of an asset such as a VNF; they describe characteristics of the asset. Some of these artifacts are supporting documents intended for human readers only, whereas others contain data that will be imported into the OpenECOMP ONAP environment when the asset is onboarded.
Once assets are on-boarded, the information provided by the vendor is translated into SDC internal resource models. The service provider will use SDC to further enrich the resource model to meet the provider’s environment, and additionally compose resources into service models and product models. The model includes not only the description of the asset but also references to OpenECOMP ONAP functions needed for lifecycle management of the asset. The tested models will then be distributed to the OpenECOMP ONAP execution environment as Deployment Artifacts.
The Deployment Artifacts include the asset definition (a Resource or Service or Product model) with instructions to OpenECOMP ONAP for creation and management of an instance of the asset in the network. Currently, SDC imports and retains information from Heat Templates for cloud infrastructure creation, YANG XML files for state data manipulated by the Network Configuration Protocol, TOSCA files for specifying cloud infrastructure, and certain vendor provided scripts. In the future, SDC may import BPMN/BPEL files for specifying business processes and their interconnections in a service-oriented architecture.
<<DocRef: OpenECOMP ONAP User Guide>>, under the section "Design", describes how to use the SDC.
...