Skip to end of metadata
Go to start of metadata

Welcome to the UC Berkeley SOA Governance group wiki!


Service Oriented Architecture (SOA) holds the promise of fostering and facilitating re-use and sharing of service models.  More than a promise, such efficiency and economy is a primary raison d'etre of the methodology.  However, if we cannot see synergies across the growing number of SOA projects at UC Berkeley, SOA has an unlikely future here. 

Coordinating reuse and sharing takes effort among architects on SOA projects. Read more...

Who's in this group?

The UC Berkeley SOA Governance group is open to campus architects and developers. Current participants represent a range of projects, including a number of large-scale, multi-institutional efforts. Cross-pollination of this type serves precisely the goal of the group: to understand the crucial issues related to resource models, entities and relationships in various contexts and to hasten alignment of key service contracts across essential campus information technology development initiatives. Please see the list of members and their projects.

Meetings and Discussions

Meetings take place regularly on the fourth Thursday of the month. Sometimes, depending on time of year, members' workloads, etc., we meet only quarterly. Often, the SOA Governance group meets in tandem with the Services Tech Stack group, so that architects, service managers and developers can investigate issues together, from a range of perspectives. See below for agendas and notes from our meetings.

Meetings occur in either Barrows Hall or in Earl Warren Hall (2195 Hearst). Meeting notices (and agenda) are sent out on our mailing list, which is also where we carry on discussion between meetings.

Follow the discussion on our Nabble archive. Find back posts to the soa_architects_discuss list dating from Fall 2009.  Note that the archive is currently set to be viewable by the public.

Please read about our emerging process.

Hot Topics

  • OpenID; guest accounts; authentication for services: Recent SOA Gov and Services Tech Stack group discussions have been focused on the identity management needs of applications. At our April 22, 2010 meeting, Allen Tom of the OpenID Foundation gave a presentation to the combined group. Afterwards, members were assigned a task: "Describe your use case for enhanced ID Management services." Please use the discussion list to present your case. Please see the ID Management page for an overview of, details about and summary of the discussion.


Strategic initiatives include:

  • seeking campus funding for several proposed projects
  • formulating a larger push for service messaging infrastructure
  • internal collaboration to implement needed improvements (services and developer tools)
  • a broad survey of service usage and needs across the campus
  • visualizations of the current state of data acquisition and sharing across systems on campus

More details forthcoming.

Table of Services

A major product of this group will be our Table of Services.

Success stories

Under review

Meeting pages

SOA Governance group meetings provide a forum for communication among the multiple service oriented architecture-based development projects in which the campus participates. By analyzing and documenting this ongoing work, the group seeks to define best practices and drive agreement on recommendations to the campus leadership regarding approaches and policies.

  • Standing agenda (Proposed)
    • General project updates (20 minutes - three to four minutes per update)
    • Presentation and discussion (30-35 minutes)
    • Other topics proposed to the group or open discussion (as time allows)
    • Identify presentation for next meeting/review action items/next steps (max 5 minutes)
  • Method
    • Presentations will be identified during the previous meeting; or, if necessary, by group moderator during the period between meetings.
    • A week prior to each meeting, we will send out a query to group members seeking calls for discussion.  Proposals should include links to documents for review before the meeting. The agenda will be finalized and distributed two days prior to each meeting. 

      Please insert calls for discussion into the preliminary agenda on the Meeting Page for the given meeting.

    • Topics might include:
      • New services/resources identified as candidates for reuse
      • Issues with existing shared services and resources
      • Updates on outstanding issues.
    • Please track this discussion and review - in advance of the meeting - any documents or links included with the agenda. 

  • No labels