Aggregated enterprise architecture wisdom
There are a couple of avoidable behaviors that architects sometimes adopt that generally annoy project teams.
The first is “nick picking” – identifying an apparent issue and then drilling down into it to minute detail. It …
So far the articles 1, 2 and 3 in the series have addressed the SOA governance aspects such as, understanding the context, defining the objectives and parameters, understanding various components such as timing and artefacts to govern, roles and respo…
A recent conversation with a colleague delved into the complicated world of new technology decisions. At every organization I’ve been at, this has been a source of contention between four major groups: Enterprise Architects, Domain Architects, Development Teams, and Engineering Teams. I specifically listed Enterprise and Domain Architects separately, because I’ve seen contention between those […]
In part II and III of this series we discussed the Common Information and Canonical Models. Because MDM is a business project we need to establish of a common set of models that can be referenced independent of the technical infrastructure or patterns we plan on using. Now it is time to introduce the Operating […]