Complexity Map Development
Feature and fix backlog
The following features and refactorings are considered, see below for a votable priority list.
General
- move more algorithms to domain-objects (in progress)
- clean separation of all architectural layers (in progress)
- polish Javadoc (ongoing)
- add SpringFramework's dependency injection to wire components
- bring Maven-2 project definition up to standards
- package CM as Eclipse-plugin (help welcome)
GUI
- remove all code/finding-related references from the GUI making the CM-GUI a generic layered treemap browser (in progress)
- extend full-frame version of CM to include working menu's and proper plastic layout (incl. icons)
- fix scroll-pane for summary layer selection
- fix for very long namespace-names
- add more extensive filter/aggregation options
- generalize available colorschemes
Data input and output
- load client-references via unshared configuration (in progress)
- review/validate and document core interfaces
- config-related: lazy-load PMD and Checkstyle metrics
- more sources to be added (e.g. Macker, JDepend)
- support event-driven modification of the object model (and the data tree)
- remove need to first parse a datatree before findings/remarks can be positioned
Other
- save complexity torque with project metadata for later analysis (e.g. cross-reference, ComplexityLine)
- visually compare two complexity maps
Vote for items on the backlog
Completed
The following features/fixes have been implemented.
General
- refactor application, turning data-structure into OO-model (done)
- package CM application standaloen - being able to analyse code-trees (done)
GUI
Data input and output
- parse data tree from XML-namespaces in XML-Schema and WSDL documents (done)
- parse data tree from Confluence via SOAP-api (done)
Other
