Talk:Target
From PGFSOA Wiki
[edit] Incorrect Standards Representation
I have taken these actions more than a couple of times now -
BPEL is an OASIS standard, but OASIS doesn't show up on the matrix. They and the W3C promote usually runtime standards. The OMG promotes usually design time standards, with the notable exception of CORBA.
NIEM is not a Semantic Web Standard, they are W3C standards like RDF and OWL.
W3C, OASIS, and the OMG are examples of Voluntary Consensus Organizations.
NIEM is not a Voluntary Consensus Organization, more like a Mandatory Agreement Organization across NIEM CoI's (?).
Many of the other standards are outdated, for example SCA goes with 'composite applications' and osoa.org.
BPEL4WS and WSCI are orchestration standards, the former of which is more appropriately grouped in BPM as a runtime execution language, the latter of which is no longer in use so far as I know.
George
NIEM is a hybrid on a lot of dimensions - semantic web standards and type of organization. NIEM is a voluntary consensus organization that as a group asked for and supports use of mandates to encourage further adoption and inter-operability. In the Federal space for certain agencies there is a use mandate, for others it is voluntary use. The standards themselves are voluntary consensus based on participation in the governance organizations.
Perhaps the NIEM community can clarify their representation in this document.
--Kshemendra Paul 17:18, 9 March 2008 (EDT)
George is correct that NIEM is not a voluntary consensus standard, as these terms are understood in the standards community. Akb 10:04, 18 March 2008 (EDT)
[edit] Target SOA, SDLC, and EA Integration
Sections 3.2.1 and 3.2.2 - Target SOA, SDLC and EA integration, SOA and interoperability - we need to do a better job integrating the ideas of segment and solution architecture here, and the reference architecture as a bridge (really, a high level design for a specific service that is a clear extension of a segment architecture. Also, SDLC and EA integration are well understood topics addressed elsewhere. In this document we should reference that guidance via the enterprise-segment-solution breakdown.
--Kshemendra Paul 17:18, 9 March 2008 (EDT)
[edit] Steven Covey pic??
As a SOA and EA practicioner I look forward to participating in this collaborative effort!
My first comment is that the picture of Steven Covey is both offputting and inappropriate for this document. He has nothing to do with SOA that I am aware of, and I wouldn't be surprised if he were to have heartburn if he knew his image was being used without his knowledge and permission (assuming that it is being used here without his knowledge and permission)!
And why Steven Covey? Why not Dale Carnegie, or W.E. Deming, or John Zachman for that matter?
Now on to more substantive issues.
Jim T., SMDI, Inc.
Agreed. Please remove this inappropriate advertisement. Akb 09:52, 18 March 2008 (EDT)
[edit] Last Sentence in the frame around Covey Picture
"On the bright side, because SOA enables agility and innovation, as agencies mature their SOA capability they will find they can more rapidly progress toward their target architecture."
Carring on the theme on addressing the political nature of mankind, add after architecture, "which is in one's on self interest."
Roy Mabry 3/12/08, 19:32
[edit] SOE, SOA, SOI - General Observation
There are three major parts mentioned in this section that describe Service Oriented Architecture. However, the 2nd major part of the Target Architecture has the same name as the main topic of the document. It causes confusion when the document is about SOA overall and within the document there is a major part describing SOA also named "SOA".
Suggestion: If SOA is broken down into three separate sections: SOE, SOA & SOI; the 2nd major part should have some other name than SOA to avoid confusion with the main SOA topic.
--Anthony Dean 10:21, 24 April 2008 (EDT)
[edit] Service Oriented Infrastructure - Section 3.3
Service Oriented Infrastructure should promote the common hosting environment to allow leverage of share infrastructure service. Suggestion: Add some language on common hosting environment in order to offer infrastructure service. May want to mention about robust infrastructure with disaster recovery (DR) capability.
--Anthony Dean 10:44, 24 April 2008 (EDT)
[edit] Federated governance should be a part of the organization's process
Federated governance is a complex topic that requires additional consideration to the points already made in section 3.1.2. For federated governance to be meaningful, it must be an integral part of the organization's process. This may be required at multiple levels of the organization, e.g. enterprise, program, project. As such, the governance method should be a part of the EA or the SDLC. This process must be documented, accessible, and repeatable. Here is one example of a common industry SDLC tied to SOA governance - http://www.ibm.com/developerworks/rational/downloads/06/plugins/rmc_soa_gov/soa_plugin.html
As governance must be considered as part of the process, it must also have a mechanism to manage the change to the governance activities.
- Liz Martin, IBM
[edit] Standard Federal Government Services Will Emerge - Section 3.2.3
I did not like this statement "Today, the IT Infrastructure Line of Business (ITI LoB) serves as the umbrella, a cross-agency initiative driving agencies toward a unified federal SOI.". I would like to see this statement weakened or significantly strengthened something about collaboration with this SOA working group if true would be sufficient, I don't know who the players in the ITI LoB are but as a practitioner I am skeptical that they are going to independently build the SOI, and it sounds like "we" are washing our hands of this problem. From what I've heard they are not even looking at things like ITIL yet (This should be a EA profile IMO, in a non resource bound world), which has many implications from an SOI perspective in my view. Standardization of essentially commodity IT processes for one thing SRM Back Office Services and Support Services, PRM Technology Measurement Area (and the associated services), known change management and infrastructure governance process areas, the CMDB with its potentially overlaps with the service portfolios and integration with the service registries/repositories) + ITIL has a lot to say about SLA performance quality attributes an important factor for SOA.
- Joe V
