Filter
Top Products
f. If there are tables and/or map groups used by the program, the generator
determines whether there is already a build tree for them. If not, initial build trees
are added for them using the program’s OVR part.
g. TeamConnection re-examines the build tree of the EZEPREP collector and
determines that new build events have been added to the build scope for
preparation of the generation outputs, and possibly for generation and
preparation of tables and map groups. Build events are started to complete the
preparation of generation outputs, and generation and preparation of tables and
map groups if necessary.
Note: See the VisualAge Generator
Generator’s Guide
for greater detail on this
process.
3. In TeamConnection (change control):
v A project administrator completes the fix record(s) for the feature f1 and adds the
work area wa1 to a system test driver. Eventually the driver is committed to the
release and the feature is completed.
Making a change to a member
1. In TeamConnection:
a. Defect d1 is created and accepted in TeamConnection
b. Work area wa2 is created for the implementation of the defect d1.
2. In ENVY:
a. An application manager creates new edition of an application that requires a
change.
b. A developer makes a change to one or more parts.
c. The class developer of the changed parts versions the class, the class owner
releases the class into the new edition of the application, and the application
manager versions the application. If more than one defect is in progress, the
class owner must release only the versions that apply for defect d1.
d. The configuration map owner opens a new edition of the configuration map
used to generate the program being changed, and releases the new application
version into the configuration map. The configuration map owner versions the
configuration map.
e. The administrator uses the ENVY/Manager-TeamConnection Bridge to put the
configuration map back into the work area wa2 for defect d1.
3. In TeamConnection (build function):
a. Build administrator builds the program(s) affected by the change. This can be
done by selecting the preparation collector for each program and requesting a
build, or by selecting a collector for a subsystem, and building the subsystem
collector. Only programs, tables, or map group affected by the changes to proxy
members will be rebuilt.
b. The generation process continues as it did for the initial build (see “Build
generation” on page 263 for details), except that there should be no need to add
new build trees unless a new table or map group was added to a program being
built
Appendix F. Enabling and Using the ENVY/Manager-TeamConnection Bridge 265