SOA Governance
by
Charlie Bess
For years - yes literally years - I've been talking to EDS internal groups and clients about the different governance that is required to effectively perform Service Oriented Architectures.
This week, I picked up InfoWorld and saw a good article on SOA Governance that addressed many of the issues I've seen.
The best practices they have document were all useful, but as I've mentioned in other entries (like this, this & this), there are a couple of things still missing:
- There is no such thing as a departmental service: As soon as the higher level organizations starts to use it - it needs to be coordinated at that level.
- Simulation will be a critical part of testing: Try and test the services against real world models.
- Whoever is maintaining the production system gets to decide if development is complete - Joint development is ideal, but if you need to have separation of development from maintenance, it is the maintenance folks that get to accept it into production, otherwise the developers can claim victory, collect the check and move on.
