The Return On Investment (ROI) of Enterprise Architecture (EA)

From application workflow to user journey

Simpler architectural models

TOGAF spirit

What is the focus of analysis: problem or solution?

This post is my shifted comment on Rafael’s post & discussion. Rafael talks about analysis vs design in the software life-cycle, where problem is the requirement and solution the software to build. First of all, IT or not, any answer makes sense as an answer only if it answers a question. So, a solution is

Modeling/Programming: Art or Science?

The story begins with two quotes from Paul Valéry’s work I put on Twitter: “What is simple is always false. What is not simple is useless” (1) “There is science for simple matters and art for complicated matters” (2) My conclusion is: it’s difficult to combine art of modeling with science of programming. It’s the

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

Only 4% of IT projects benefit from a double dream team effect!

I was debating yesterday about how a small, smart, agile, efficient, architecture minded developers team could achieve an IT project development in time, with high quality results and smiling end users. That is true. They can perform this better than a very much bigger team of less efficient developers. Not a surprise! But what about

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

1 2 3 4 5