← Prev in month ← Prev in thread
Next in thread → Next in month →

Fwd: PGFSOA - Review & Comment Request - Practical Guide to Federal Service Oriented Architecture

From
Len Maskey
Date
2008-03-12T20:56:44+00:00
ID
Thread
Fwd: PGFSOA - Review & Comment Request - Practical Guide to Federal Service Oriented Architecture
For those of you who may not have seen this, I think we should pay some attention to this and try to make sure it leverages and is consistent with the hard work we've done.

In particular, see https://osera.gov/web/fcioc/aic/pgfsoa/smw.

Also note from below,

We publicly announced the wiki at the OMG conference this week, here is

a

link to an article about that:

http://www.fcw.com/online/news/151875-1.html

Ken

Begin forwarded message:

-----Original Message-----

From: Paul, Kshemendra N. [mailto:] 

Sent: Monday, March 10, 2008 5:56 PM

To: Paul, Kshemendra N.; Carter, Deborah E; ;

; ; Golombek, Alan CIV

NII/DoD-CIO; ; ;

; ; ;

; Ford, Ylanda T; ;

; ; ;

; ;

;

; ; ; Frey,

Gregory;

Schoenbach, Andrew M.; ; ;

; ; ;

;

; ; josephgb; Wenger, Philip R.;

Okon,

Walt, Mr, NII/DoD-CIO; Mabry, Roy, Mr, NII/DoD-CIO; ;

; Wauer, George, Mr, NII/DoD-CIO

Cc: Martin, Isela; Pianko, Deborah L.; Smialowicz, Thomas J.; Stingley,

Patrick T.

Subject: RE: PGFSOA - Review & Comment Request

Hello, everyone,

I am pleased to announce that the Architecture and Infrastructure

Committee

(AIC) of the Federal CIO Council has initiated the next review cycle

for the

Practical Guide to Federal Service Oriented Architecture. The AIC has

decided to do this via a public wiki:

https://osera.gov/web/fcioc/aic/pgfsoa/smw

I encourage you all, and your teams, including bureau and program teams

that

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

the

month, and then go through a more formal approval process in April via

the

CIO Council. The expectation is that the wiki, if it is adding value to

the

process, may continue on and look to a next version or add on guidance.

I

have already made some comments and edits, and I intend to continue to

stay

engaged. 

The PGFSOA steering committee (subset of the AIC leadership) and

editorial

board will be the final arbiter in this process, the members of which

are

listed in the document.

We publicly announced the wiki at the OMG conference this week, here is

a

link to an article about that:

http://www.fcw.com/online/news/151875-1.html

Looking forward to seeing how this evolves. Please keep in mind that

the

decision to use the wiki represents something of a social media

experiment

for us as a community. Also, thanks to our partners at GSA for hosting

the

wiki.

Thanks in advance for jumping into the wiki.

-K

________________________________

=======================================================================

=====

==========

CIO Council starts wiki on architecture guidance

By Jason Miller 

Published on March 10, 2008

The CIO Council's Architecture and Infrastructure Committee (AIC)

launched a

wiki today asking for feedback from public- and private-sector experts

on

its draft "Practical Guide to Service-Oriented Architecture."  The

guide has

been through several reviews and this likely is the final one, said

Kshemendra Paul, the Office of Management and Budget's chief architect.

"We

wanted to get past sending a spreadsheet to agencies and then getting

back a

lot of comments," he said today at the Object Management Group's

Government

Days conference in Arlington, Va. "This is kind of a social media

experiment." 

The SOA guide's wiki will accept attributed and unattributed comments,

but

remarks made by experts who use their names will carry more weight,

Paul

added. The wiki also is using the Open ID standard, which lets users

log on

to many different Web sites using a single username and password. "We

want

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

wiki,

which the General Services Administration is hosting, likely will live

on

for future reviews. He added that Version 1 of the guidance should be

out by

late spring. 

The current draft guidance includes five chapters and is 71 pages long.

The

rationale, target and implementation chapters are most important, Paul

said.

The rationale chapter explains why SOA is important, including

improving

responsiveness, simplifying delivery of services and improving

transparency,

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

issues,

which tend to be the most challenges aspects of making SOA work well. 

The SOA portion focuses on modeling and the infrastructure portion

looks at

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

the

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

fits

into your governance structure and you need to ensure you have the

right

granularity to track results of SOA implementation." 

Paul also said the CIO Council is working on segment architecture

guidance.

A working group is collecting and analyzing best practices from several

agencies, including the Housing and Urban Development, Interior, and

Justice

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

segment

architectures."

The guidance will include methodology, training materials and templates

for

developing segment products. 
 

 

 
------------------------------------------------------------------------------------------
 
Ken Laskey
 
MITRE Corporation, M/S H305     phone:  703-983-7934
 
7515 Colshire Drive                        fax:        703-983-1379
 
McLean VA 22102-7508
← Prev in month ← Prev in thread
Next in thread → Next in month →