My favorites | Sign in
Project Home Downloads Wiki Issues Source
Project Information
Members

The goal of JArchitectureControl is to provide a DSL for architects to specify and control the respect of architecture rules by the code.

The framework analyses code (and maven repository dependencies) :

  • reflection meta data (static analysis) : types, modifiers, annotations
  • byte code meta data (semi-dynamic analysis) : methods invoked, instantiated classes, ...)

The framework visits the code in regards to the specification provided by the architect (naming, properties, relations ships), tags code elements, reports rules violations.

You can find the Need-Solution analysis that led to this project at http://softreves.wordpress.com/2010/02/10/n-s-check-principes-darchitecture/

The following progress have been achieved :

analysis of codeok (maven only)
reflection based analysisok
bytecode based analysisok
specificationok (api, xml and gui)
controlok (gui only)
reportingok (both xml and gui)
testingok: detailed unit test cases for the tricky parts (mainly the bytecode analysis and the control)
used in productionok (used twice for real audits)

Future (short-term) directions may be :

  • extended and automated testing of the bytecode analysis
  • use with eclipse projects instead of maven projects
  • integration as a maven and sonar plugin, generating html reports, uploading configuration files to the server

We need contributors (commiters) !

Powered by Google Project Hosting