From:
soa-forum-bounces@xxxxxxxxxxxxxx [mailto:soa-forum-bounces@xxxxxxxxxxxxxx] On Behalf Of ajit kapoor
Sent: Wednesday, August 16, 2006
6:19 PM
To: Service-Oriented
Architecture CoP
Subject: Re: [soa-forum]
Question/Issue for the SOA CoP
Thanks for sharing your work. I must say I agree with you in
so much as it addresses the necessary technology conditions that must be met to
have a SOA paradigm, but the sufficiency has largely been ignored (may be based
on assumption that people and process based practices will follow).
[->] This is a critical
point ...the SOA paradigm is about aligning technology capabilities to ‘business’
capabilities. Any of the three dimensions (people, process, technology)
alone is necessary but insufficient to fully realize the benefits of SOA.
Today, many capabilities are still developed in a stove-piped manner. But in the DOD, as well as elsewhere, there
are initiatives already working to break down such stove-pipes to bring
about service oriented transformation.
I have been quite intrigued by the "SOA Buzz"
industry wide but am concerned by the lack of understanding of the architecture
(if viewed only from a technology viewpoint). The best practices should be
addressed fundamentally from the view point of standard processes,
people/organizational culture (a basic propensity to hinder change)and then
overlay the technical layer on it. Also even on the technology front the
standards are still in flux and the best efforts to integrate higher layer of
the SOA protocol stack must rely on the WS Interoperability forum.
[->] I whole-heartedly
agree that a focus on interoperability through industry standards is
required. But, even with the greater basis from WS-I forum, any
enterprise (government, private or extended) must establish its strategy to achieving
interoperability. This strategy will often result in a feedback loop, from
understanding needs and capabilities to profiling existing standards and
eventually working with the industry standards bodies to include use cases that
are particular to the needs and capabilities of the enterprise.
Vendors are selling point solutions for the higher layer
protocols and we will end up creating EAI equivalent of the SOA integration
problem. Where will the values be in terms of reusability, etc. I believe the
DoD and Government in general as part of the GIG/NC initiative must take the
lead in coalescing multiple standards on all the fronts of people, process, and
technology so as to start talking about best practices building blocks.
[->]The Enterprise
Wide Systems Engineering Activity, spearheaded by ASD/NII and DISA, is already taking
this lead.
1. Define essential enterprise-wide functions
2. Establish a GIG interoperability performance
framework
3. Capture the key enterprise interoperability
requirements
4. Work closely with the commercial Internet IT
industry and standard bodies to ensure DoD understanding of available and
future commercial technologies that could support the GIG
5. Provide technical input to ... joint portfolio
management processes and investment decisions
6. Involve the user community with the GIG development
community through ongoing experimentation and rapidly developed pilot
capabilities that enable informed user input
7. Ensure program compliance with the GIG technical
baseline through DoD CIO oversight and influence over DoD budget and
acquisition processes
I look forward to other comments and potential
recommendations. The result of this exercise should be, in my opinion, a
roadmap from current SOA platform to the desired state with People, process and
technologies roadmap defined in an evolutionary and standards way.
[->] As part of
this activity, the Net Centric Implementation Documents (NCID) document the
end-to-end requirements for performance, interoperability, and security, as
well as essential network enabling protocols, standards and implementation conventions
as part of the GIG technical baseline. I would encourage FDCE to engage
in this activity, especially as it relates to the GIG Enterprise Service
Oriented Architecture Reference Model that you’ve excerpted in your attachment.
In fact several of the concepts related to sandboxing,
certification, and lifecycle management are already being woven into NCIDv3.0.
Best,
Rebekah
----- Original Message -----
Sent: Wednesday, August
16, 2006 4:32 PM
Subject: RE: [soa-forum]
Question/Issue for the SOA CoP
Brand, I’m working on a project
sponsored by DISA Joint Interoperability Test Command. A key component is
the need to develop appropriate SOA implementation and validation and
verification guidance. The idea is to provide a useful service to GIG
software developers that encourages re-use of best practices and code.
The attached is a work in progress.
So….1. We have a mandate to do
this work. 2. We have no “not-invented-here” issues. 3. We
want to port as many industrial best practices as possible. 4.
We’re on a fast track.
We welcome any and all help from the SOA
Forum. The attached is very much a work in progress with no pride of
authorship.
Best, Chris
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
From:
soa-forum-bounces@xxxxxxxxxxxxxx [mailto:soa-forum-bounces@xxxxxxxxxxxxxx] On Behalf Of Niemann.Brand@xxxxxxxxxxxxxxx
Sent: Wednesday, August 16, 2006
3:08 PM
To: soa-forum@xxxxxxxxxxxxxx
Subject: [soa-forum]
Question/Issue for the SOA CoP
I have been asked about the
ownership/governance issue and whether any best practices exist for SOA.
We covered governance in the First SOA Conference for E-Government, but I don't
recall specifically ownership being discussed. Any suggestions, references,
etc. would be appreciated.
Thanks, Brand
_________________________________________________________________
Subscribe/Unsubscribe/Config: http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP