IBM SC34-4499-03 States of TeamConnection objects, Component subprocesses, Release subprocesses

Chapter 4. The states of TeamConnection objects

The actions that you can perform on certain TeamConnection objects are controlled by two factors:

vThe process followed by the component and by the release

vThe current state of the object

Certain TeamConnection objects follow certain states through their life cycle. An instance where an object might not follow all the possible states is when it moves through the states de®ned in the subprocesses of the component and the release. The following table brie¯y lists the component and release subprocesses. For more information on component and release subprocesses, refer to the Administrator's Guide.

Component subprocesses

vdsrDefect - Design, size, and review ®xes to be made for defects

vverifyDefect - Verify that defect ®xes work

vdsrFeature - Design, size, and review changes to be made for features

vverifyFeature - Verify that feature changes work

Release subprocesses

vtrack - Relate all part changes to a speci®c defect or feature and a speci®c release

vapproval - Require all changes to be approved before incorporating them into a release

v®x - Use ®x records to ensure that all required changes are made

vdriver - Use drivers to integrate changes into a release

vtest - Require all changes to be tested before they are integrated into the release

This chapter explains the possible states of certain TeamConnection objects and how objects are moved from one state to the next. It also explains how component and release subprocesses affect the ¯ow of states. For a diagram showing the ¯ow of states, refer to the poster Staying on Track with TeamConnection Processes.

Defects and features

Use defects to report problem information; use features to record information about proposed design changes. After you open defect or feature, TeamConnection tracks the progress of the defect or feature through various states. Defects and features are tracked according to the processes followed by the release and component that they are assigned to. The possible states for defects and features are:

Open state

When you open a defect or feature, it is in the open state and you are considered the originator.

You assign the defect or feature to a component. The owner of this component becomes the feature or defect owner and is responsible for managing its

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 41