Glossary

Applications: Bring together components with their deployment targets and orchestrate multi-component deployments.
Application Releases: Manage the release of a specific instance of one or more applications through a release train.
Approvals: Approvals may be required to allow a release train to proceed to scoping, QA, and final deployment stages; to validate that a release train may exit a stage based on stage gate exit criteria; and to confirm that pre-defined milestones for release trains or application releases have been reached by a certain date.
Artifacts: Files or other software elements.
Business Requests: Represent work items for an application release in response to a business need. Business requests can come from SBM applications or from integrations with third-party tools, such as ServiceNow.
Component Versions: Instances of a Release Automation component, which is the artifact to be deployed or otherwise configured.
Deployment Paths: Sequences of environments into which you schedule your turnover deployments.
Deployment Tasks: Sets of steps in the deployment process. Deployment tasks can be manual or executed in Release Automation.

Deployment Units: See Component Versions.
Development Tasks: Represent work items for an application release. Development tasks can come from SBM applications or from integrations with third-party tools, such as Atlassian JIRA.
Environments: Sets of resources to which turnovers are deployed. These are user-defined collections of resources that host an application, typically modeled on some stage of the software project life cycle, such as development, QA, or production. An environment can consist of a single machine, be spread over several machines, or be spread over clusters of machines.
Milestones: Date-based activities against which progress can be measured. Milestones are typically interim deliverables within a life cycle stage.
Projects: Containers for release items, such as application releases, release trains, and environments; SBM projects.
Release Approvals: Built-in approval items that may be required for the release train to enter the Scoping, QA, and final stages. The default approval names are Train, Development, and Executive. Up to four levels of approval may be defined for each of these.
Release Automation: The part of Release Manager that executes automation of release deliveries.
Release Elements: Entities or objects that support your release process, such as applications, environments, release types, and deployment paths.
Release Trains: Calendar-based management of a set of application releases across various life cycle stages. The default stages are Scheduling and Scoping, Construction, Verification, and Deployment.
Release Type: A user-defined category for release trains, application releases, and turnovers. Release type values are stored in an auxiliary table, so that you can easily add the values that are appropriate for your implementation. The default values are Development, Emergency, and Normal.
Resources: Represent a deployment target on a Release Automation environment. Examples include physical machines, virtual machines, databases, or J2EE containers.
Runbooks: Templates of ordered deployment tasks.
Snapshots: A snapshot captures an application's current state, and as the application moves through different environments, the snapshot ensures that proper component versions are used.
Stages: Phases of the release process, such as scoping, construction, and verification.
Stage Gates: The point between one stage and another where exit criteria may be validated and approved as met before the release train can move to the next stage.
Timelines: Present the overall status for release trains and application releases in a calendar format.
Turnovers: Contain all the information needed to deploy application release artifacts to environments.
Work Items: Represent work needed for an application release, such as business requirements and development tasks.