Talk:Introduction

From PGFSOA Wiki

My sense is that the discussion on SOA and EA here and elsewhere in the document needs to make more explicit the role of segment architecture. Further, the idea of reference architectures should be positioned as bridging between segment and solution architectures.

We should also add in this same chapter a sidebar or more explicitly reference the architectural principles (www.cio.gov). They directly motivate much or all of what is presented. Making this reference more explicit in this document, will make it easier for the reader to place this guidance in context.

EA is explicitly mentioned later in the document. It seems that the discussion in this chapter is the primary discussion. If so, then the other discussions need to be edited to remove any duplication.

Perhaps the next generation segment architecture tiger team can help tighten the alignment above?

--Kshemendra Paul 17:05, 9 March 2008 (EDT)

In the section on SOA challenges, we state the the adoption of SOA in the Federal space is immature. Looking for broad-based adoption that is probably true. But there are important works in progress. I would suggest we pick and highlight an emerging success story to provide some balance. For example, we could add a sidebar on the recent announcement by the Program Manager for the Information Sharing Environment (PM-ISE www.ise.gov) of a cross Government standard for Suspicious Activity Reporting. This is a nice example of cross domain, cross level of government, cross sector info sharing based on semantic models (NIEM) and SOA. It touches the Local, State, and Tribal communities in a big way. It also includes a federated repository between the DoD, IC, DOJ/DHS, and State and Local communities, which is a need highlighted later in the document.

Perhaps the PM-ISE architecture community can help illustrate this example?

--Kshemendra Paul 17:05, 9 March 2008 (EDT)

[edit] SOA Challenges

First of all: OPENID won't let me long in. So I'll note my comments:

We say "politics aside" and then go on to list 4 challenges. I agree with the comments to date, but unless we deal with the "politics" we are ignoring one of the major inhibitors. Recommend we add that has a 5th challenge and at least deal with it form the perspective of mother hood and apple pie. Most all are patriots and the idea that we have to become more agile and adaptive has already been introduced. We need to encorage that politics be put aside for the sake of the government operating as an efficient and effective enterprise.

Roy Mabry 3/12/08, 18:22

[edit] Confirmation of K Pauls guidance "from the field"

I concur with Kshemendra Paul's comments, a couple of us attended the CAF which motivated me to try and help out with effort. What is striking to me in this document is the lack of explicit reference to the FEA and Segment Architecture. IMO this link needs to be made or clearly excluded (I know this document isn't intended to be prescriptive) because these are different worlds, but to someone who has spent time in both EA and Solutions Architecture (EA is uber-Solutions Architecture in many industries), this connection is not going to be understood by many in either camp. I have a paper that is scheduled to be published in this months EA Journal that deals in part with this link, and we have some good internal material I'd like to contribute if my wiki ability allows. The document "calls out" illustrative examples of assessment methods such as Oracle's, it could also refer to methods like the MBT which may not be common knowledge.

The other general point about this document, I got the implication that the lower layers of the 3 layer model (SOI) had less "opportunities", this has not been my observation in the government, I know this seems to be conventional wisdom from the various consultancies.

- Joe V