pgfsoa-infra
[Top] [All Lists]

Re: [pgfsoa-infra] Key messages

To: "pgfsoa - SOA Infrastructure" <pgfsoa-infra@xxxxxxxxxxxxxx>
From: "Farrow, Robert" <RFarrow@xxxxxxxxxxxxxx>
Date: Wed, 14 Feb 2007 12:51:35 -0800
Message-id: <B53C551CE7B5F4429283A65C2E771C5303E8EBA4@xxxxxxxxxxxxxxxxxxxx>
Chris,
 
I like where you're headed.  I've added a couple of my thoughts to the outline below (in red).  Let's discuss.  Thanks...
 
Bob
 
Bob Farrow
Vice President, Federal
Fujitsu Computer Systems Corporation
1120C Benfield Boulevard
Millersville, MD 21108
Office 410-987-4035
Mobile 410-598-7628
Fax 408-764-5013
 


From: pgfsoa-infra-bounces@xxxxxxxxxxxxxx [mailto:pgfsoa-infra-bounces@xxxxxxxxxxxxxx] On Behalf Of Chris Gunderson
Sent: Tuesday, February 13, 2007 5:21 PM
To: pgfsoa-infra@xxxxxxxxxxxxxx
Subject: [pgfsoa-infra] Key messages

Team,  Well, I’ve read and re-read all our inputs re: “key messages” .   There is certainly good thinking embedded… However, I believe we have to take a step back and ask what is different about our effort compared to the many white papers re: SOA we’ve all read and written.  Here’s my thinking:

 

  1. PGFSOA is from the Fed CIO’s Council so should represent enforceable policy.
  2. It should emphasize “practical” business case vice wonders of technology
  3. Our chapter is “infrastructure” so we should focus on shared capability

 

With that in mind, this is what I came up with…It’s posted in the public wiki under ContributionFive for your edits.

 

I think most of the comments our group has made can fit into this framework.  If you don’t like this approach, we’ll need another suggestion for binning the scatter diagram that we’ve currently got I think… Ideas? Best, Chris

 13 February 2007

Chris.Gunderson@xxxxxxxxx

703 262 5332

 

 

Key Messages Re: Practical Guide to Federal SOA Infrastructure

 

I would think that a “practical” guide for anything should provide simple answers to the questions: What? Why? When? Where? and How?

 

Bear in mind that practicality is not about technology, it’s about productivity.

 

Further, if this PGFSOA document is to be useful as practical policy guidance, its tenants must be objective and enforceable.   

 

Clearly, a practical guide to (1) Federal (2) Service Oriented Architecture (3) Infrastructure, should address (1) serving the tax payer; (2) the business case for a computer network “service” model; (3) generic capability shared across communities. 

 

With these ideas in mind, I think the key messages for the “Infrastructure” chapter of the Practical Guide to Federal Service Oriented Architecture are as follows:  

 

What:  An Enterprise Service (Software) Bus with the following characteristics:

 

  • Public, not private, (intellectual) “property”

 

  • Collaborative, not competitive, investment and development 

 

  • Open, not proprietary, interfaces 
 
  • Mediation between protocols, data and message formats, and interaction patterns
 
  •  Scalable, robust secure communications for diversely located services 

 

 Why: Decrease Cost and Increase Productivity 

 

  • Decrease cost of information processing capability by leveraging re-use and economy of scale. 

 

  • Increase speed to deploy information processing capability through central service deployment and upgrade.

 

  • Innovate through collaborative mash up. 
 
  • Employ best of breed solutions that are interoperability centric 

 

When: Now  

 

  • Field capability immediately and incrementally, don’t plan  a “flag day” for the “out years”

 

Where:  In the “White Space” Between Stovepipes

 

  • Address issues that cross community boundaries  
 
  • Focus initially on XML-based web services    

 

How:  Continuous Community Investment in Incremental Improvement

 

  • Identify key business issues and establish objective measures of effectiveness.

 

  • Identify critical infrastructure issues -- e.g. security & interoperability, especially semantic interoperability -- and define and instantiate corresponding open standards.  

 

  • Pool resources through a community tax.  

 

  • Invest in a collaborative development and testing platform.  Fail fast and cheap; learn together; succeed.  
 
  •  Deploy both Service Level and Exception management approaches   

 

  • Populate and document a dynamic library of successful reference implementations; build on top of success.   

 

 

Chris Gunderson

Research Associate Professor of Information Science

Naval Postgraduate School

Principal Investigator, W2COG and Netcentric Certification Office Initiatives

(O) 703 262 5332

(C) 831 224 5182

 


_________________________________________________________________
Message Archives: http://colab.cim3.net/forum/pgfsoa-infra/
Subscribe/Unsubscribe/Config: 
http://colab.cim3.net/mailman/listinfo/pgfsoa-infra/
Shared Files: http://colab.cim3.net/file/work/pgfsoa/pgfsoa-infra/
Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?PracticalGuideToFederalSOA
Community Portal: http://colab.cim3.net/
To Post: mailto:pgfsoa-infra@xxxxxxxxxxxxxx    (01)
<Prev in Thread] Current Thread [Next in Thread>