Project Name SOA Governance
Project Status Approved by the SOA Working Group
Contribution to the Mission The SOA Working Group contributes to the Open Group mission of Boundaryless Information Flow, by developing and fostering common understanding of SOA in order to facilitate alignment between the business and information technology communities. The SOA Governance project will provide part of that contribution in the following specific ways. It will:
Develop a common definition of SOA Governance, including distinguishing between overall IT Governance and SOA Governance Define reusable processes and structures for SOA Governance Describe the relationship between IT to business governance and technical IT governance Define a SOA Governance Reference Model Better understanding of governance around SOA will
facilitate SOA adoption.
Deliverables The project will deliver typical TOGAF architecture artifacts such as:
What overall processes do we expect to include in SOA Governance More detailed scenarios including business services, actors and possible organizational views, for example: Service Oriented Architecture Management (the architecture itself) Business Process Management Information Management Solution (composite application) Management Service Portfolio Management Service Value
Management Service Management Service Delivery Management Service Design, Implementation, Deployment, De-commission Management Service Assets Management A conceptual model of concepts used within SOA governance An information model for SOA Governance A description of a business-IT governance in an SOA environment (View) A description of technical IT governance in an SOA environment (View) - An SOA Governance reference model, including IS
functions needed and their interaction. Application system - IS function mappings Application system interactions Standards for SOA Governance tool interoperability
Inputs Relevant work includes;
TOGAF The SOA Working Group SOA Definition Available SOA Governance inputs from Open Group members and other relevant, publicly available material such as the OASIS SOA Reference Mode ITIL and COBIT materials, as appropriate for them to be used SOA Reference Architectures Working Procedures The project will primarily work using conference calls, documents posted to the SOA WG Plato site and meetings at appropriate times and
venues.
The work of the project will follow the principles of the TOGAF standard + SOA principles, e.g. agility, reuse. (This could be a good way to validate SOA architecture principles from some other SOA work stream).
The project shall prioritize the deliverables to enable quick results.
The project will Collaborate and align with other relevant work both within and outside the SOA Working Group when appropriate:
Relation of SOA to EA (TOGAF) for work stream process SOA Ontology for Information Concepts SOA Reference Model for concepts and IS Architecture SOA Maturity for governance processes SOA Definition for SOA principle SOA KPI’s for SOA monitoring OASIS, OMG and other
organizations Project Leaders Mats Gejnevall, Capgemini
Tony Carrato, IBM
Project Team The team is composed of the members of the soa-governance mail list .
Project Plan The project will include the following activities:
Project formation by End of August , 2006 Regular teleconferences starting September 200 Initial face to face meeting, week of October 23, 2006 at the Lisbon Architecture Practitioners Conference
Proposed activities
Iteration 0 - Planning (4-8 weeks)
Activity
Description
Timing
Create project team
Market the project to get members. Appoint team responsibilities.
Create project plan
Expand on this plan
Model (8 - 12weeks)
Activity
Description
Timing
Define format of deliverables from iterations
What format shall we use for the deliverable?
Create common definition
Agree on a common definition (one popular and one detailed) and set scope
Create gross list of overview processes and actors
Levels 0 and 1 (Process groups and overview processes in each group)
Create gross list of information objects
What information is used within SOA Governance? Cooperate with SOA Ontology’s and reuse from OASIS reference model.
Iteration 2 – Digging into the details (8 - 12 weeks)
Activity
Description
Timing
Prioritize processes
Which processes are most important
Create business services for the processes
Break up the processes into business services.
Detail information objects needed by the prioritized processes/business services
What information is used by these business services?
Define course-grained IS services needed for prioritized processes
What IS services are needed to implement the business services (information)
Define IS service interactions
How will these IS Services interact to implement the business services and processes
Define (logical) application system (service domains/service groups/components)
How shall we group the IS services to create services domains/service groups/components. Don’t know the correct TOGAF concept
Define (logical) application system interactions
How will these application systems interact?
Iteration 3 (8 - 12 weeks)
Same as iteration 2 but for lower-priority processes