This documentation supports the 9.1 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. A Change Coordinator can directly create such a request by using BMC Change Managment in order to initiate a release request. Also, a Release Coordinator can create a release request in BMC Release Management, directly.
  2. When the user submits the request, it is passed to the Service Fulfillment Engine.

    Note

    A release usually includes multiple approvals, depending on your business needs. For more details about phases in a release lifecycle, see Milestones in the release request lifecycle .

  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. For more details about roles in a Release Lifecyle, see  Release coordinator role .
  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. For more details, see Milestones in the release request lifecycle .
  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. For more details, see Milestones in the release request lifecycle .
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Leonard Warren

    The diagram does not indicate the use of Tasks with Activity and Change Requests.

    The diagram does not indicate the approval process with Release Management.

    Jan 05, 2018 07:28
    1. Jyoti Nerkar

      Hello Leonard, Apologies for the delay in reply. Thanks for pointing out all these points. There are additional topics about Approval processes, milestones, and roles and their functions. I have provided links to those topics at the relevant locations. Hope that helps and clarifies the Release management process in details. Regards, Jyoti

      Apr 03, 2019 05:18
  2. Leonard Warren

    Number 1: If anyone is requesting the need for a Virtual System and Software to be installed, they would not go through SRM. This is a more complex request and is 99% done through Change Management as a Change Coordinator submitting the request as the initial phase to create a Release. Generally, the group asking for the Virtual System and Software would be the organization to perform the work, Thus, they would go directly to the Change Request or Release Request to submit the ticket. I would remove SRM as any possibility and just have the End User submit it through Change Management or Release Management.

    Jan 05, 2018 07:31
    1. Jyoti Nerkar

      Please refer to the reply on this topic.

      Apr 03, 2019 05:19
  3. Leonard Warren

    Number 4 indicates the Release Coordinator would review the Change Request but that is not true. The Change Coordinator would review the Change and then determine if this is a Release or not. Thus, this statement needs to have Change Coordinator as the reviewing role and not Release Coordinator.

    Jan 05, 2018 07:32
    1. Jyoti Nerkar

      Please refer to the reply on this topic.

      Apr 03, 2019 05:19
  4. Leonard Warren

    Number 6 is missing the Planning and Close Down Milestones. Also. there is no indication of Release Approvals at each of the milestones provided - which there are six approval stages that have to be considered.

    Jan 05, 2018 07:33
    1. Jyoti Nerkar

      Please refer to the reply on the earlier comment on this topic.

      Apr 03, 2019 05:20
  5. Leonard Warren

    Number 7 indicates the use of Asset Inventory but you cannot have Release Management without Change and Asset Management installed unless you are talking about a third party Release Management with just the BMC Remedy CMDB product. Not seeing Asset Inventory being made available without Asset Management established.

    Jan 05, 2018 07:34
    1. Jyoti Nerkar

      I will discuss this with an SME and will get back to you on this.

      Regards. Jyoti

      Apr 03, 2019 05:21
      1. Jyoti Nerkar

        Hi Leonard,


        The following topic covers information about Asset Inventory permission:

        https://docs.bmc.com/docs/display/itsm91/Asset+Inventory+permissions

        Regards,

        Jyoti


        Apr 16, 2019 04:22
  6. Leonard Warren

    Number 8, states, "After all changes and activities are completed, the release request can be completed and closed." However, what it should state is, "Each milestone can be moved to completed once all changes and activities have been completed and milestone has passed the approval process. The Release Request can be completed and closed down once the Close Down Milestone has been approved."

    Jan 05, 2018 07:36
    1. Jyoti Nerkar

      Please refer to the reply on the earlier comment on this topic.

      Apr 03, 2019 05:20