Download ISTAR Evaluation - Software Engineering Institute

Keystroke Details:
Create a successor configuration item to B01(1), namely B01(2) in the contract
database. This is a copy of B01(1).
Export the modified or newly created transfer items (compilation units) as variants or
successors of their parents, as appropriate.
Keystroke Problems:
See Experiment 1, steps 3, 4, 5 and 6.
Generic Experiment Description:
[Experiment 1, step 10] Create the new baseline.
Mapping Issues/Problems:
What is a baseline in ISTAR?
See Experiment 1, steps 3, 4, 5, and 6.
Mapping/Rationale:
See Experiment 1, steps 3, 4, 5, and 6.
Keystroke Details:
See Experiment 1, steps 3, 4, 5, and 6.
Keystroke Problems:
Generic Experiment Description:
[Experiment 1, step 11.] Build executable of current system.
Mapping Issues/Problems:
How are system builds to be done?
See Experiment 1, step 7.
Mapping/Rationale:
This step was not performed as it repeated functionality already tested.
Keystroke Details:
Keystroke Problems:
Generic Experiment Description:
[Experiment 2, step 1] Experiment setup.
Mapping Issues/Problems:
See Experiment 2, step 3 (below).
Mapping/Rationale:
A new contract, owned by the experimenter, was created to perform steps 3 and 4.
Keystroke Details:
Enter Component Management Tool (CMT) in original contract. Create a configuration item to serve as the contract specification. Assign new contract to self. Commit
action. Leave CMT. Await delivery, which is instantaneous. Accept new contract.
112
CMU/SEI-88-TR-3