- 2. Services: (3CIU)
- a. What are services? (3CIV)
- I think I’ll use the decidedly non-govie Service Component Architecture (SCA) specifications and initiative that has tremendous momentum from the following vendors; IBM, BEA, Oracle, Sun, Redhat/JBoss, Sybase, IONA, and others – see osoa.org. (3CIW)
- SCA is relevant to the AIC/IAC wip (posted to ssc on core.gov 12/14) ‘Practical Guide to Fed SOA’ Outline parts 4-8. (3CIX)
- SCA is a model for constructing, assembling and deploying composite applications using heterogeneous languages, platforms and protocols that leverages existing mature standards. (3CIY)
- b. How are services composed and orchestrated in a SOA? (3CIZ)
- I’ll continue with SCA here again. (3CJ0)
- I’ll also likely mention the relationship to the BPM community, where composite applications are equivalent to business process execution, and this communities emphasis on modeling and simulation, executability and observation, and continuous improvement. (3CJ1)
- I will also mention relevant emerging BPDM standard that unifies existing MDA standards (including EDOC, UML, BPMN), distinguishes between choreography and orchestration, and will help to deal with portability and interoperability problems across different declarative runtime standards like XPDL and BPEL. (3CJ2)
- I’ll likely conclude by trying to make sure folks know that BPEL is only one way to orchestrate Web Services, and Web Services are only one style of implementing SOA – SCA is a good example of this. (3CJ3)
- c. What is the role of standards organizations? (3CJ4)
- To begin the process of creating stovepipes ;-) (3CJ5)
- Just kidding (sorta) – standards orgs help decouple the terms and concepts in design and runtime pursuits. Given that each standards org is different, they play different roles, usually driven by members that pay fees and influence outcomes for better or worse. (3CJ6)
- WHAT WE NEED: help in harmonizing (globally) and sometimes even normalizing (locally) the massive redundancy of so called ‘triangle of meaning’ concepts and terms (and objects) across design and runtime standards, which causes so much churn in human discourse – tremendous amount of waste occurs here. This is an area that the last Arch+ SOA panel of standards org reps punted on… (3CJ7)
- d. What can and should be piloted? (3CJ8)
- These are all Roadmap and Maturity demonstration of shared services management strategy principles in practice: (3CJ9)
- SOACoP should continue to add more heterogeneous design and runtime vendor implementations, using authoritative sources of actual OMB/AIC Reference Architecture service specifications from Federal LoB’s from actual providers, demonstrating design and runtime standards. This should evolve into a living and continuously available test suite of the Federal Enterprise Architecture. (3CJA)
- OMB/AIC should continue to demonstrate the concepts of Model Based Acquisition (MBA), in accordance with OMG Government Domain Task Force, and the relationship of MBA to Performance Based Contracting and Competitive Sourcing, differentiating and demonstrating the use of choreography and orchestration techniques in composite applications. (3CJB)
- SOACoP should add Enterprise QoS concerns, beginning with security and privacy and proceeding with reliability/accessibility/serviceability to the heterogeneous design and runtime platform implementations demonstrating multi-party interoperability based on Federal LoB’s. This should be done in the context of emerging profiles in WS-I and extended Web Services standards stack (WS-Policy, etc.). (3CJC)
- SOACoP should explore and demonstrate more Ontology driven interoperability scenarios, such as the autonomic configuration of service provider/consumer SOAP message exchanges based on WS-Policy statements requiring compliance with security/reliability/privacy ontologies as demonstrated by GSA, and other uses of emerging Semantic Web Services. (3CJD)
- Design and Runtime policy compliance in general - (3CJE)
- e. What is the AIC Services Subcommittee planning to do? (3CJF)
- Use the work of the SSC to make a stronger and explicitly traceable connection between Federal LoB RA’s and test driven service based procurement of targeted RI’s. (3CJG)
- Create standards out of RA’s in conjunction with OMG, as has begun with RMS and FTF. (3CJH)
- Use this to contribute to the ideas set forth in MBA. (3CJI)
