Visualization change control procedure

Instructor: George Lukas

Developed by: Zaixia Zhang

Date: Oct. 21, 2003

Version 1

1. Work products go to technical review to determine whether initial development work on it can be declared complete.
2. Work products are submitted to “change board” (here it means Professor Lukas and all team members) when initial development is complete.
3. Work products are placed under “revision control”. In our case, we plan to use SourceJammer.
4. Following changes to products are treated systematically:

· Team member or author gives the change proposals (oral or written) to the product.

· Supervisor identifies parties that might be affected by the change and delivers the change proposals to those concerned members for review.

· The concerned parties assess the change impact to their own parties from their individual viewpoints.

· Supervisor combines these assessments and prioritizes the change proposals and notifies all concerned parties about how the change proposal was resolved.