Articles on creating software working on domains models

The code as a source for models

I am taking a rest after some hours of work. I used the javassist library to extract informations from the code of a layer in an enterprise application and use it to build a model to generate the successive layer. I wish I could extract some of the informations using generics but the infamous “Java 1.4 only” constraint plagued me. Anyway to use generics I would need to refactor a little bit the layer I am using as source of my model (aka the “source layer”) and I can’t.

There were moments where I wanted to bang my head so strongly on the wall but after some efforts I managed to extract the informations in the 75% of the cases I needed to. Anyway it is informations that comes for free because it is not expressed purposely to build my model, it is just normal code. The problem is that I can not obtain all the information automatically, I still need a human refinement of the model before I start the generation of the target layer. So I am considering if the information I obtained is worthy because it saved the 75% of the human effort needed to build the complete model or it useless because it is not enough to support automatization.

Mumble, mumble… opinions?

First bites on model driven development on enterprise code (and whispers about…)

Today I kept working on my thesis. I am analyzing an enterprise application spanning across many layers. At this point I am trying to analyze commonality and variability across every layer. My target is to evaluate how difficult it would be to represent the same information as a model and generate code from it. There are portions that could be easily generated as they are now: model driven development would be a suitable solution to generate the exact same code. I think that other layers would require to be thought in a different way, I think that model driven development could achieve to produce code that reachs the same targets but in a different way. Anyway it is a very though and amazing challenge to analyze real, enterprise code and try to model it. It is model driven development, out there in the jungle. I think it can survive and do the job. Will I be wrong?

By the way, if something goes not wrong I would publish my first article on Well, wait and see.

Model driven web devolopment: today and Eclipse DemoCamp

Today I presented some thoughts about state-of-art in model driven development to the professor mentoring me (Marco Torchiano) for my thesis and the company interested in its outputs (Trim). It took me almost two hours to illustrate concrete and philosopical differences across WebRatio, Acceleo (the standalone version, not the one integrated in Eclipse Modelling) and the very rich openArchitectureWare toolsuite. They seemed to be very interested and we decided in which direction focus the next efforts. I am really excited about practical applications of these technologies to concrete projects in the environment of a medium-sized innovative compan such Trim. This company was created with the assistance of Politecnico di Torino and it seems to me that was able to maintain a soul devoted to research and enhancement.

I will have also the opportunity to illustrate some thoughts about my humble efforts to the coming Italian Eclipse DemoCamp. An event organized by RCP-Vision and planned for the 10th of December in Florence. I am really excited about this meeting and also a little bit worried. So it’s better to return working in this project.

Modelling: the quest for resources continues

Another blog about modelling that I want to point out is this one:

It contains posts from Cédric Brun, one of guys working on Acceleo.

In example you can find a reference to his last speech at the Eclipse Summit.


P.s. when I will had garnered some good links I will put all together on a page. Until that tome enjoy the growing list by reading my posts