Download ISTAR Evaluation - Software Engineering Institute

Mapping Issues/Problems:
Mapping/Rationale:
Define a checklist for later use.
Keystroke Details:
As qa, accept contract from mpm as quality assurance work. WORKBENCH, QA
MANAGEMENT, QA MANAGEMENT, BUILD work area release. SELECT release. CREATE a
form note with all checks applicable to a release. Include a few criteria (type C) and
one reference (type R) to another form. No need to EDIT since the CREATE will have
all the correct fields. Export release work area to release(1)+note(1). Framework,
CONFIGURATION, COMPONENT, move over to release(1), change, ACCESS RIGHTS, ACCESS - LOG. FUNCTIONS, CREATE NEW CI release(qa1,1), move over to it, change, MERGE
INTO, from release(1), select note(1), ACCESS RIGHTS, ACCESS - LOG. EXIT. LOGOUT.
Keystroke Problems:
It was difficult to find in the documentation how to create new checks correctly. The
easiest method is to go to the ID field and just CR to the next check.
Generic Experiment Description:
[QA2] [deleted] Refines plan and sends it back to manager.
[QA3] [deleted] Receives two (independent) fixes from Team 2. Performs acceptance
test on UI_SM. Integrates this change into the system.
[QA4] [deleted] Receives one fix from Team 3. Performs test on UI_VT. Integrates
these changes into the subsystem.
Mapping Issues/Problems:
Mapping/Rationale:
These steps are not performed in the ISTAR PM experiment.
[QA2] There is no plan refinement step since ISTAR does not support the sending
back of comments that are to be integrated into higher-level plans with environment
assistance.
[QA3] There is no Team 2 in the ISTAR PM experiment.
[QA4] There is no Team 3 in the ISTAR PM experiment.
Keystroke Details:
Keystroke Problems:
Generic Experiment Description:
[T1-13] Complete UI-CLI. Prepare for QA review. Send to whoever handles delivery
to qa (may be self or manager). Notify manager.
Mapping Issues/Problems:
How are un-planned, child-to-child interactions handled?
The first child can DELIVER on the assignment just to notify the superior and then
ask the peer externally to RETRIEVE the CI.
+Keeps the superior informed while avoiding the possibility of passing much
technical information needlessly.
146
CMU/SEI-88-TR-3