2011 Winter Project Week: Slicer4-ITK4 Continuous Integration
- Bill Lorensen
- Hans - Iowa
- Luis - Kitware
Identify API changes in ITK4 that cause compilation or run-time errors in Slicer4.
Slicer4 development is underway and ITK version 4 has recently started. One of the goals of ITK 4 is too improve and cleanup the application programming interface (API). Although every attempt is being made to keep the API compatible with ITK 3.x. However, since ITKv4 will be a new major release, there are opportunities to remove antiquated code and repair long standing design defects.
The API changes may be planned or accidental. This project will establish mechanisms to discover, resolve and document API issues.
This project will use the DMAIC methodology of the Six Sigma management process to "Define", "Measure", "Analyze", "Improve" and "Control" compiler warnings in Slicer3. This project will concentrate on warnings produced by the GNU gcc 4.3 compiler. Similar approaches can be applied to other Slicer3 compilers.
The basic methodology (from Wikipedia) consists of the following five steps:
- Define process goals that are consistent with customer demands and the NA-MIC's strategy.
- Measure key aspects of the current process and collect relevant data.
- Analyze the data to verify cause-and-effect relationships. Determine what the relationships are, and attempt to ensure that all factors have been considered.
- Improve or optimize the process.
- Control to ensure that any deviations from target are corrected before they result in defects. Set up pilot runs to establish software quality, move on to production, set up control mechanisms and continuously monitor the process.
The goal is to provide a mechanism to identify incompatible Slicer4/ITK4 API changes.
A baseline dashboard was created on December 27, 2010. There mere 605 compilation errors.
A description of each API incompatibility and how to address it will be provided.