Filter
Top Products
Chapter 5. Working with no component or release processes
To illustrate how to work with objects in a release that does not follow a tracking
process or component processes, this chapter follows an example of a programming
team that is developing the control systems for a robot. They are working in a family
called robot.
Instructions for performing the task are given for both the graphical user interface (GUI)
and the command line interface (Command).
This chapter illustrates two scenarios: working in serial development and working in
concurrent development. Working in
serial development
means that after you check out
a part, TeamConnection locks the part so that it cannot be updated by anyone else.
Compare this to
concurrent development
, in which more than one person can
simultaneously update the same part.
The following table directs you to the scenario you need:
For this scenario, Go to this
page.
Working in serial development 51
Working in concurrent development 70
Working in serial development
Alex is one of the programmers working on the robot application within a release called
robot_control. The release does not follow a tracking process, and the release supports
serial development. Even though the release does not follow a tracking process, defects
are opened when problems are found.
This example assumes that the parts that Alex will work with have already been created
in the release, and the build tree has been established. The build tree shows the
hierarchy of objects that take part in the build of an application. It identifies parts as
inputs, outputs, and dependencies of a build. For more information about build trees,
see “Working with a build tree” on page 133 or “Creating the build tree for the
application” on page 184.
This example also assumes that the family named robot has been defined in the
TC_FAMILY environment variable. Because Alex accesses information in several
releases, he has not defined the release named robot_control. Therefore, he must
explicitly identify the release when performing TeamConnection actions, but not the
family.
A fellow team member, Carol, has discovered that the robot’s aperture is not working
correctly. To address this problem, she opens a defect. To fix the problem, Alex needs
© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 51