Hardware Reference
In-Depth Information
E.
If the task's execution is successful then an important defect is
directed to the CCB, and it waits to be redirected again to the next
task, (it returns to Task 2)
F.
If the task's execution is successful then a less important defect
continues with the next logical task, for instance after
Analysis
it
can be
Resolution
.
G.
If the task was not successfully executed then an important defect is
returned to the CCB for a re-evaluation (Task 2).
H.
If the task was not successfully executed then a less important
defect is handled again by the same task (Task 3)
Task 4.
Once all the tasks of the CCB process have been successfully
carried out, the case of the defect is closed.
Fig. 2.
CCB process model as described in the Quality Manual
Although the analysis is based on four projects, we selected one, project P, to illus-
trate the analysis process. In order to be able to control the development process of
project P and to predict its outcome, the development team collects data about soft-
ware defects. A consultant makes a copy of such database each week. Using this data,
we attempted to retrieve non-trivial information that provides a useful insight into the
CCB process. Having the insight that is based on the real behavior within the process,
the organization could improve its CCB process.
