ITK/Release 4/Modularization: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
2) Organize the ~2,330 files into conceptual cohesive groups. | 2) Organize the ~2,330 files into conceptual cohesive groups. | ||
3) Test and label each group according to measures of quality control : Code coverage, correctness, style, | 3) Test and label each group according to measures of quality control : | ||
Code coverage, correctness, style, dynamic testing, documentation... | |||
4) Raise the quality bar for critical components. | 4) Raise the quality bar for critical components. | ||
For example, the itkObject must have 100% code coverage, while we could live with the Blox classes having 30%. | |||
5) Maintain that level of quality as more code is added to the toolkit. | 5) Maintain that level of quality as more code is added to the toolkit. | ||
Revision as of 22:56, 5 February 2011
Goals
1) Find / label / remove the trash in ITK.
2) Organize the ~2,330 files into conceptual cohesive groups.
3) Test and label each group according to measures of quality control : Code coverage, correctness, style, dynamic testing, documentation...
4) Raise the quality bar for critical components. For example, the itkObject must have 100% code coverage, while we could live with the Blox classes having 30%.
5) Maintain that level of quality as more code is added to the toolkit.
6) Facilitate the use of Add-ons with ITK without having to include them in the toolkit.
Latest Progress
What itk-developers need to know about contributing to modularized ITK?
What users need to know about using modularized ITK?
Development history
Initial Goals Steps and tools
Prototype [Iowa Meeting] Prototype
TCon 2010-12-03
