Under the pavement

@pbmobi asserts that “Infrastructure Architecture is the foundation for #entarch, not the other way round”. This suggestion draws on a book review of “The Works: Anatomy of a City”, in which the reviewer suggests that the tubes, wires and pipes und…

Under the pavement

@pbmobi asserts that “Infrastructure Architecture is the foundation for #entarch, not the other way round”. This suggestion draws on a book review of “The Works: Anatomy of a City”, in which the reviewer suggests that the tubes, wires and pipes und…

Data-architecture 101 and the naming-problem

The echoes of the ‘naming-problem‘ around business-architecture and the like continue to rumble on, this time via another happy Twitter-exchange with Ron Tolido: rtolido: @tetradian just show me the non-IT people that invented #entarch and / or #bizarch tetradian: @rtolido we’re in a circular-definition here: what you call #entarch or #bizarch is whatever was ‘invented’ […]

Competence, non-competence and incompetence

One of the key reasons why I’m so vehemently against any-centrism and suchlike revolves around the question of competence – or, more usually, the lack of it. Competence is where someone knows what they’re doing, and does it. And, oddly, often don’t bother to say that they’re competent – perhaps because they don’t need to […]

Configuring the EA approach

I often don’t like when EA discussions take the route into meta concepts. Enterprise architects – as the abstract thinkers they often are – have a tendency to discuss meta concepts. “What does the meta model of that method look like?”, “What do you mean when you say capability?”, “How do you define enterprise architecture?”. […]