This documentation supports the 9.0 version of Remedy IT Service Management Suite.

To view the latest version, select the version from the Product version menu.

Release Lifecycle Automation use case

Each use case has a Universal Modeling Language (UML) robustness diagram associated with it. A robustness diagram depicts the core components of a system and how the components communicate or collaborate with one another to satisfy a use case. Arrows between the components indicate the flow of information between the components.

The following symbols are used:

Symbol

Meaning

Actor — User role that interacts with a component in the system

Boundary — Component that represents an interface with which Actors interact

Entity — Domain objects within the system that typically present a persisted state of that object

Control — Components that connect Boundary and Entity components and implement some logic to manage the interaction between them

The goal of the Release Lifecycle Automation use case is to illustrate how release requests are initiated and managed through fulfillment by coordinating change implementations.

This use case has the following steps:

  1. Release requests might be a result of an end user request from the BMC Service Request Management interface, but they are not created directly by end users. To provision a new release request, a user starts with BMC Service Request Management (SRM). For purposes of this use case, BMC Service Request Management comprises six logical components — Service Request Portal, Service Fulfillment Engine, Service Catalog, BMC Asset Management, BMC Change Management, and BMC Atrium CMDB. A user, using the Service Request Console, selects a service offering that represents the provisioning of a virtual system and associated software. Depending on how the service request has been configured, the user might be asked a series of questions regarding such things as server capacity or software to be deployed.
  2. When the user submits the request, it is passed to the Service Fulfillment Engine.
  3. The Service Fulfillment Engine invokes BMC Change Management, passing all required information. A change request is created with data values transferred from the service request through the Service Fulfillment Engine.
  4. The Release Coordinator reviews the change request and creates a release request to manage non-standard changes.
  5. Alternatively, IT Support users can create release requests directly through the Release Management Console. This procedure is called Release Coordination and is used to initiate the implementation of releases.
  6. The Release Management process coordinates changes and activities through a series of milestones. These milestones include the Initiate milestone, the Build milestone, the Test milestone, and the Deployment milestone.
  7. The process can include activities to update the CMDB or Asset attributes through BMC Asset Management or through the Asset Inventory component of BMC Change Management when BMC Asset Management is not present.
  8. After all changes and activities are completed, the release request can be completed and closed.
Was this page helpful? Yes No Submitting... Thank you

Comments