Release management

You can manage assets for the delivery of a release by using IBM® Rational® Asset Manager as a definitive library.

The following figure illustrates the roles and asset types in the development process in delivering a software release by using Rational Asset Manager.

The image shows boxes that represent asset types and the user roles that apply to the delivery of a release over the planning, design, construction and deployment phases of a development cycle. From the upper left to the lower right of the image, the business manager, analyst, architect, release manager, developer, release engineer, quality engineer, and operations managers are shown performing actions on business solution, business case, release, specification, and implementation asset types. At the end of the image, consumers can download the release or other asset types.

As the figure shows, stakeholders collaborate to plan, design, develop, build, test, and deliver a release. For example, business managers create requirements for business solutions, and architects design blueprints for solutions and make solutions available in the asset library. Analysts search for solutions. At the end of development and deployment, consumers download the service in the Implementation asset, which is linked from the published Release asset.

You can use your Rational Asset Manager system as the hub for all the approved versions of files, components, or libraries. You can define approvals for sets of requirements, for example:

You can also use your system to centralize all approved versions of files or libraries that are dependencies for other work products or resources.

With the system, you can govern your business processes, which are defined by asset lifecycles and the relationships between asset types. In the progression of a development lifecycle, the approved Business solution drives a Release, and the Implementation approval drives the approval of the Release.


Feedback