Category: Modeling

UML is a standard… Which one?

Nice live discussion with @edseidewitz last week, with some good wine! One subject was UML: past, present and future. UML became a standard: what does that mean? Let’s see OMG’s web site: “The Unified Modeling Language™ – UML – is OMG’s most-used specification, and the way the world models not only application structure, behavior, and

Lazy modeling #2: laziness attitude

Say that lazy means not going till something’s end. Lazy modeling means doing models that don’t hold all the material they could carry. Say we talk about MDD(a) (What else? ;D), so we talk about a PIM(b) which describes business/functional/architectural requirements. This PIM holds decisions about a solution to an initial business need that has

Lazy modeling?!

Yesterday I met Rémy Fannader, author of Caminao: a simple but very powerful modelization approach compatible with MDE practices. During a part of the discussion about how wide was the modeling state of art (as wide as at least one track for each artist ;D), popped out a simple illustration question: “May an abstract class

The Sustainable MDA Manifesto: 1st draft

Following recent discussions, with MDA and Executable UML OMG’s initiatives in background, here is my proposal for a Sustainable MDA Manifesto. It’s a first draft, so feel free to contribute. Introduction Even if one want to see them overlapping, modeling and programming are by very nature different activities. The “IT world” does love programming, mainly

MDA/MDD: Model is not code!?

Following my post on round-tripping, a discussion raised again on “what is model?” on Think in models. Here I try to focus on why “model is not code” in an MDA/MDD context. First of all, let’s define the investigation field: MDA/MDD: using models to generate (parts of) code with generators Model (in this context): a formal

MDA/MDD: don’t round-trip!

In MDE life-cycle, round-trip engineering means ability to update a model based on source code reverse modeling. Funny practice: as the source code is issued from this model during the generation step, it’s a kind of “shoe is on the other foot”! More precisely, round-tripping is a way to work indifferently on model or source

Should MDA be the Holly Grail of Agile Manifesto?

OK, I’m in a teasing mood… But let’s take the four Agile Manifesto values and have a look on MDA(*)  through these values. Individuals and interactions over processes and tools The fact is that tools have a huge importance in MDA. Individuals, even interacting well, will not succeed if MDA tools don’t work (modeler and model-to-code

1 2 3