Seems like most of the discussions I see of SOA governance are written by techies for techies and therefore emphasize technology. To a lesser degree, they emphasize process, and mostly ignore topics like how people interact with IT and how roles/rights/responsibilities shape IT.
My general approach will be to start at the top of a stack consisting of People, Organization, Process, Technology (POPT) stack.
Why POPT? For example, PPT is often used in architectural discussions, and DOTMLF is often seen in defense-centric processes.
Taxonomies reflect a drawing of distinctions with the purpose of highlighting contrasts among fundamental entities. These contrasts provide a framework for considering fundamental relationships...ultimately enabling more effective decisions & actions. This drawing of distinctions is the first act in transforming a formless pile of data into knowledge.
A taxonomy should be as simple as possible, and no simpler...for my purposes POPT seems about right...I first encountered it in a John Garstka presentation at NCW 2007.
The current SOA governance discussion seems to have not gotten much beyond generic statements about the importance of it being "driven by business needs."
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment