KISTERS develops several products in parallel processes and mostly referred to Bugzilla as a central development process. To achieve Target Milestone (Product Version), a number of cases will be reported to the Bugzilla (Open Source which has been tweaked for the special case in KISTERS) which contributed from internal and external customers. The cases could be maintenance activities, enhancement and new requirements. To resolve the cases, assignee (a person in charge for solving the case mostly are developers and QA guys) will be assigned and the estimation works will be calculated. Due to evolution (i.e. code branching and integration) and product characteristics (active development vs long cycle), the cases are mostly dependency and the rise of complex problem such as prioritization tasks, redundant workload, no time estimation, etc. In order to avoid the problem, the bugzilla case must be investigated in order to visualize the case and task dependencies that perhaps the root problem of late release i.e. conflicts, deadlock etc. Although the Bugzilla has provide a graph (for visualizing the blocking case and case dependency tree) and a Gantt chart (for estimating timeline and progress work), there is no mechanism to detect the root problem mentioned previously. By extracting data from Bugzilla database, it is believed that the propose tools could resolve the problem as an early indicator before the assigner assign the case to assignee with proper analysis of release cycle.

The tasks that need to be performed by the student are:

1. Identification of conflict points or different conflict cases that could contribute to unmanageable tasks in Bugzilla with a cooperation partner.
2. Specifying the conflict problems into a model.
3. Finding a strategic task coordination to organize the tasks manageable or to resolve the cases ahead.
4. Evaluate the work by performing the case study with cooperation partner.