Sharing the Solution Domain Taxonomy

Sometimes, Enterprise Architecture efforts fail.  This is no surprise to folks in the EA business.  This failure occurred slowly, back in 2007 and 2008.  But it did occur.  It took me a while to realize it.  I had developed a method useful for Application Portfolio Management as well as for Service Oriented Architecture called “Solution…


Placing Architecture Properly into Scrum Processes

As I’m about to complete my share of a longer engagement on using Lean principles to improve the processes at an online services firm, it occurred to me that the efforts we undertook to properly embed Architecture practices into their Scrum process were novel.  I haven’t seen much written about how to do this in…


Linthicum’s Challenge: Where does SOA stop and EA start?

Tom Graves, David Linthicum, and I recently got into an interesting discussion on Twitter as the result of a, EBiz blog post by David, where he makes the statement that Good SOA is the same as Good EA.  (See ‘Do SOA and enterprise architecture now mean the same thing?’ Yes, they do’).  Both Tom and…


Service Oriented Architecture Conceptual Model

Almost two years ago, I described some of the key concepts of service oriented architecture, including the distinction between a canonical model and a canonical message schema.  Since that time, I worked on a wide array of models, including Microsoft IT’s Common Conceptual Model.  That model (CCM for short) is the metamodel for IT concepts…


The cost of “SOA-fication”

No, Virginia, there is no SOA Santa Clause.  SOA is not free. That said, if I’m changing a system to meet new needs, and I’m substantially refactoring a section of the code to deliver to those needs, SOA doesn’t have to be wildly expensive either. The myth of “expensive SOA” is just that: a myth. …


SOA Optimistic Data Synchronization considered harmful

Let’s say that you have two systems: Adipose and BellyFat.  They both need the same information.  Adipose handles customer transactions, so it needs information about customers.  BellyFat handles the long-term management of customer information, like what products they have purchased and what rights they own.  It also needs information about customers. How do we keep…


Understanding SOBA

Just ran across, quite by accident, a blog post from last spring from Johan den Haan on the "Architectural requirements for Service Oriented Business Applications."  This is a clear, consistent, well described web post on SOA and service architecture.  I recommend it highly.


Creating a distinction between business services and SOA services

I’m always a bit dismayed when I hear the following terms mixed up, or combined: SOA service and business service.  In my mind, these things are different.  In one sense, they are related, but indirectly. A business service is a function (or capability) of the business that is offered to one or more customers.  Those…


Understanding Governance as Decision Rights

Todd Biske, whom I respect for his writings on SOA, seemed to miss the mark in his recent blog post about SOA Governance and Decision Rights.  In that post, he said: if you focus on education, you can allow individual teams to make decisions, because you’ve given them the necessary information to make the right…


Malik’s Laws of Service Oriented Architecture

No one but you will build the services you need in time for you to use them If you build a service that no one else asked for, you will have built it for yourself If you build a service for yourself,  you will optimize it for your own use It is therefore the optimal…