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

From application workflow to user journey

Simpler architectural models

TOGAF spirit

Get rid of Pacbase (and CASE tools) #1

First of all, the views expressed here are mine and do not necessarily reflect the views of my past, current and future employers. Situation: A Company uses a CASE tool (Computer Aided Software Environment) to develop and maintain part of its application portfolio. For some reasons, the company wants to get rid of this CASE tool. One

MDE shuffled again

Some background (click to show) [show][hide] Almost nine months after my last post on this blog. What happened? I got a baby! She’s ten months old now and she has taken a big place in my “spare life”. Also I started others blogs. So, I take this long break as an opportunity to think again

Agile & Modeling new way of life!

Nice title, isn’t it? I’d like to share the idea that we can associate agile project management and software development  practices (two different things!) to build sustainable software. In doing this, the sustainable artifacts would be source code AND analysis and design models (and maybe code generation rules if used for this purpose). The idea

Business logic’s paradox: the barber’s story

Inspired by Model practice’s last posts I will try to illustrate a business logic’s paradox on the barber’s paradox taken as a business rule ;) The barber’s paradox: “The barber shaves only those men in town who do not shave themselves! Who shaves the barber?”. The first sentence is the business rule: “the barber shaves

Successful MDA’s drawbacks… A true story #2

Facts This (other) company, uses an MDA/MDD life-cycle since many years. It works fine but… A first problem, funny if you think of it, is that MDA works too well: developers who work on MDA projects for a while, say 3 years, lost part of their ability to be a “standard” developer. Say they develop

True story of a MDA paradox

Based on a true return of experience. Facts This company has built an efficient MDA/MDD life-cycle based on UML and a robust MDE tooling. They outsource part of their new applications development. They offer to their IT services providers to use the company’s MDA tooling, and even offer to educate them and provide MDA expertise

I read the MDA Guide v 1.0.1

Just reading the title of this post you know I’m kidding. This founding OMG’s MDA guide is unreadable by a human being ;D. However, even if skipping a lot of sections, it’s interesting enough to worth reading it as it proposes definitions for terms very much used in the MDE community: MDA, CIM, PIM, PSM,

1 2 3 4 5