ITK/Release 4/Modularization: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(→Issues) |
No edit summary |
||
| Line 1: | Line 1: | ||
== Goals == | == 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 == | |||
[[ITK_Release_4/Modularization/Modulizer|How to get modularized ITK?]] | [[ITK_Release_4/Modularization/Modulizer|How to get modularized ITK?]] | ||
| Line 14: | Line 26: | ||
What '''users''' need to know about using modularized ITK? | What '''users''' need to know about using modularized ITK? | ||
= | == Development history== | ||
Initial Prototype [Iowa Meeting] [[ITK_Release_4/Modularization/Prototype|Prototype]] | |||
Initial Goals [[ITK_Release_4/Modularization/Purposes|Steps and tools]] | |||
Prototype [Iowa Meeting] [[ITK_Release_4/Modularization/Prototype|Prototype]] | |||
TCon [[ITK_Release_4/Modularization/Tcon-2010-12-03|2010-12-03]] | TCon [[ITK_Release_4/Modularization/Tcon-2010-12-03|2010-12-03]] | ||
Revision as of 22:55, 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
