So you are a java programmer, you have a data model (a Class Diagram) and you want to implement your system?
Get your State Machines sorted, then you can specify a system to xUmlCompiler, and validate, test and execute it.
The result is an executable system so that we satisfy to a fair degree that "the model is the code".
Executable UML at Wikipedia. Executable UML (Mellor & Balcer, 2002) at Google Books
In detail, a system specified in java code using helper methods provided by xUmlCompiler is used to generate java persistence annotated (JPA) classes. Guice is used to inject action language (java) for methods and events. xUmlCompiler offers a swing viewer for the system and generates persistence.xml resources for quick testing turnaround.
Overview, Guide, QuickStart, Plan
2010 Feb 17Two example projects (two artifacts each) and maven parent build in svn 2010 Feb 11Uploaded sample Eclipse project 2010 Feb 10Converted build from Ant to Maven 2009 Mar 27Fixed generated jsp pages 2009 Feb 10All associations are lazy fetch 2009 Jan 13Generate shared interface implemented by members of a specialization group 2008 Sep 06Mutual exclusion enforced on specializations 2008 Sep 04Multiple generalizations enabled 2008 July 02Specialization needs work to ensure a generalization is abstract and to allow multiple generalizations 2008 July 01Improved Viewer Specializations, ant task to generate diagrams as jpeg 2008 June 25State Machine Viewer is in 2008 June 23Uploaded first download. Included jar downloads all dependencies when run via java -jar. 2008 June 22Sorted out download of Ecore dependencies via Maven 2008 June 18Viewer now uses ecore data model generated classes for serialization/deserialization 2008 June 11Simple system wiki page done 2008 June 10Documenting a simpler system to demonstrate the complete development cycle (Shop can wait till later) 2008 May 29Documenting a more interesting Shop system 2008 May 22First commit