Nigel Green (Executive Enterprise Architect at Capgemini UK) has an interesting discussion asserting that a "wiring diagram" approach to business processes is likely to falter when it spans department or external boundaries.
He touches on factors I've mentioned before (e.g., values, policies, events, content, trust), and rightly notes that these must be explicitly addressed in architecting.
These factors have been formalized into an acronym (VPEC-T), and discussed in a book ("Lost in Translation", by Nigel Green and Carl Bate) that "focuses on outcomes and adoption, not on technology, processes, and function." This sort of thing is exactly right in my opinion, but it seems that many techno-centric companies find it not so much heretical as incomprehensible.
His Beads-Threads metaphor may not be especially catalytic, but the basic message is an important one that rarely appears in the techno-centric world of IT architecting.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment