Glossary for IBM Engineering Lifecycle Management

This glossary provides terms and definitions for IBM® Engineering Lifecycle Management.

The following cross-references are used in this glossary:
  • See refers you from a nonpreferred term to the preferred term or from an abbreviation to the spelled-out form.
  • See also refers you to a related or contrasting term.


  1. In configuration management, to update a stream to take changes that someone else has delivered.
  2. In source control management, to add any change set to a repository workspace. The change set can come from a stream, another repository workspace, or it can be attached to a work item.
access permission
A privilege that permits the access or use of an object.
access token
  1. An object that contains security information for a process or thread, including the identity and privileges of the user account that is associated with the process or thread.
  2. A value used by the consumer to gain access to the protected resources on behalf of the user, instead of using the user’s service provider credentials.
Pertaining to the project data such as costs, dates, and work that have occurred, as opposed to those that are scheduled, or planned.
actual result
The behavior produced/observed when a component or system is tested. (ISTQB)
An intermediary software component that allows two other software components to communicate with one another.
adoption item
A development work item that tracks when changes by one team must be adopted by another team.
agile software development
A software development methodology that focuses on collaboration and quality to produce complete product increments at regular intervals, called iterations or sprints.
See application lifecycle management.
Ant with Enterprise Extensions
A set of extensions to Apache Ant that makes it possible to build z/OS-based applications using Ant.
Apache Ant
A Java-based open-source tool from Apache Software Foundation that is used to automate build processes.
One or more computer programs or software components that provide a function in direct support of a specific business process or processes. See also application server.
application lifecycle management (ALM)
An iterative and continuous process of coordinating people, processes, and tools with the goal of delivering a software or systems project. This process involves planning and change management, requirements definition and management, architecture management, software configuration management, build and deployment automation, application security, and quality management. The features of this process include traceability across lifecycle artifacts, process definition and enactment, and reporting.
application server
A server program in a distributed network that provides the execution environment for an application program. See also application.
A value passed to or returned from a function or procedure at run time.
An entity that is used or produced by a software or systems development process. Examples of artifacts include designs, requirements, source files, plans, scripts, simulations, models, test plans, and binary executable files. In an HTTP context, artifacts have a URI and are called resources. See also back link, baseline, component, configuration, configuration provider, configuration specification, global configuration provider, revision, stream, version.
Artifacts page
A list of all of the artifacts in a project, as they exist at the project level.
artifact type
A class of objects that is specific to an artifact. For example, requirements management artifacts include the following types: document, business process sketch, user interface sketch, user interface sketch part, screen flow, storyboard, use case diagram, requirement, glossary, and term. See also resource shape.
To appoint or designate a profile or resource to an activity that is to be completed within a specified period.
Pertaining to events that are not synchronized in time or do not occur in regular or predictable time intervals.
A defined quality and values that can be assigned to an artifact. For example, a work item artifact might have a 'priority' or 'severity' attribute.
attribute data type
A descriptor of the information that can be stored in an attribute. Data types might define integer values, string values, date values, and other basic formats of data.
attribute group
Convenience grouping of one or more attributes. For example, the attribute group "Address" might include the attributes Street, City, State, and Zip.
An examination of the changes that have been made to a artifact over time.
The process of granting a user, system, or process either complete or restricted access to an object, resource, or function.
  1. To automatically retrieve and package build output, then move that output to another location for users to run or test it.
  2. An automated process that retrieves and packages build output, and then moves that output to another location so that users can run or test it.
auto-resolve conflict
The automatic merging of conflicting changes to an item. Conflicts can only be automatically resolved if the conflicting changes are made to two separate areas within the item.


back link
A relationship between artifacts in different products where each artifact stores a link that points to the other artifact. See also artifact, back linking.
back linking
A process in which two links are used to define a relationship between artifacts in different products. Neither product has to query for these links because that information is provided in each product. See also back link.
In agile development, a list of features or technical tasks that are necessary for a project or release that the development team assesses and prioritizes to assign work.
base artifact
An artifact that is at the project level and not viewed as an embedded object in another artifact.
  1. An uneditable configuration of one or more components that captures a meaningful state of artifacts. Teams can use baselines as a known configuration or an initial state for a new stream of work. See also artifact, configuration, stream.
  2. In source control management, a permanent copy of a component in a particular repository workspace or stream. A component baseline represents a configuration of a component at a particular point in time.
baseline staging stream
See staging stream.
The status of a test case that cannot be run because the preconditions for running the test case have not been met.
To create a stream for parallel or insulated development.
build definition
An object that defines a build, such as a weekly project-wide integration build.
build engine
The representation of a build system that runs on a dedicated server.
business process sketch
A diagram that illustrates a directed flow of activities that are specified by using a subset of Business Process Modeling Notation (BPMN). Two types of processes are supported: simple and business-to-business.
business rule
A policy, constraint, or required operation that applies to a specific set of business conditions or dependencies. An example of a business rule for a bank is that a credit check is not required when opening an account for an existing customer.


A function or feature that is made available by an application, tool, or product.
See change and configuration management.
A digital document that binds a public key to the identity of the certificate owner, thereby enabling the certificate owner to be authenticated. A certificate is issued by a certificate authority and is digitally signed by that authority.
change and configuration management (CCM)
A systematic approach to establish and maintain the consistent performance of a system or product throughout its lifecycle, and to effectively manage changes in that product or system.
change management
The process of controlling and tracking modifications to artifacts.
change request (CR)
  1. A request from a stakeholder to change an artifact or process.
  2. A request to change some aspect of the project, project plan, activity definition, or document.
change set
A group of related changes to artifacts in a workspace or stream.
A collection of test environment properties that describes a delivery platform in your test effort.
check in
To save local changes in a change set that is part of a repository workspace. A checked-in change set can later be shared with a team by delivering the change set.
class loader
Part of the Java virtual machine (JVM) that is responsible for finding and loading class files. A class loader affects the packaging of applications and the runtime behavior of packaged applications deployed on application servers.
class path
A list of directories and JAR files that contain resource files or Java classes that a program can load dynamically at run time.
The malicious practice of hiding links in clickable content to redirect users to an unexpected location.
See Collaborative Lifecycle Management.
CLM project
A project that was created using IBM Collaborative Lifecycle Management tools.
  1. A new version of an artifact in a different component. The new version has the same ID as the original artifact.
  2. To create a new version of an artifact in a different component. The new version has the same ID as the original artifact. See also refactor.
See configuration management.
code churn
A report that shows the volume of changes in a project over time.
cold standby
A recovery method in which backup servers with installed applications are in place and in a stopped state.
Collaborative Lifecycle Management (CLM)
See Engineering Lifecycle Management.
An annotation attached to an artifact, element, or a collection of elements.
completed change set
A change set that can no longer be changed. Change sets can be shared with others only after they are marked as a completed change set.
complexity attribute
An attribute that enables the selection of another attribute by which work items are sized. This attribute is used in release plans to compute the progress of each plan.
  1. In source control management, a grouping of related artifacts in a stream or repository workspace. A component can contain any number of folders and files.
  2. In configuration management, a unit of organization for a reusable set of engineering artifacts. A configuration of a component selects versions of the artifacts of that component. See also artifact, component skew.
component skew
A situation that occurs when a configuration hierarchy contains different configurations of the same component. See also component, configuration.
concurrent-use license
A license that limits the number of users that can be connected to a resource concurrently.
config spec
See configuration specification.
A unique set of versions of artifacts. Configurations commonly identify one version of each artifact in the set. The artifacts can be unchanging (from a baseline) or open to change (in development). In some systems, configurations can be hierarchical, so that they contain other configurations. See also artifact, baseline, component skew, configuration context, configuration management, configuration provider, configuration specification, global configuration, global configuration management, global configuration provider, local configuration, stream, version.
configuration context
The current configuration that is being worked in, which is either a local configuration or a global configuration. See also configuration, global configuration.
configuration layer
A customized set of metadata that can be used to configure data sources and variables.
configuration management (CM)
A process for grouping and tracking versioned artifacts across the development lifecycle to help identify and track the artifacts in a specific version of a system. See also configuration, global configuration management.
configuration provider
An application that manages sets of versioned artifacts, for example, change management or test management artifacts. See also artifact, configuration.
configuration specification (config spec)
A set of rules that specify versions of artifacts. Commonly a configuration specification identifies at most one version of a given versioned artifact. See also artifact, configuration, version.
A situation in which two or more change sets independently modify the same item in a repository workspace.
In IBM Engineering Lifecycle Optimization - Engineering Insights views, the set of UI properties that define the look and feel of links between artifact containers.
consequence cost
The impact on cost if a risk is not addressed.
An entity that receives data from another entity.
content assist
A feature of some source editors that prompts the user with a list of valid alternatives for completing the current line of code or input field.
content link
A simple hypertext link in rich text or graphical artifacts that provides navigation only. See also trace link.
content store
The database that contains the data needed to operate, such as report specifications, published models, and security rights.
context-aware search
A search function that uses natural language terms to search for work items and source code in Java, C, C++, and COBOL. Regular expressions and wildcard characters are not required.
context root
The web application root, which is the top-level directory of an application when it is deployed to a web server.
See change request.
critical path
A series of activities that determines the earliest completion of a project; the critical path changes as activities or tasks are completed ahead or behind the original schedule estimates.
CSV file
A text file that contains comma-separated values. A CSV file is commonly used to exchange files between database systems and applications that use different formats.


A user interface component that provides a comprehensive summary of pertinent information from various sources to the user.
data collection
The process of collecting data from one or more sources, cleansing and transforming it, and then loading it into a database.
data driven testing
A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the table. Data driven testing is often used to support the application of test execution tools such as capture/playback tools. (ISTQB) See also keyword driven testing.
data dump
A large amount of data transferred from one location or system to another.
data mart
A subset of a data warehouse that contains data that is tailored and optimized for the specific reporting needs of a department or team. A data mart can be a subset of a warehouse for an entire organization, such as data that is contained in online analytical processing (OLAP) tools.
data model
A common model that facilitates reporting of all types of data from multiple data sources.
data set definition
A Jazz model object that describes a data set on z/OS and is stored in the IBM Engineering Workflow Management Jazz repository. If the data set already exists, the data set definition must specify just the data set name. If the data set is new, the data set definition must specify both the name of the data set, and the characteristics of the data set, such as record format. Every data set that a build process references must correspond to a data set definition.
data set prefix
An identifier that, together with the data set name (indicated in the data set definition), specifies a data set that is allocated to IBM Engineering Workflow Management. A data set prefix can contain multiple segments, including a high-level qualifier (HLQ); for example, HLQ.PROD. With a prefix defined by a user, artifacts can be modified in isolation from other users.
data source
The source of data itself, such as a database or XML file, and the connection information necessary for accessing the data.
data spill
An unintentional or unwanted disclosure of data.
data type
In programming languages, a descriptor of a set of values together with a set of permitted operations. A data type determines the kind of value that a variable can assume or that a function can return.
data warehouse
A subject-oriented collection of data that is used to support strategic decision making. The warehouse is the central point of data integration for business intelligence. It is the source of data for data marts within an enterprise and delivers a common view of enterprise data.
A project element that allows stakeholders to track bugs and bug fixes.
defect aging
A report that helps track patterns in defects, which can be used to take corrective action for reducing both defect resolution time and number of defects.
defect report
A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. (ISTQB)
  1. In source control management, to conduct an outgoing flow of change sets and baselines from a repository workspace to a stream or to another repository workspace.
  2. To add changes to a stream, or make them available to be accepted into a stream.
A link between interrelated projects activities. Activities with these links depend on the start and finish dates of at least one other element and therefore cannot be completed without taking the other into consideration.
dependency build
A build definition that saves time and system resources by only building artifacts that need to be rebuilt based on what has changed since the last successful build. Changes to a program's source or dependencies, and deletion or modification of a program's output will be detected and cause the program to be rebuilt.
A process that retrieves the output of a build, packages the output with configuration properties, and installs the package in a pre-defined location so that it can be tested or run.
deployment plan
A template of a virtual service definition.
To remove a change set from a repository workspace.
An item that can be stored, retrieved, and exchanged among systems and users as a separate unit. It can be any multimedia digital object. A single document can include varied types of content, including for example, text, and images.
document generation
The process of applying a template to a data source to generate a document-style report.
document specification
The definition of document templates, data sources, and output formats used to create a report.
Pertaining to a direction that goes with the flow of a development process that moves from requirements to designs to implementation to tests. For example, tests are downstream from requirements. See also upstream.
A period of time during which a project element continues. It is calculated as the finish time minus the start time.


An open-source initiative that provides independent software vendors (ISVs) and other tool developers with a standard platform for developing plug-compatible application development tools.
The estimated hours of work required for an activity. Effort is calculated based on the specified duration (in days) of the activity, and the number of working hours per day specified in the project calendar. See also work.
See Engineering Lifecycle Management.
Engineering Lifecycle Management (ELM)
The integration of products on Jazz technology to connect the work of analysts with development and test teams. These integrations provide a common approach to artifact linking, dashboards, security, and user interface frameworks.
entity tag (ETag)
An HTTP header that is used for web cache validation and conditional requests from browsers for artifact resources. These headers are unique and can be quickly compared to determine whether two artifact versions are the same. ETags can also help prevent artifacts from being overwritten by simultaneous updates.
entry criteria
The set of generic and specific conditions for permitting a process to go forward with a defined task, e.g. test phase. The purpose of entry criteria is to prevent a task from starting which would entail more (wasted) effort compared to the effort needed to remove the failed entry criteria. (ISTQB)
In agile development, a work item that defines a big use case with a large or unknown amount of work, which is often completed over several sprints. Epics can be divided into stories.
See entity tag.
See extract, transform, and load.
An occurrence of significance to a task or system. Events can include completion or failure of an operation, a user action, or the change in state of a process.
execution result
The behavior or response that is produced or observed when a component or system is tested. This behavior and information regarding the test run such as the weight distribution and result details are also recorded. See also expected result.
exit criteria
The set of generic and specific conditions, agreed upon with the stakeholders, for permitting a process to be officially completed. The purpose of exit criteria is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing. (ISTQB)
expected result
The behavior predicted by the specification, or another source, of the component or system under specified conditions. (ISTQB) See also execution result.
A client-side element or function that is not installed with a system, but instead is authored by a system user.
external contribution
The contribution of a global configuration that resides on one Global Configuration Management server to a global configuration that resides on a different Global Configuration Management server.
extract, transform, and load (ETL)
See data collection.


A test is deemed to fail if its actual result does not match its expected result. (ISTQB)
fine-grained component
See component.
A dependency type between two project elements where the predecessor element must finish before the successor element can start.
An arrangement between two workspaces or between a workspace and a stream that enables users to deliver and accept change sets.
flow target
A source or destination of incoming and outgoing change sets. In a team setting, most workspaces have flow targets. The flow target can be another repository workspace or a stream. Streams have flow targets only if they are part of a stream hierarchy.
formal review
A review characterized by documented procedures and requirements, e.g. inspection. (ISTQB)
An entity that has an established connection to another entity for communication. For example, a server can be a friend to another server.
full capacity licensing
A method of licensing in which the licensee must obtain PVU entitlements that are sufficient to cover all activated processor cores in the physical hardware environment that are made available to or managed by the licensed program.
functionality testing
The process of testing to determine the functionality of a software product. (ISTQB) See also security testing.


A proprietary widget that works under specific conditions or that is designed to a certain standard, such as a dashboard widget based on the OpenSocial standard. See also widget.
Gantt chart
A graphical representation of a project timeline and duration in which schedule data is displayed as horizontal bars along a time scale.
In source control management, a state in which a target workspace or stream is missing preceding change sets for a change set that is being accepted or delivered. When a gap occurs, the change set cannot be accepted or delivered; it must be applied as a patch, which creates a new resulting change set.
See global configuration management.
global configuration
A configuration that gathers configurations from multiple tools, so you can define all the relevant artifacts for a system. Global configurations can establish the same context across all tools when each tool stores artifacts in otherwise unrelated configurations. See also configuration, configuration context, global configuration management.
global configuration management (GCM)
A process for gathering configurations from multiple tools that helps visualize and manage relationships in the development lifecycle by tracking artifact links across lifecycle tools and stages. See also configuration, configuration management, global configuration.
global configuration provider
A configuration provider that coordinates contributions from multiple configuration providers. See also artifact, configuration.


To secure a system by reducing its vulnerabilty.
An artifact in a module that is automatically numbered and displayed prominently. A best practice is for headings to be their own artifact type.
An area of storage that is allocated with a lifetime unrelated to the execution of the current routine. The heap consists of the initial heap segment and zero or more increments.
A signal that one entity sends to another to convey that it is still active.
home GCM server
See home Global Configuration Management server.
home Global Configuration Management server (home GCM server)
The Global Configuration Management server that an application can contribute configurations to. Typically, this server is the one registered with the Jazz Team Server that is associated with the application.
An empty script in which code can be entered.
hot standby
See idle standby.


idle standby
A recovery method in which backup servers with installed applications are in place and started, but in an idle state.
impact analysis
The identification of how a change to one item affects other, related items.
An item that prevents progress or a work item to track something that prevents progress.
incoming change set
A change set in a stream or repository workspace that flows to a user repository workspace. An incoming change set is present in a workspace flow target, but not in the workspace itself.
incoming link
A link from the current (target) artifact to a source artifact, such as a Validated By link from a requirement to a test case. See also outgoing link.
A set of URIs that point to resources in one or more lifecycle tool so that the set of URIs can be queried together. Access depends on the identity of the authenticated user.
internal contribution
The contribution of a global configuration to another where both configurations reside on the same Global Configuration Management server.
In linking and traceability, pertaining to a manually set status when two artifacts do not satisfy the meaning of the link between them. The contents of at least one artifact must change to satisfy the link. See also suspect, valid, validity summary.
ISPF client
An SCM client used for working with source code from the ISPF interface. The ISPF client can be used to load, edit, check in, and deliver source. It can also be used to access build functions and associate work items with changes.
In agile development, a set period of time in which work is completed. Sprints can vary in length, for example, from 1 to 4 weeks, but typically have a fixed duration within a project.
iteration plan
An artifact that shows the work items and additional unstructured information for a team or project area within a development phase.


Java Database Connectivity (JDBC)
An industry standard for database-independent connectivity between the Java platform and a wide range of databases. The JDBC interface provides a call level interface for SQL-based and XQuery-based database access.
See Java Database Connectivity.


In security, a file or a hardware cryptographic card where identities and private keys are stored, for authentication and encryption purposes. Some keystores also contain trusted or public keys. See also keytool.
A utility used for creating SSL encryption keys and managing the keystores where they are maintained. See also keystore.
A statement or group of statements that one can reuse in test scripts.
keyword driven testing
A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control script for the test. (ISTQB) See also data driven testing.


language definition
A Jazz model object that serially connects the translators used to build an artifact. The association of a language definition to an artifact provides instructions for how the artifact should be built.
last mile
In communications, the final part of the network that delivers services to end users.
A system object that serves as a directory to other objects. A library groups related objects, and allows users to find objects by name.
library definition
A system object that describes an IBM i Library, and is stored in the IBM Engineering Workflow Management Jazz repository. Every library that a build process references must correspond to a library definition.
The complete process for planning, creating, testing, and deploying software or systems.
lifecycle application
A tool that manages the work for a phase of the development lifecycle. See also lifecycle tool.
lifecycle index
A set of URIs that point to resources in one or more lifecycle tools so that the set of URIs can be queried together. Access depends on the identity of the authenticated user.
Lifecycle Query Engine (LQE)
A component that indexes and searches for assets that are stored in any tool that can support the Tracked Resource Set (TRS) specification.
lifecycle tool
An application that manages the work for a phase of the development lifecycle. See also lifecycle application.
In a linked data system, a relationship between two artifacts as expressed by a unique URI.
linked data
A method of publishing structured data so that it can be linked to and from other data sets.
link index provider (LIP)
An application that indexes links to artifacts in contributing applications and makes those links available to other applications.
links explorer
A capability for visualizing relationships among artifacts and modifying those relationships.
link type
A definition of a relationship between artifacts. A link type has a relationship label that indicates how the linked artifacts are related.
link validity
See validity.
See link index provider.
load rule
  1. A statement in the config spec that specifies an element or subtree to load into a snapshot view. Config specs can have more than one load rule.
  2. An entry in a load rule file that determines how an item from a repository workspace, such as a file, folder, or symbolic link, is loaded into a local sandbox.
local change
A change to an element that only exists in a sandbox and has not yet been committed to the repository workspace.
local configuration
A configuration that's managed by one tool. See also configuration.
See Lifecycle Query Engine.


Managed Bean (MBean)
In the Java Management Extensions (JMX) specification, the Java objects that implement resources and their instrumentation.
master configuration
The configuration data held in a set of files that form the master repository for either a deployment manager profile or a stand-alone profile. For a deployment manager profile, the master configuration stores the configuration data for all the nodes in the network deployment cell.
See Managed Bean.
To combine some or all of the content of one stream or baseline into another stream.
metadata model
A set of related dimensions, query subjects, and other objects that represent data for reporting applications.
In the asynchronous migration task, a process that runs to upgrade data for a specific artifact type.
A significant event in a project or process that is used to determine progress toward goals.
In a large diagram, a view that shows a smaller version of the entire diagram to orient users to their current location in the diagram.
A structured document that is composed of multiple requirement artifacts. Structure can be created in a module by modifying the order and hierarchy of the artifacts.
An MBean (managed bean) that references a predefined set of data types so that any client, including a remote client, can use the bean.


An HTTP-based authorization protocol that gives applications scoped access to a protected resource on behalf of the resource owner, by creating an approval interaction between the resource owner, client, and resource server.
Open Services
See Open Services for Lifecycle Collaboration.
Open Services for Lifecycle Collaboration (Open Services, OSLC)
An open community that facilitates collaboration and standardization across the delivery lifecycle by building practical specifications for integrating software.
See Open Services for Lifecycle Collaboration.
outgoing change set
A change set in a repository workspace that flows to a stream or to another repository workspace. An outgoing change set is present in a workspace, but not in a workspace flow target.
outgoing link
A link from the current (source) artifact to a target artifact, such as a Satisfies link from a test case to a requirement. See also incoming link.
outgoing synchronization
A process by which changes that users make to work items are propagated to the ClearQuest user database.


  1. A product or component that is specifically designed for installation by IBM Installation Manager.
  2. A subset of a project that is created to make metadata available to users. Different packages can be created so different user groups can create the reports they need.
In a graphical interface, a predefined display image that typically provides fields and controls that help users accomplish tasks.
parameter (parm)
A value or reference passed to a function, command, or program that serves as input or controls actions. The value is supplied by a user or by another program or process.
See parameter.
  1. A test is deemed to pass if its actual result matches its expected result. (ISTQB)
  2. The status of a test when the actual results match the expected result.
A sequence of characters used either with regular expression notation or for path name expansion, as a means of selecting various characters strings or path names, respectively. The syntaxes of the two patterns are similar, but not identical.
personal stream
In configuration management, a modifiable configuration of artifacts that is insulated from public streams. Users can test their changes before delivering them to a public stream.
See product line engineering.
A separately installable software module that adds function to an existing program, application, or interface.
Environmental and state conditions that must be fulfilled after the execution of a test or test procedure. (ISTQB) See also precondition.
Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure. (ISTQB) See also postcondition.
An activity in a dependency relationship that logically precedes another.
In software and systems development, a rank assigned to requirements or work items to determine the order in which they are worked on.
processor core
A single processing unit on a chip with multiple processing units.
processor value unit (PVU)
A unit of measure that is assigned to each processor core for software licensing purposes. PVUs vary according to chip architecture. See also subcapacity.
Something produced that is marketed or sold. A product is formed from a particular configuration of component parts, which can be software applications, physical parts, or services. A complex product might contain multiple systems. A system might be made up of multiple products. See also product line, system, variant.
product backlog
See backlog.
product family
See product line.
product line
A group of closely related products that are variants of each other. Products that make up a product line are often produced from a common base or architecture. See also product, system, variant, variation point.
product line engineering (PLE)
A method for designing and developing a line of products that are based on common components with variations in features and functions to provide a diverse product line efficiently at a reduced development cost.
A temporary endeavor or initiative created and managed to achieve an organization's objectives.
project area
An area in the repository where information about one or more software projects is stored.
project area configuration
See local configuration.
project release plan
An artifact that shows plan items and additional unstructured information for a team or project area and all related child team areas and iterations.
project snapshot
A subset of a baseline that identifies artifacts that have been approved or assigned to a milestone or other meaningful event.
A mechanism for moving binaries, source code, source code data, build maps, output, Partitioned Data Sets (PDS) on z/OS or libraries on IBM i, and other build artifacts up the development-test-production hierarchy on a z/OS or IBM i system.
A characteristic of an object that describes the object. A property can be changed. Properties describe an object name, type, value, or behavior, among other things.
To permanently delete data from a location, system, or database.
See processor value unit.


See quality management.
quality management (QM)
A systematic approach to build quality into a solution and assess the quality of deliverables and processes throughout a project lifecycle.
  1. A specification for a set of data retrieved from a data source.
  2. A way of retrieving information from the lifecycle index of artifacts, such as products, work items, requirements, design models, and test cases. The resulting list of artifacts can be used to populate a view, run a report, perform an analysis, and more.


See Uniform Resource Identifier.
  1. A source control operation that makes a development work area current with the set of versions represented by a more recent baseline in another stream, usually the project's integration stream or a feature-specific development stream.
  2. To recalculate the base resources of a tracked resource set.
To compare and optionally update the links in an artifact that point to other artifacts. When a source artifact is reconciled, its links are compared with the states of its associated target artifacts in another application. After reconciliation, the changes can be synchronized or ignored, or the associated artifacts can be updated. See also synchronize.
See scrub.
To make changes across a set of artifacts without changing the behavior of the application or its relationships to other elements. See also clone.
See repository.
A set of data deliberately laid out to communicate business information.
report server
An application server that hosts reports and report editors.
report template
A template that is used to create reports. Parameters in the report template are specified when the report is created or run.
repository (repo)
A persistent storage area for data and other application resources.
repository workspace
A repository object that includes one or more components. Repository workspaces are typically used by individual team members to contain their changes in progress. Team members deliver their changes from their repository workspace to the stream and accept changes from other team members into their repository workspace from the stream. Every repository workspace has an owner, and only the owner can make changes in the workspace. See also workspace.
Representational State Transfer (REST)
A software architectural style for distributed hypermedia systems like the World Wide Web. The term is also often used to describe any simple interface that uses XML (or YAML, JSON, plain text) over HTTP without an additional messaging layer such as SOAP.
See Requirements Interchange Format.
request token
A value that is used by the consumer to obtain authorization from the user and that is exchanged for an access token.
  1. A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document. (ISTQB)
  2. A condition or capability that a system must provide. This condition is either derived from user needs or stated in a contract, standard, specification, or other document.
Requirements Interchange Format (ReqIF)
An XML file format and workflow to exchange requirements, metadata, and status between software tools from different vendors.
requirements management (RM)
A systematic approach to eliciting, organizing and documenting the requirements of a system, and establishing and maintaining agreement between the customer and the project team on changes to those requirements.
Requirements Management Rich Text Format (RM-RTF)
The native format of textual requirements in the RM system.
To reconcile conflicts among change sets in a repository workspace.
  1. A specific XML entity in an XML data source. A resource can be associated with an XML schema and can be used to map a data source to a relational database table to create reports.
  2. See artifact.
  3. A person who can be assigned to work breakdown structure (WBS) elements.
resource definition
  1. See library definition.
  2. See data set definition.
resource group
A collection of XML sources from a product that share a common base web address. The web address determines the connection between the product data and the relational database that is used to create reports.
resource leveling
During plan scheduling, the process of resolving over-allocated resources by delaying tasks until the assigned resources are available to work on them.
resource shape
In the Open Services for Lifecycle Collaboration (OSLC) specification, a high-level description of the contents, properties, and constraints of a resource. See also artifact type.
response file
A file that can be customized with the setup and configuration data that automates an installation. During an interactive installation, the setup and configuration data must be entered, but with a response file, the installation can proceed without any intervention.
See Representational State Transfer.
To reinstate a previously suspended change set to a repository workspace.
reverse proxy
An IP-forwarding topology where the proxy is on behalf of the back-end HTTP server. It is an application proxy for servers using HTTP.
A version of an artifact that is designed to replace an earlier version, such as a model year of a car or a revised requirement. See also artifact, version.
rich hover
An in-context preview of the content that a link points to when the cursor hovers over the link.
An ongoing or upcoming concern that has a significant probability of adversely affecting the success of major milestones.
See requirements management.
See Requirements Management Rich Text Format.
roll back
To revert a software package to a previously installed version.


An area on a file system where a developer can modify and test items in isolation, before returning them to the source control component and sharing them with other developers. A sandbox is a reflection of all or part of a repository workspace on disk.
schedule constraint
A limit to set controls on the start and finish dates on project tasks. Available constraints are as soon as possible and finish-no-later-than.
A specification for the structure and semantics of some related data. The schema is used to validate or otherwise understand a group of data.
See System for Cross-domain Identity Management.
  1. See software configuration management.
  2. See source control management.
screen flow
A representation of a sequence of user-driven software processes that are presented as a series of graphical user interfaces.
To permanently delete all instances of and references to specific data, such as removing all traces of sensitive information from an application.
An agile software programming method that uses small, self-organizing, cross-functional teams, and iterative, incremental practices.
A daily, informal meeting between stakeholders in an agile development project. Participants must include a scrum master, the product owner, and the team and might include the product manager and other stakeholders.
search path
A list of the libraries provided to a IBM Engineering Workflow Management build to locate artifacts for the build, including the load library and object library for an i Project on IBM i.
security certificate
A certificate containing information used by the SSL protocol to establish a secure connection. The information can include who a certificate belongs to, who issued it, its unique serial number, its valid dates, and its encrypted 'fingerprint’ that is used to verify the contents of the certificate.
security testing
Testing to determine the security of the software product. (ISTQB) See also functionality testing.
server friend
A server that allows other servers to communicate with it. After cross-server communication is configured, project areas and artifacts can be linked across servers.
In software and systems development, a measurement of the importance for a unit of work, for example, critical, high, medium, or low.
silent installation
An installation that does not send messages to the console but instead stores messages and errors in log files. A silent installation can use response files for data input.
Simple Cloud Identity Management
See System for Cross-domain Identity Management.
single sign-on (SSO)
An authentication process in which a user can access more than one system or application by entering a single user ID and password.
  1. In IBM Engineering Lifecycle Optimization - Engineering Insights, a saved, shareable instance of a view that shows artifacts and their relationships at the moment that instance is saved. A snapshot can be refreshed to show current artifacts and relationships.
  2. See baseline.
  3. In source control management, a collection of baselines that represents the configuration of a workspace or stream at a particular point in time.
software configuration management (SCM)
The tracking and control of software development. SCM systems typically offer version control and team programming features. See also source control management.
source code data
Metadata, dependency properties, and other user-defined data that are created and updated periodically by running scanners against the source code. The data can be queried, edited, and used to analyze the impact of potential changes. Source code data is used by dependency builds to determine which dependant artifacts have changed and therefore require that buildable files be rebuilt.
source control
A tool that is used to manage source code, documents, and other artifacts to place under version control and share with a team.
source control management (SCM)
An aspect of software configuration management that involves managing changes to collections of files. See also software configuration management.
A query language for RDF that is used to express queries across diverse data sources. The W3 specification defines the syntax and semantic of the SPARQL query language.
See iteration.
See single sign-on.
staging stream
A copy of a stream hierarchy that acts as a staging area for a new baseline.
An individual or organization that is involved in or may be affected by project activities.
stale resource
A resource that is out-of-date in the Lifecycle Query Engine index because a change made in the application is not yet reflected in the index.
start date
A point in time associated with the start of work and usually qualified as actual, planned, estimated, and scheduled. Start date combined with duration and dependencies permits the calculation of finish date.
A development work item that defines part of a use case or a specific contribution to the value of the overall product.
A sequential illustration of a user scenario that consists of numbered frames on a timeline.
  1. In source control management, a repository object that includes one or more components. Streams are typically used to integrate the work that is stored in repository workspaces. Team members deliver their changes to the stream and accept changes from other team members into their repository workspaces from the stream.
  2. In configuration management, a modifiable set of versioned artifacts. See also artifact, baseline, configuration.
Pertains to a software licensing scheme that bases charges on the capacity of the partition where the licensed program is used, rather than on the total capacity in the server. See also processor value unit.
summary task
A container element that comprises a series of tasks.
In linking and traceability, pertaining to a status when two artifacts might not satisfy the meaning of the link between them. The contents of the artifacts must be reviewed to verify that they satisfy the link. See also invalid, valid, validity summary.
To temporarily remove a change set from a repository workspace.
suspicion profile
A profile that identifies a set of link types, artifact types, and attributes to watch for changes. When artifacts that match the profile criteria are changed, the linked artifacts are marked with a suspicion indicator.
See synchronize.
synchronization engine
The process that synchronizes data between Rational ClearCase and IBM Engineering Workflow Management source control.
synchronize (sync)
To add, subtract, or change one feature or artifact to match another. See also reconcile.
A set of individual components, such as people, machines, or methods, that work together to perform a function. See also product, product line.
system definition reference search
A search that is used to discover which artifacts are associated with a particular system definition. The search can also re-reference a set of artifacts with a different system definition in one step.
system definitions
A collective term referring to a group of definitions in IBM Engineering Workflow Management, including IBM i libraries, z/OS data set definitions, language definitions, and translators.
system definitions node
A project node that is used to organize IBM i libraries and search paths, z/OS data set definitions, language definitions, and translators in the Team Artifacts view of IBM Engineering Workflow Management.
System for Cross-domain Identity Management (SCIM)
An Internet Engineering Task Force (IETF) specification and open API for managing user identities in cloud-based applications and services.


An identifier that groups related artifacts.
  1. In agile development, a work item that defines a specific piece of work.
  2. A scheduled project activity to which a resource can be assigned to perform work.
See test case.
See test case execution record.
team area
A place within a project area for managing team membership, roles, assignments, and team artifacts.
team release plan
An artifact showing plan items and additional unstructured information for a team or project area and a development iteration and the associated child iteration plans.
test case (TC)
  1. A set of tasks, scripts, or routines that automate the task of testing software.
  2. A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement. (ISTQB)
test case execution record (TCER)
A record of the execution environments for a specific instance of a test case. One can use this record to run a test case instance and to track the status of each test run.
test configuration
A set of characteristics of the system that hosts the system under test. These characteristics affect the conditions for test execution and the evaluation of test results.
test data
Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test. (ISTQB)
test design specification
A document specifying the test conditions (coverage items) for a test item, the detailed test approach and identifying the associated high level test cases. (ISTQB)
test environment
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test. (ISTQB)
test estimation
The calculated approximation of a result related to various aspects of testing (e.g. effort spent, completion date, costs involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy. (ISTQB)
test plan
A set of test cases that defines an area of testing.
test script
Commonly used to refer to a test procedure specification, especially an automated one. (ISTQB)
test suite
A collection of test cases that are grouped for execution purposes.
test suite execution record (TSER)
A record of the execution environments for a specific instance of a test suite. One can use this record to run a test suite instance and to track the status of each test run.
time code
A code that is used by resources in the timesheet module to classify reported time.
An area of activity in a project that typically has its own schedule, deliverables, teams, and process.
A set of development tools used to write and test software applications.
The physical or logical mapping of the location of networking components or nodes within a network.
trace link
A hyperlink that conveys relationships between the artifacts it links, such as dependency, origin, derivation, implementation, or validation. Trace links have link types, which are defined by an Open Services for Lifecycle Collaboration specification or by a project. See also content link.
track build item
A development work item that tracks required fixes after a failed build.
tracked resource set (TRS)
The set of resources in a finite collection of artifacts, expressed as a set of members (a base) and a change log.
A Jazz model object that describes a single build step in which a translator executable program is invoked with the required inputs and outputs. Inputs and outputs are the same as z/OS data sets or IBM i libraries, so a translator must reference multiple data set or library definitions.
The process of systematically visiting each node in a diagram or tree once.
To systematically visit each node in a diagram or tree once.
See tracked resource set.
trusted consumer
A consumer that can share authorization with other trusted consumers and does not require user approval to access data. A consumer must be designated as trusted in an access request to become a trusted consumer.
See test suite execution record.
type definition
An entry in the type system for an artifact type, attribute, data type, or link type.
type system
The set of types of artifacts and the definitions of their attributes, data types, and link types that are available in an application.


Uniform Resource Identifier (URI)
A unique address that is used to identify content on the web. The most common form of URI is the web page address, which is a particular form or subset of URI called a Uniform Resource Locator (URL). A URI typically describes how to access the resource, the computer that contains the resource, and the location of the resource on that computer.
Pertaining to a direction that goes against the flow of a development process that moves from requirements to designs to implementation to tests. For example, requirements are upstream from tests. See also downstream.
See Uniform Resource Identifier.
use case
The specification of a sequence of actions that a system can perform, interacting with users of the system. Use cases are used in system analysis to identify system requirements.
user interface sketch
A mock-up of a graphical user interface at any one point in the application's operation.


In linking and traceability, pertaining to a manually set status when two artifacts satisfy the meaning of the link between them. See also invalid, suspect, validity summary.
In linking and traceability, an assessment of whether two artifacts satisfy the meaning of the link between them. See also validity summary.
validity summary
In linking and traceability, an aggregate assessment of whether links for an artifact are valid. See also invalid, suspect, valid, validity.
In IBM Engineering Workflow Management, a user-defined parameter that can be included in the command and option strings of the translator.
A version of an artifact or a product that is identified by a specific set of characteristics that distinguish it from other artifacts or products in the product line, where each variant can exist at the same time as other versions of the artifact or product. See also product, product line, variation point.
variation point
An aspect of a design with multiple potential values that, when chosen, define one of the characteristics that distinguish one product from another within a product line. See also product line, variant.
verbose logging
A logging option that records more information than standard logging to provide information for troubleshooting.
The referenceable state of an artifact. In a linked data system, each version can be referenced with a unique URI. See also artifact, configuration, configuration specification, revision.
  1. In Eclipse-based user interfaces, any pane in the workbench that is outside the editor area and can be stacked (dragged and dropped) on top of other views. Views provide different ways to look at or work with the resources in the workbench.
  2. A subset of information that can be displayed by applying filters or sorting.
V process model
A visual representation of the systems development lifecycle as a modified waterfall methodology, with the phases arrayed across a V shape to correlate development with testing.


See work breakdown structure.
web app
See web application.
web application (web app)
An application that is accessible by a web browser and that provides some function beyond static display of information, for instance by allowing the user to query a database. Common components of a web application include HTML pages, JSP pages, and servlets.
A list of accepted, approved, or recognized items.
A portable, reusable application or piece of dynamic content that can be placed into a web page, receive input, and communicate with an application or with another widget. See also gadget.
A simple line diagram or schematic that is used to mock up user interfaces or web pages.
An assignment to tasks with estimated or planned hours. See also effort.
work breakdown structure (WBS)
A grouping of project elements, organized in a hierarchical tree structure. It defines the total scope of the project at the highest level in the tree and each descending level provides an increasingly granular definition of each element.
A sequence of connected steps that moves an action to completion.
work item
An artifact representing a generalized notion of a development task, such as a task, defect report, or enhancement request.
  1. In Eclipse, the collection of projects and other resources that the user is currently developing in the workbench. Metadata about these resources resides in a directory on the file system; the resources might reside in the same directory. See also repository workspace.
  2. A context that contains a collection of artifacts that a user with appropriate permission can modify.
workspace flow target
A source or destination of incoming and outgoing change sets.
workspace snapshot
A record that captures the contents of a repository workspace at a particular time. A workspace snapshot consists of a collection of baselines, one for each component in the repository workspace.


XDC file
See XML data configuration file.
XML data configuration file (XDC file)
A configuration file that defines the relationship between entities in a data source and columns in a relational table.


A logical group of z/OS artifacts that share a common context; for example, all of the artifacts in a zComponent might comprise part of some application.
zComponent project
  1. A container into which buildable artifacts, such as COBOL programs, can be grouped.
  2. An Eclipse integrated development environment (IDE) project with specific z/OS IBM Engineering Workflow Management components.
An artifact that represents a PDS member on MVS. A zFile can be associated with a language definition for Ant builds or for Rational Developer for System z integration syntax checking.
A container for a group of artifacts within a zComponent Project, used to represent a partitioned data set (PDS). Each zFolder is associated with a data set definition to create the source PDS on z/OS.

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki