by Etienne Juliot (noreply@blogger.com) at December 10, 2008 06:09 AM
by Etienne Juliot (noreply@blogger.com) at December 10, 2008 06:09 AM

by Etienne Juliot (noreply@blogger.com) at December 10, 2008 06:09 AM

by Etienne Juliot (noreply@blogger.com) at December 10, 2008 06:09 AM





by Etienne Juliot (noreply@blogger.com) at December 10, 2008 06:09 AM




I also chatted a bit with the whole Eclipse marketing effort !
See you at EclipseCon !
by noreply@blogger.com (Cédric Brun) at November 26, 2008 06:05 AM
I have been within Obeo for almost one month now. As expected, it is crazy, and exciting!
Exciting for several reasons, first because it's a new job with new challenges, and then for the followings:
I like this way of working! It's an ideal way to reconcile family life and
work, we will see it when my son/daughter will be born in February 
As I am an intensive user of Open standards and Open-source softwares such as GNU/Linux, Apache, Tomcat, Java, PostgreSQL, Spring, Eclipse, Ant, Ivy, Hudson,... I think that Open-Source must a win-win model. Thus, I am an active contributor to mailing-list, forum, documentation, experience sharing , bug reporting, or even more source code contribution. It is this approach that led me to interest me to severals Open-Source project like Acceleo, on which I contributed actively and became commiter. This great diving phase in the Open-Source world offers me an opportunity to capitalize in depth experience. As shifting to the Open source world became obvious in my mind, Moving to Obeo was a great opportunity for me!
Since one month, I am pleased to work on a new big Open-Source project : the new UML2 the new UML2 modeler hosted by Eclipse Foundation called Eclipse Papyrus . This big rebuild of Papyrus project (http://papyrusuml.org) is aimed at integrating several contributions on a solid and flexible BackBone. In this project, Standards is another important point, we want support and respect 100% of the OMG standards. In the first sprint to give a first version of code source for the IPZilla incubation process, we focused on implementing the Class Diagram. Thus I discover and start to use the Graphical Modeling Framework (see the first screenshot of this collective work) to improve Class Diagram:

I promise you to communicate about this on this blog!
Yesterday, it was the Acceleo JEE Module Sprint'08. It was an opportunity to meet members of the community and define the roadmap of this module. It was as deep dive meeting, we worked on severals tracks by small team. And you can see the Minute here.
In the coming months, i think meet some famous Eclipse committers like Ed Merks,Tom Schindl,... and participate to important event like Solution Linux, eclipse DemoCamp, maybe Eclipse Summit Europe or EclipseCon ...
And I discovered the offer of Obeo. I known Acceleo since two or three years ago, it's a very cool technology. But it's only a portion of the Iceberg. I enjoyed to discover a big Model Driven Platform called Agility. It can help you to build complete software factories and migration factories. It provide very impressive features!
In conclusion, I just invite you to take a look to Obeo and contact me if you have any question about product portfolio.
by Etienne Juliot (noreply@blogger.com) at June 28, 2008 03:57 PM

by Etienne Juliot (noreply@blogger.com) at June 12, 2008 04:20 PM
I have work some hours on a simple plone2.5 code generator with Acceleo. It is available on the acceleo svn:
svn checkout svn://svn.forge.objectweb.org/svnroot/acceleo/trunk/modules/community/uml21/zope/plone/25/org.acceleo.module.pim.uml21.plone25/trunk
This code generator is not finished, but the way of doing is good enought to start the plone3 one. I would like here to explain the purpose of the Acceleo Generator for Plone3 i want to make.I will first explain the problems i have with ArchgenXML.
What i don’t like in AGX:
What i like in AGX:
For sure i want to keep all that good point for the project. So the overview of what i want:
An other point: generate something only if it save your time. The best example i have is tagged values from AGX, like Searchable = 1. One tagged value for one line of code !A first advice from Cédric Brun (obeo) is to don’t fall in the modelisation of the code itself. For example doing an UML component to generate a zope component (BrowserView, adapter, …). In that case you will lost a lot of time in doing you UML diagram, and be obliged to add stereotypes (adapter, …). So to follow this advice, i have think about the idea of using Component diagram from UML, and i finally don’t want to use it, cause for me an UML component is not equal to a zope component. A UML component can be more seen as an egg. I need to think a bit more about that point, but that could be a great aspect to zope code generation.
Would we need to ‘model’ workflow and generate them according to a state diagram ? Here the point is a bit more complex. In fact you know that you need to make them to explain to your customers the need of specify workflows by UML. But the permission system in zope is specific to it, and the state diagram is not suppose to support this (in AGX we use tagged value one more time). And since we use GenericSetup to specify workflow now, the time saved by doing the state diagram for your workflow is negative. So i think we will just generate the state, but not the permissions associated, that are often explain with the diagram in a documentation. But i would like to generate the test associated with workflows. There were a good conference at Naple on that point.
Next, do we force the use of stereotypes to generate stuff or do we do as with AGX, and so force the use of ’stub’ stereotype to indicate the generator that this class is not a content type to generate. I personally prefer the first option. In that way you can take an existing UML diagram, load the plone3 profile, and said this package is an egg, this class is a ATContentType.
Well, a good demo package to do is the case of the Martin Aspeli ’s book.
Next time i will publish the UML from what i want the martin’s code to be generated.

Today i attended to a conference about Alfresco and MDA by BlueXML. What i have discovered is a set of softwares done with Eclipse and Acceleo to generate an Alfresco project (configure the portal, make content types, …). I have been really interested in the fact they have done a new meta model derivated from UML to model an ECM project and also a GUI modeler associated with this meta-model.
That means the meta-model can also be used for Plone3. For example configuring Plone, by creating group of user, permissions, workflows, … would be stuff available if we use it. But firstly i need to test it to validate the usability of this meta model and of the modeler. All is available at BlueXML home site.


by noreply@blogger.com (Cerdicus) at December 11, 2007 07:30 AM

by noreply@blogger.com (Cerdicus) at December 10, 2007 07:55 AM
by Etienne Juliot (noreply@blogger.com) at September 07, 2007 11:26 AM
I will start this blog by debating on differences between MDA (Model Driven Architecture) en MDSD (Model Driven Software Development) approaches. One could see MDSD as a deprecated version of the standard MDA. But another will see that MDSD has a wider scope than MDA. So I will try to explain what MDSD embraces and what's it is useful for.
First, let's compare what we've got on both sides. For MDA :
Standardized by the OMG since 1999
Based on XMI, MOC, OCL, UML...
Aims at automating all transformations between models to code, suppressing the coding part
Driven by the Y cycle and CIMs, PIMs, PSMs and PDMs
Tries to define standard meta-models shared across industry domains
For MDSD :
Based on the ideas brought by MDA
Not bound to its standards : can be any meta-model like DSLs, not only UML and profiles
Try to promote customized DSLs answering to each need, not assuming that every body will have the same needs on a given domain
Use models as abstraction and still leave a place for development tasks
Defines its own ideas of PIMs and PDMs depending on projects or needs contexts
From the use I can see in my job,the MDA standard is more something made for the big players in the industry, whereas MDSD is a more flexible approach that can be used by a larger group of users, less attached to standards and with smaller scale needs.
To conclude, I will just say that MDSD is a pragmatic way of using MDA concepts. With the new wave of tools such as Eclipse, EMF, GMF, Acceleo..., you can use these kind of approaches on large scale projects and I would recommend anyone to have a deep look into it as it really helps to cut down software development costs !
And the quickest way to do that is to try it using Acceleo I think !
by noreply@blogger.com (Stephane LACRAMPE) at May 16, 2007 09:10 AM
by Etienne Juliot (noreply@blogger.com) at May 14, 2007 04:34 PM
by Etienne Juliot (noreply@blogger.com) at May 04, 2007 01:06 PM
by Etienne Juliot (noreply@blogger.com) at April 20, 2007 04:54 PM
by Etienne Juliot (noreply@blogger.com) at April 20, 2007 04:46 PM
by Etienne Juliot (noreply@blogger.com) at June 14, 2004 01:10 PM
by Etienne Juliot (noreply@blogger.com) at June 04, 2004 05:13 PM
by Etienne Juliot (noreply@blogger.com) at June 04, 2004 05:04 PM
by Etienne Juliot (noreply@blogger.com) at May 12, 2004 05:01 PM
Last updated:
January 06, 2009 03:00 AM
All times are UTC.