Glossary for the Rational solution for Collaborative Lifecycle Management (CLM)

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.

For other terms and definitions, see the IBM® Terminology website (opens in new window).

Entries indicated by "ISTQB" are from the Glossary of Terms Used in Software Testing Version 2.1 that is produced by the International Software Testing Qualifications Board. You can find more software testing terms on the ISTQB website.

A

accept
  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 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. 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.
  2. 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.
actual result
The behavior produced/observed when a component or system is tested. (ISTQB)
adapter
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.
aggregation
The process of collecting, interpreting, and sorting data from various locations into a single file.
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.
ALM
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.
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
The target of a request from an application requester. The database management system (DBMS) at the application server site services the request.
artifact
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, 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 a requirement definition technique. Artifact types include document, business process sketch, user interface sketch, user interface sketch part, screen flow, storyboard, use case diagram, requirement, glossary, and term.
attribute
  1. 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.
  2. A characteristic or trait of an entity that describes the entity; for example, the telephone number of an employee is one of the employee attributes.
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.
auto-deploy
  1. 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.
  2. To automatically retrieve and package build output, then move that output to another location for users to 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.

B

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.
backlog
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.
baseline
  1. 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.
  2. An editable 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.
baseline staging stream
See staging stream.
BI
See business intelligence.
blocked
The status of a test case that cannot be run because the preconditions for running the test case have not been met.
branch
To create a stream for parallel or insulated development.
build
The process during which a build program produces one or more derived objects. This may involve actual translation of source files and construction of binary files by compilers, linkers, text formatters, and so on.
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 intelligence (BI)
The consolidation and analysis of data collected in the day-to-day operation of a business, which is then used as a basis for better business decisions and competitive advantage.
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.

C

capability
A function or feature that is made available by an application, tool, or product.
CCM
See change and configuration management.
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 set
A group of related changes to artifacts in a workspace or stream.
channel
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 path
A list of directories and JAR files that contain resource files or Java classes that a program can load dynamically at run time.
CLM
See Collaborative Lifecycle Management.
CM
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)
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.
comment
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.
component
  1. In configuration management, a unit of organization for a reusable set of engineering artifacts. Components often correspond to project areas. Global configurations exist within a component. See also artifact.
  2. 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.
component skew
A component hierarchy in a global configuration that contains more than one version of a configuration. See also global configuration.
config spec
See configuration specification.
configuration
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, configuration context, configuration management, configuration provider, configuration specification, global configuration, global configuration management, local configuration, version.
configuration context
The current configuration that is being worked in, which is either a project area configuration or a global configuration. See also configuration, global configuration, local configuration.
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.
conflict
A situation in which two or more change sets independently modify the same item in a repository workspace.
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.

D

dashboard
  1. An interface that integrates data from a variety of sources and provides a unified display of relevant and in-context information.
  2. A web user interface component that provides information about the project status at a glance. Users can view project summary information or more detailed information.
database (DB)
A collection of interrelated or independent data items that are stored together to serve one or more applications.
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 mapping template
A template used for mapping XML elements to relational table columns.
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 Movement Service
A service that is used to run and schedule builds and job streams on remote computers.
data set definition
A Jazz model object that describes a data set on z/OS and is stored in the Rational Team Concert 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 Rational Team Concert. 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 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.
DB
See database.
defect
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 arrival rate
A report that shows the frequency of new defect submissions over time, categorized by severity.
defect density
The ratio of the number of defects to the program length.
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)
deliver
  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.
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.
deployment
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.
dimension build
A build that delivers data to describe a single business dimension, such as a product or a customer. A dimension build has a source dimension table, a hierarchy for the data, a target database, and a target table.
dimension data
Data that is used to describe or qualify facts in a star schema fact table.
dimension mapping category
A set of similar dimension maps. For example, a category can be created for days, weeks, and hours, with different levels of granularity.
dimension mapping table
A table that creates correlations between dimension tables from different data sources. Each data source may use different names for semantically similar elements.
dimension table
A table that contains attributes used to constrain and group data when performing data warehousing queries.
discard
To remove a change set from a repository workspace.
document
An item that can be stored, retrieved, and exchanged among Content Manager 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, images, and embedded artifacts.

E

Eclipse
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.
enhancement request
A change request for a new feature or functionality.
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)
epic
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.
ETL
See extract, transform, and load.
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.
extension
A client-side element or function that is not installed with a system, but instead is authored by a system user.
extract, transform, and load (ETL)
  1. See data collection.
  2. The process of collecting data from one or more sources, cleansing and transforming it, and then loading it into a database.

F

fact build
A build that delivers fact data and dimension data so the user can construct a private data mart from within a single build.
fact table
A database table, commonly located at the center of a star schema surrounded by dimension tables, that contains measures of a business process, and foreign keys from the dimension tables.
fail
A test is deemed to fail if its actual result does not match its expected result. (ISTQB)
flow
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. Streams have flow targets only if they are part of a stream hierarchy.
foreign key
In a relational database, a key in one table that references the primary key in another table. See also primary key.
formal review
A review characterized by documented procedures and requirements, e.g. inspection. (ISTQB)
friend
An entity that has an established connection to another entity for communication. For example, a server can be a friend to another server.
functionality testing
The process of testing to determine the functionality of a software product. (ISTQB) See also security testing.

G

gadget
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.
gap
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.
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 component skew, configuration, configuration context, global configuration management, local configuration.
global configuration management
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.

H

heading
An artifact in a module that is automatically numbered and displayed prominently. A best practice is for headings to be their own artifact type.
health
The general condition or state of the database environment.

I

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.
impediment
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.
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.
iteration
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.
iteration velocity
A report that shows the number of tasks completed in each iteration.

J

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 also Open Database Connectivity.
JDBC
See Java Database Connectivity.

K

keyword
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.

L

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.
library
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 Rational Team Concert Jazz repository. Every library that a build process references must correspond to a library definition.
lifecycle
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 tool
An application that manages the work for a phase of the development lifecycle. See also lifecycle application.
link
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.
LIP
See link index provider.
load rule
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, configuration context, global configuration.
lookup build
A simple, single-level reference structure in an extract, transform, and load (ETL) catalogue. Look-ups track the relationships between fact data and the operational data store that contributes to the fact.

M

mapping
The correlation of attributes between specifications. For imports, mappings relate the attributes of the file specification to the attributes of the primary specification of the catalog or hierarchy. For exports, mappings relate the attributes for the primary specification to the attributes of the destination specification.
measure
A value that can be analyzed, such as the number of defects.
merge
To combine one stream or baseline into another stream.
metadata
Data that describes the characteristics of data; descriptive data.
metadata model
A set of related dimensions, query subjects, and other objects that represent data for reporting applications.
metric
A measurement that assesses a key area of a business.
milestone
A significant event in a project or process that is used to determine progress toward goals.
minimap
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.
model
A representation of a process, system, or subject area, typically developed for understanding, analyzing, improving, and replacing the item being represented. A model can include a representation of information, activities, relationships, and constraints.
module
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.

N

namespace
For authentication and access control, a configured instance of an authentication provider that allows access to user and group information. In Framework Manager, namespaces uniquely identify query items and query subjects. Different databases are imported into separate namespaces to avoid duplicate names.
natural key
For data sources that are not in relational databases, the name of an XML file or user name that can be mapped to tables in a data warehouse.

O

ODBC
See Open Database Connectivity.
ODBC driver
A dynamically linked library (DLL) that implements ODBC function calls and interacts with a data source.
Open Database Connectivity (ODBC)
A standard application programming interface (API) for accessing data in both relational and nonrelational database management systems. Using this API, database applications can access data stored in database management systems on a variety of computers even if each database management system uses a different data storage format and programming interface. See also Java Database Connectivity.
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.
OSLC
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 synchronization
A process by which changes that users make to work items are propagated to the ClearQuest user database.

P

package
  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.
page
In a graphical interface, a predefined display image that typically provides fields and controls that help users accomplish tasks.
pass
  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.
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.
physical metadata layer
In the operational metadata model, a layer that contains metadata information from the data source. It also contains query subjects that represent the imported tables and relationships between them.
PLE
See product line engineering.
portal
A single, secure point of access to diverse information, applications, and people that can be customized and personalized.
portlet
A reusable component that is part of a web application that provides specific information or services to be presented in the context of a portal.
postcondition
Environmental and state conditions that must be fulfilled after the execution of a test or test procedure. (ISTQB) See also precondition.
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.
primary key
In a relational database, a key that uniquely identifies one row of a database table. See also foreign key.
priority
In software and systems development, a rank assigned to requirements or work items to determine the order in which they are worked on.
product
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.
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.
profile
A set of behaviors, privileges, or capabilities that determine how database objects interact with resources.
project area
An area in the repository where information about one or more software projects is stored.
project health
The efficiency of a project as reflected through defects, changes, build quality, and work distribution.
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.
promotion
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.

Q

QM
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.
query
A specification for a set of data retrieved from a data source.

R

RDF URI
A custom URI that one assigns to predicates and resources that are used in linked data representations.
reconcile
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.
reference dimension
A dimensional framework that holds reference structures and templates used to provide information when merging data and delivering dimension data into data marts.
relational data
Data stored in a relational database management system (DBMS).
repo
See repository.
report
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.
request token
A value that is used by the consumer to obtain authorization from the user and that is exchanged for an access token.
requirement
  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 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.
resolve
To reconcile conflicts among change sets in a repository workspace.
resource
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.
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.
REST
See Representational State Transfer.
resume
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.
revision
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.
RM
See requirements management.
RM-RTF
See Requirements Management Rich Text Format.
roll back
To revert a software package to a previously installed version.

S

sandbox
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.
SCM
  1. See software configuration management.
  2. See source control management.
scorecard
A collection of metrics representing the performance of one unit or aspect of an organization.
screen flow
A representation of a sequence of user-driven software processes that are presented as a series of graphical user interfaces.
Scrum
An agile software programming method that uses small, self-organizing, cross-functional teams, and iterative, incremental practices.
scrum
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 Rational Team Concert build to locate artifacts for the build, including the load library and object library for an i Project on IBM i.
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.
severity
In software and systems development, a measurement of the importance for a unit of work, for example, critical, high, medium, or low.
sign-on
The procedure by which the user starts working at a workstation.
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.
snapshot
  1. See baseline.
  2. 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.
sprint
See iteration.
SSO
See single sign-on.
staging stream
A copy of a stream hierarchy that acts as a staging area for a new baseline.
star schema
A type of relational database schema that is composed of a set of tables comprising a single, central fact table surrounded by dimension tables.
story
A development work item that defines part of a use case or a specific contribution to the value of the overall product.
storyboard
A sequential illustration of a user scenario that consists of numbered frames on a timeline.
stream
  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.
surrogate key
An artificially created unique identifier column for rows in those tables that have no such natural key column.
suspect link
An indication of change to an object that is part of the chain of links into or out of the current object.
suspend
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.
sync
See synchronize.
synchronization engine
The process that synchronizes data between Rational ClearCase and Rational Team Concert source control.
synchronize (sync)
To add, subtract, or change one feature or artifact to match another. See also reconcile.
system
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 Rational Team Concert, 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 Rational Team Concert.

T

tag
An identifier that groups related artifacts.
task
In agile development, a work item that defines a specific piece of work.
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
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
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 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 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
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.
timeline
An area of activity in a project that typically has its own schedule, deliverables, teams, and process.
toolkit
A set of development tools used to write and test software applications.
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.
transformation model
A model within a fact build that is used to manipulate the acquired source data. For example, the transformation model can merge data from different sources or aggregate data.
translator
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.

U

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.

V

value map
A map that is used to transform source values to a new value during the extraction process in order to standardize common definitions for data from multiple sources.
variable
In Rational Team Concert, a user-defined parameter that can be included in the command and option strings of the translator.
variant
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.
version
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.
view
  1. A subset of information that can be displayed by applying filters or sorting.
  2. 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.

W

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.
widget
  1. 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.
  2. 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.
workflow
A sequence of connected steps that moves an action to completion.
work item
  1. An artifact representing a generalized notion of a development task, such as a task, defect report, or enhancement request.
  2. The smallest component of work to be done in a workflow. It is a collection of both data and references to the system information necessary for processing the data. A work item is transitory; once it has been processed as required, it ceases to exist.
workspace
  1. A context that contains a collection of artifacts that a user with appropriate permission can modify.
  2. 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.
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.

X

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.

Z

zComponent
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 Rational Team Concert components.
zFile
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.
zFolder
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 Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog