background image
<< the Rational Developer Network | Glossary 2 >>
Glossary
<< the Rational Developer Network | Glossary 2 >>
Glossary
147
activity.
A unit of work that a team member performs.
actor.
Someone or something, outside the system or business, that interacts with the system or business.
analyst.
A person who determines what the system does, specifies and manages requirements, and
represents the user's needs to the development organization.
artifact.
A piece of information that is produced, modified, or used by a process; defines an area of
responsibility; and is subject to version control. There are many types of artifacts, including
requirements, models, model elements, documents, and source code.
automated testing.
A testing technique wherein you use software tools to replace repetitive and
error-prone manual work. Automated testing saves time and enables a reliable, predictable, repeatable,
and accurate process.
baseline.
A consistent set of artifact versions that represent a stable configuration for a project's
components.
class.
In object-oriented analysis and design, a set of objects that share the same responsibilities,
relationships, operations, attributes, and semantics.
component.
A nontrivial, nearly independent, and replaceable part of a system that fulfills a clear
function in the context of a well-defined architecture.
component-based architecture.
A design technique in which a software system is decomposed into
individual components.
configuration management.
Helps teams control their day-to-day management of software
development activities as software is created, modified, built, and delivered. Comprehensive software
configuration management includes version control, workspace management, build management, and
process control to provide better project control and predictability.
developer.
A person who determines how the system works; defines the architecture; and creates,
modifies, tests, and manages the code.
discipline.
The summary of all activities you can go through to produce a particular set of artifacts.
edition.
Sets of Rational Suite tools that are customized for each functional area of a software
development team.
element.
An object that encompasses a set of versions for software project artifacts. Elements can be
either files or directories.
Extended Help.
A powerful feature of Rational Suite that provides links from Rational Suite products to
the Rational Unified Process and any customized information you want to add.
feature creep.
A term used by software development teams to describe the tendency to add unplanned
changes to product features throughout (and often late in) the development process.
forward engineering.
The process of generating code from a Rational Rose visual model. See visual
model.
Glossary