Using TOGAF to Define and Govern SOAs : Introduction and Objective
The purpose of this Technical Guide is to contribute to The Open Group mission of Boundaryless Information Flow, by providing guidance on how the architect can use TOGAF – now in Version 9 – to develop, manage, and govern Service-Oriented Architectures (SOA) or any architecture where SOA is part of the scope. This should facilitate the common understanding of the process for the development of SOAs and greatly improve alignment between the business and information technology communities. Utilization of the process, meta-model, references, and other TOGAF facilities will lead to the further adoption of SOA as an architectural style.
This Guide adapts the well-recognized set of best practice processes for the development, management, governance, and adoption of enterprise architecture and applies it specifically to SOA.
This Guide provides specific information on the adaption of TOGAF to develop SOA in the following areas:
- Use of the Architecture Development Method (ADM) to develop SOAs
- Modification of the TOGAF Content Meta-model for SOAs
- Modification of the TOGAF Content Relationship Meta-model for SOAs
- Adoption of SOA-specific general and technical reference models and their use within a TOGAF environment
- Adoption of SOA-specific governance requirements for a TOGAF environment
- Adoption of SOA-specific maturity models for application within a TOGAF environment
This Guide is designed for use by:
- Business people and business analysts to develop/identify/analyze the inherent linkage of business services delivered as information technology services
- Solutions/data/security/technology architects for the recognition of stakeholder viewpoints and the delivery of views/artifact that address stakeholder concerns specific to business and technology services
- Enterprise architects for the recognition of the re-usability of services across the organization and the prevention of the proliferation of information silos
- System and software designers for guidance in the delivery of architecture-compliant SOA solutions