Sent: Monday, March 10, 2008 5:56 PM
Cc: Martin, Isela; Pianko, Deborah L.; Smialowicz, Thomas J.; Stingley,
Subject: RE: PGFSOA - Review & Comment Request
I am pleased to announce that the Architecture and Infrastructure
(AIC) of the Federal CIO Council has initiated the next review cycle
Practical Guide to Federal Service Oriented Architecture. The AIC has
decided to do this via a public wiki:
I encourage you all, and your teams, including bureau and program teams
are planning for or pursuing SOA implementations, to:
* go to the wiki,
* read the document,
* review the discussion pages and recent changes,
* make attributed changes, and
* track the evolution of your input and the document as a whole
The goal is to try to have the review process converge by the end of
month, and then go through a more formal approval process in April via
CIO Council. The expectation is that the wiki, if it is adding value to
process, may continue on and look to a next version or add on guidance.
have already made some comments and edits, and I intend to continue to
The PGFSOA steering committee (subset of the AIC leadership) and
board will be the final arbiter in this process, the members of which
listed in the document.
We publicly announced the wiki at the OMG conference this week, here is
link to an article about that:
Looking forward to seeing how this evolves. Please keep in mind that
decision to use the wiki represents something of a social media
for us as a community. Also, thanks to our partners at GSA for hosting
Thanks in advance for jumping into the wiki.
CIO Council starts wiki on architecture guidance
By Jason Miller
Published on March 10, 2008
The CIO Council's Architecture and Infrastructure Committee (AIC)
wiki today asking for feedback from public- and private-sector experts
its draft "Practical Guide to Service-Oriented Architecture." The
been through several reviews and this likely is the final one, said
Kshemendra Paul, the Office of Management and Budget's chief architect.
wanted to get past sending a spreadsheet to agencies and then getting
lot of comments," he said today at the Object Management Group's
Days conference in Arlington, Va. "This is kind of a social media
The SOA guide's wiki will accept attributed and unattributed comments,
remarks made by experts who use their names will carry more weight,
added. The wiki also is using the Open ID standard, which lets users
to many different Web sites using a single username and password. "We
people to read all the comments and add to the discussion groups," Paul
said. "The final decisions will be made by the governance board."
This latest review cycle will end in by April 1, but Paul said the
which the General Services Administration is hosting, likely will live
for future reviews. He added that Version 1 of the guidance should be
The current draft guidance includes five chapters and is 71 pages long.
rationale, target and implementation chapters are most important, Paul
The rationale chapter explains why SOA is important, including
responsiveness, simplifying delivery of services and improving
security and resilience.
The target chapter focuses on the three levels of SOA: service-oriented
enterprise, service-oriented architecture and service-oriented
infrastructure. The enterprise discusses governance and key cultural
which tend to be the most challenges aspects of making SOA work well.
The SOA portion focuses on modeling and the infrastructure portion
how SOA can run in an operational environment.
Paul said the keys to implementation are the heart of the document and
encouraged users to read it.
"There are several generic SOA maturity models that currently exist and
road map section offers one, but agencies can use which ever model they
choose," he said. "You have to understand where you are now, where it
into your governance structure and you need to ensure you have the
granularity to track results of SOA implementation."
Paul also said the CIO Council is working on segment architecture
A working group is collecting and analyzing best practices from several
agencies, including the Housing and Urban Development, Interior, and
departments in addition to the Human Resources Line of Business effort.
"We want to make it more straightforward to implement segment
architectures," Paul said. "The goal is to increase the value of
The guidance will include methodology, training materials and templates
developing segment products.