...
Resource: a fundamental capability, implemented either entirely in software, or as software that interacts with a hardware device. Each Resource is a combination of one or more Virtual Function Components (VFCs), along with all the information necessary to instantiate, update, delete, and manage the Resource. A Resource also includes license-related information. There are three kinds of Resource:Anchor Resource Resource - Infrastructure (the Cloud resources, e.g., Compute, Storage) << <<TODO: more specific example??>>
- Network (network connectivity functions & elements) Example: a Virtual Network Function (VNF)
- Application (features and capabilities of a software application) << <<TODO: example?>>
Service: a well formed object comprising one or more Resources. Service Designers create Services from Resources, and include all of the information about the Service needed to instantiate, update, delete, and manage the Service << <<TODO: example? >>Anchor Service Service
Product: includes one or more Services packaged with commercialization attributes for customer ordering, billing, and issue resolution. Products are created by Product Managers, and can have one or more "category" attributes assigned by Product Strategists. << <<TODO: example? >>Anchor Product Product
Offer: bundling of Products with specific Marketing configurations for selling to customers << <<TODO: example? >>Anchor Offer Offer
The key output of SDC is a set of models containing descriptions of asset capabilities and instructions to manage them. These models are stored in the SDC Master Reference Catalog for the entire enterprise to use.
...
- The Catalog is the repository for assets at the Resource, Service and Product levels. Assets are added to the Catalog using the Design Studio.
- The Design Studio is used to create, modify, and add Resource, Service, and Product definitions in the Catalog.
- The Certification Studio, available in 2017, is used to test new assets at all levels. It will be used for sandbox experimentation, and will include support for automated testing.
- The Distribution Studio is used to deploy certified assets. From the Distribution studio, new Product assets, including their underlying Resources and Services, are deployed into lab environments for testing purposes, and into production after certification is complete. In a future release, there will be a way to export Product information to external Business Support Systems for customer ordering and billing.
<< <<TODO: the following paragraph requires expert review; for example, are Heat Templates really Information Artifacts rather than Deployment Artifacts?>>
...