How To Enforce Your Enterprise Architecture With TOGAF
So you have defined your architectural vision, strategy and blueprints — what's next?
EA Life CycleEnterprise Architecture(EA) has little value without implementation and governance. Simply communicating the EA and expecting the organization to comply is ineffective.
Once the EA is defined, it is necessary to govern that architecture through implementation.
EA is a cyclical process of EA definition, scope identification, project governance and feedback loops.
Enter TOGAFThe TOGAF Architecture Development Method (ADM) defines the EA life cycle in a series of steps A-H.
TOGAF Step G - Implementation and Compliance provides a framework to enforce the EA.
TOGAF Implementation and ComplianceImplementation and Compliance takes place at the project level. It takes the EA as an input and produces two work items: solution building blocks and compliance assessment.
Solution Building Blocks
Early-on in the project an enterprise architect should work with the solution architects to identify building blocks from the EA blueprint will be incorporated in the solution.
Periodic compliance reviews ensure that project solutions are in-line with enterprise architecture. Project stakeholders such as project managers, IT managers, solution architects and lead developers should be accountable to compliance.
Compliance assessments include a series of checklists for hardware, operating systems, software services, middleware, applications, information management, security, systems, system engineering, methods and tools.
What is the value of your EA project in 9 words or less?|
ITIL 2011 (v3) identifies 25 core processes. Here they are. |
Current state blueprints capture business, data and implementation architecture at the conceptual, logical and physical levels.|
Our collection of SOA architecture resources and tools.|