This version was approved by votes of The OPen Group'sSOA Working Group and Architecture Forum. It replaces the Project Description: Relation of SOA to Enterprise Architecture and TOGAF, Version 0.4.
SOA is emerging architectural style that needs to be explicitly supported by TOGAF. As an architectural style, explicit support is best provided through style specific adjustments of TOGAF. Style specific adjustments should enable a TOGAF trained practitioner to use TOGAF 8 & the SOA adjustment "out of the box" to develop a service oriented architecture.
Project bounded by current version of TOGAF 8. Intent is to provide "preliminary phase adjustments" to TOGAF. Focus on ADM phase A-D: providing required views, attributes, artefacts, process change. Work effort & scope will be adjusted to capture other SOA WG / OG Architecture Forum projects that overlap. Guiding principles will be "good enough" and "practical" to an architecture practitioner.
Project will operate with two co-chairs (Dave Hornford & Awel Dico). Co-chairs are both members of the SOA Working Group and Open Group Architecture Forum. Project has two integrated reporting structures: SOA Working Group and Architecture Forum. Co-chairs will report progress and accept direction regularly to both Open Group bodies.
Decision making within the project is consensual with formal voting open to participants within the project & subsidiary work areas. In the event of conflict regarding work product, preference will be given to delivery participants within the project or referred back to the SOA WG/Architecture Forum as required.
Co-chairs may devolve responsibility to work area leaders.
Open to members of the SOA Working Group and Open Group Architecture Forum.
Project will borrow shamelessly from contributed IP and the work products of other SOA Working Group projects & Architecture Forum projects.
Project will use open tools & mainstream office productivity tools by preference to avoid participant barriers to entry. Specialized commercial tools will be utilized if a participant has the tools, licenses can be provided to other participants for the purpose of the project and the output is in a transportable format.
Co-chair: Efficient delivery of project following Open Group cultural norms and reporting processes
Work area leader: Efficient delivery of expected work product following Open Group cultural norms and reporting processes
Schedule bounded by conferences. Initial delivery focused on Jan/Feb conference.
Further refinement may proceed at the discretion of participants, SOA WG & Architecture Forum. Project will terminate in 365 days.
"Good enough", "Practical" & "Energy" - project will continue or stop when enough has been provided to a practitioner to deliver SOA using this adaptation of TOGAF 8, or when participants are prepared to move on.
Formal vote by project participants
Usability of TOGAF to a practitioner will be improved if the practitioner is delivering SOA
Meeting times will be referenced from the Canadian Eastern & Mountain Time Zones
Where practical communication tools that enable offline communication will be used to facilitate a global team
Practical Guide to using TOGAF to 'do SOA'
A practical guide to performing SOA with TOGAF will provide a common practical method of delivering SOA using an industry leading enterprise architecture method. The process of refining best practices into a practical guide will require a common understanding of SOA, SOA preparation and SOA implementation for architecture practitioners, business people and information technology.
The SOA/TOGAF Practical Guide project will make a very specific contribution to the common understanding of SOA and the utilization of TOGAF, thus fulfilling part of the mission of the SOA Working Group, the Architecture Forum and of The Open Group.
SOA Home
