Talk:Executive Summary

From PGFSOA Wiki

Below the definition of the OAIS def for SOA, you say the the document is for Architectes. In the Enabling the Mission, you include more in your list than just architects. Suggest these be consistent.

<ph> I addresssed the concern of 'architect only' by adding CIOs as we had in the "Enabling the Mission" section.

This section talks very little about standards and how departments or agencies adopt those standards. I believe that without a strong standards program in place implementing a successful SOA program will be difficult if not impossible. I believe this section falls short without having well defined standards program identified as key for implementing SOA.

<note from editor -- I didn't now where to put the following, so I stuck it here> Haycock - This section below seems to be quite detailed for the Exec Summary. I would remove it here. This document is very complete, but neglects two areas that are crucial to the success of a SOA implementation, both within a single agency and in a federated environment.

The first and most significant area is that of data and associated schemas/ontologies. It is not enough to say that data will be exchanged using these entities. It will be necessary to put significant effort into data modeling to create Conceptual Data Models (CDM) that can be converted into data schemas that are used for data exchange. This enables the organization to have a single set of business rules that are used to populate the schemas with data. The schema process must be tightly governed by the organizational entity resposible for it. Schemas cannot "evolve" as discussed within the document, but must be created and changed only after their data has been modeled and they have been vetted through the data governance processes. Having schemas that have been produced through strong modeling and governance processes is especially important when data are to be exchanged among agencies.

The second area is that of service logging. It is essential that access to provided services be logged and that the logging data include an identifier that can link it to the invoking system. Such logging data are essential for notifying owners of applications that call the services of new versions and for producing usage metrics. <end of editor note>