Service Release Blueprint (Key Data Object)

Provides the planned design/configuration of the components of the service system. It contains the description and procedures in order to activate, deploy, and operate a service and its underlying components including applications and technology. May have many variations for a given Service Release as considerations such as environmental (development, stage, and production) or hosting (on premise or cloud) could be specified differently. Iterative development methods may reuse a Service Release Blueprint multiple times.

Relationships:

Service Release to Service Release Blueprint (1:n): A Service Release can be released to different environments based on different Service Release Blueprints.
Service Release Blueprint to Build Package (n:m): Multiple Build Packages, which represent the deployable content of the service components, can be deployed using the instructions contained in the Service Release Blueprints.
Service Release Blueprint to Desired Service (1:n): One Service Release Blueprint can be translated to one or more Desired Service(s).
Service Release Blueprint to Fulfillment Request (1:n): One Service Release Blueprint is used for service instantiation by one or many Fulfillment Requests.
Service Release Blueprint to Service Contract (n:m): One or more Service Release Blueprints contain the template of one or more Service Contracts.
Service Catalog Entry to Service Release Blueprint (1:n): Each Service Catalog Entry is created based on definitions of a Service Release Blueprint.
Service Release Blueprint to Defect (n:m): One or more Service Release Blueprints can contain one or more Defects in the form of Problems/Known Errors.