Projects

openArchitectureWare

openArchitectureWare (oAW) is a modular MDA/MDD generator framework implemented in Java(TM). It supports parsing of arbitrary models, and a language family to check and transform models as well as generate code based on them. Supporting editors are based on the Eclipse platform. OAW has strong ... [More] support for EMF (Eclipse Modelling Framework) based models but can work with other models, too. [Less]

Eclipse Modeling Workflow Engine

claimed by Eclipse Foundation

The Modeling Workflow Engine is an extensible framework for the integration and orchestration of model processing workflows. It comes with some basic components for and provides API for others to provide their own model processing tools.

Eclipse Modeling Project

The Eclipse Modeling Project focuses on the evolution and promotion of model-based development technologies within the Eclipse community by providing a unified set of modeling frameworks, tooling, and standards implementations.

emf-observables

emf.observables allows you to use a in emf modeled data model for a RCP application with databinding. From an .genmodel file you can generate next to your .model plugin a separate .observables plugin which contains wrapper classes to your emf model classes. Using this classes you can - easily build ... [More] your memory based data model using a builder interface instead of the PackageFactory classes - access IObservable object wrappers in a type safe way. [Less]

Olympos

Olympos is an holistic MDA/MDD approach to projects. It allows to create Web (PHP, J2EE), Desktop (c#) and Mobile applications (.NET, J2ME) from a UML model. Features a Web 2.0 IDE, a generator based on openArchitectureWare and several cartridges.

GenGMF

GenGMF is a model driven generator framework for the Eclipse GMF graph and map models. It will generate large models from a small template model for you. It is based on Eclipse GMF, AspectJ and openArchitectureWare.

toools

toools is a Java based application stack to build solid web based applications. toools is utilizing GWT (Google Web Toolkit), spring, EJB3 (toplink essentials), JBoss and tomcat and comes as Netbeans project. You are free to choose a RDBMS. RELEASE 1.0 (scheduled for 10/01/2008) toools will be a ... [More] full featured CRUD stack which allows rapid web application development based on a EJB3 domain model. toools will integrate with AndroMDA to support the model driven architecture (MDA) paradigm. RELEASE 1.1 (scheduled for 01/01/2009) toools components will be generated based on XMI compliant UML models. support of class (EJB3) modeling (domain modeling). RELEASE 1.2 (scheduled for 03/01/2009) support of activity modelling (process modeling). current state of development: 0.5 checkout DemoAppSetup DeploySetup check out the demo application ... [Less]

agreementdsl

This project hosts the code which implements the Agreement DSL thought up by Martin Fowler. This implementation is discussed in an article in the dutch magazine Java Magazine.

dslvariantmanagement

Product line engineering and model driven development are two approaches to software development that are becoming more and more important. The combination of the two approaches is promising. There are various ways of how those two approaches can be combined. One way is to use feature modeling to ... [More] define variants of models created with domain specific languages. The tools in this project are in implementation of this approach. For textual DSLs built with openArchitectureWare 4.3.1 Xtext this project contains tools to define variability. This means, that feature dependencies can be annotated to arbitrary grammar elements. A model processor removes all the elements from the model after it has been loaded whose features are not selected in the current configuration. Tool integration exists with pure::variants. Code completion from the DSL into the feature model is implemented, as well as traceability from the feature back to the models. For completeness this project also contains a text processor that can customize text files according to features selections. The download page contains documentation of how these tools should be used. To understand the background, please refer to the following two documents. The first one explains the general approach of using textual DSLs for architecture description. The second one specifically addresses variability. http://www.voelter.de/data/articles/ArchitectureAsLanguage-PDF.pdf http://www.voelter.de/data/articles/ArchitectureAsLanguage-Part2-PDF.pdf [Less]

iphonical

iPhonicalModel Driven Software Development for the iPhoneThe iPhonical project provides a rapid prototyping development process as well as an Eclipse-Plugin (based on Xtext) that offers a simple Domain Specific Language (iPhonical DSL) for describing iPhone applications. The created models based on ... [More] this DSL are the input for an openArchitectureWare code generator which creates various ObjectiveC artifacts in order to accelerate iPhone development and improve the quality of the ObjectiveC code by replacing a lot of glue code with generated code. Generated artifacts are things like: Entity classes (Domain Objects) optionally Object Relational Mapper for SQLite3 (DAO Layer) Transformation - from and to JSON format View Controllers with basic outlet attributes Simple NIB Files corresponding to the view controllers JSR-311 HTTP/JSON Rest based Web Services (iPhone Client and Server using JBoss RESTEasy) These things are generated in a layered architectural style that should reduce the need to manipulate any generated code. Using Categories and Subclasses should be all that's needed to program the (manual) rest of the application. The generated code has dependencies to the following open source projects which provide some excellent APIs to use (see links for more info): FMDatabase JSON-Framework JBoss RESTEasy Getting startedsee here Right now it is beneficial if you are experienced with XText and openArchitectureWare development until further information/tutorials are provided. Anyway you can try the example an you can adapt the scripts to your own purposes. Usage examples for iphonical DSL: iphonicalModel iDriveLog { ... entity Car { String name; String number; Integer km; JourneyEntry * journeys; }; entity JourneyEntry { Location startLocation; Location endLocation; String comment; Integer startKm; Integer endKm; Car car; Driver driver; Reason reason; }; entity CarDataResponse { String creationDate; Car car; Location location; JourneyEntry journey; Driver driver; }; viewController Root { ui Label myLabel; ui Textfield myTextfield; action myAction; }; restService iDriveLogService "/idrivelogservice" { baseUrl "http://localhost:8080/iDriveLogRESTWebServices"; get data "/data" response:CarDataResponse; }; }Usage examples for generated code: //Persistence and JSON Marshalling NSLog(@"Opened database ... "); [db open]; [db setShouldCacheStatements:YES]; [db beginTransaction]; // Create and Save car CarDAO *carDAO = [[CarDAO alloc] initWithDBManager:db]; NSLog(@"CarDAO initialized ..."); Car *car = [[Car alloc] init]; car.km = [[NSNumber alloc] initWithInt:10]; car.name = @"BMW 7er"; car.number = @"KA-IT 310"; car = [carDAO save:car]; NSLog(@"Saved Cars! %@ with idnr: %i", car, car.idnr); car = [carDAO findCarByIdnr:car.idnr]; NSLog(@"Found Car! %@ with idnr: %i", car, car.idnr); NSLog(@"To JSON: %@",[car asJSON]); NSLog(@"From JSON: %@", [[car initWithJSON:[car asJSON]] name]); [db commit]; [db close]; ... // WebService usage example - (int ) webservicecall { CarDataResponse *response = [IDriveLogService getData]; NSLog(@"Marshalled: %@", [response asJSON]); return 0; }There is also a Google Group for iPhonical: http://groups.google.de/group/iphonical If you have any questions about the project you can contact me under: wolfgang.frank AT arconsis.com [Less]