Architecture, Data and Intelligence

@ pbmobi asserts that "Infrastructure Architecture is the foundation for # entarch , not the other way round". This suggestion ...

@ JohanDenHaan pointed me at a couple of articles by Bill Poole Layered Service Models are Bad Layered Service Models are Bad (continued) B...

This post starts by talking about the value proposition of Web 2.0, and then makes some more general points about the distribution of value ...

Nick Malik asks whether a common vocabulary is a blessing or curse . Who benefits from a common vocabulary - whose agenda is it? IT architec...

In my previous post Does ERP matter? I discussed the business requirements for enterprise resource planning - a management style involving ...

In a post entitled Your SOA is JABOWS , Microsoft's Nick Malik identifies what he calls the SOA Sweet Spot, which represents the interse...

Martin Geddes draws some interesting parallels between the telecom system/infrastructure and the UK railway system/infrastructure, and discu...

Day 2 of the SPARK workshop was an attempt to develop frameworks that encapsulated the architectural response to the challenges identified i...

Martin Fowler reports on a workshop in which people ( a good group of people, [but] it was hardly a definitive source of enterprise develop...

I have just come across an interesting talk by Shai Agassi of SAP, entitled Achieving Enterprise Agility. Slides ( pdf ) from Accelerating...

Adam Brown from John McAslan and Partners gave a talk recently about his restoration/renovation work with Swiss Cottage Library. Dan Hill h...

A business or value chain is composed in a geometric structure. (In the past we have often called this structure an architecture, but this w...

With a layered picture of SOA, it is clear that each layer undergoes a lifecycle – but at different cycle times. Some of the layers have a r...