background image
<< Glossary 4 | Index >>
Glossary 5
<< Glossary 4 | Index >>
Glossary
151
test case.
A set of test inputs that describe a testable and verifiable behavior in a system, the extent to
which you will test an area of an application, and the results of each test.
test configuration.
The sequence of attributes for potential organizational structures of the system that
you will apply to your test cases.
tester.
A person who creates, manages, and executes tests; ensures that the software meets all its
requirements; and reports the results and verifies fixes.
test input.
Any artifact used to develop a system, and can be used to influence testing.
test plan.
Contains information about the purpose and goals of testing within a project, and the
strategies to be used to implement testing.
Tool Mentor.
Step-by-step instructions on how to use specific Rational tools to perform activities as
described in the Rational Unified Process.
traceability.
The ability to trace one project element to other, related project elements.
Unified Change Management (UCM).
The Rational approach to managing change in software
development, from requirements to release. UCM spans the development lifecycle, defining how to
manage changes to requirements, design models, documentation, components, test cases, and source
code.
Unified Modeling Language (UML).
The industry-standard language for specifying, visualizing,
constructing, and documenting software systems. It simplifies software design, and communication
about the design.
use case.
A sequence of actions a system performs that yields observable results of value to a particular
actor. A use case specification contains the main, alternate, and exception flows.
Unified Software Project Management (USPM).
The Rational approach to managing software projects,
from requirements to release. USPM spans the development lifecycle, focusing on compiling information
to assess status, trends, quality, and other aspects critical to project management and articulation of
progress.
version control.
The process of tracking the revision history of files and directories.
view.
A ClearCase LT object that provides a work area for one or more users to modify source versions.
vision document.
A document that contains a high-level view of the user's or customer's understanding
of the system to be developed.
visual model.
A graphic representation of a system's structure and interrelationships.
workflow.
The sequence of activities performed by roles within a discipline to attain an observable
value.