1. U.S. General Services Administration George Thomas, GSA OCIO Chief Architect Line of Sight = Reuse

2. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-162 Topics Levels of abstraction Recursive decomposition Specifying external boundaries Deployment decisions Discovery of commonality

3. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-163 VCA + MDA on SOA = Executable EA What we want - –Process centric and Service Oriented executable models with FEA associations to automate artifact generation for a variety of end users What we need - –Formal grammar expressing collaborative role interactions Our Approach - EDOC/ECA/CCA –Enterprise Distributed Object Computing (EDOC) – Enterprise Collaboration Architecture (ECA) – Component Collaboration Architecture (CCA) Open Standard – Object Management Group (omg.org) ratified Unified Modeling Language (UML) Profile The Result –PIM - Data driven (Data Reference Model - DRM) conversations between roles (Service Component Reference Model - SRM) in the context of a business process (Business Reference Model - BRM) –PSM - specializations mapped to deployment decisions (Technical Reference Model - TRM) –Performance Reference Model (PRM) metrics pervade PIM and PSM models

4. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-164 (EDOC/ECA) CCA Grammar Implementation Net Hardware Operating System Framework, Middleware & Container Interaction Path Component in Role Interaction (With Information) Role Collaboration

5. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-165 Order to Payment Process Diagram

6. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-166 Identifying Roles

7. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-167 Finding Roles and Inner Roles Customer Project Manager Customer Contracting Customer Financial Officer Supplier Financial Officer Supplier Project Manager Supplier Contracting Officer FSS: Order Manager FSS: Financial Officer “Swim Lanes” Order to Payment CustomerProcurement Broker Supplier Project Manager Contracting Officer Financial Officer Project Manager Contracting Officer Financial Officer Financial Officer Order Manager RFQ Manager Catalog Manager Roles in a Collaboration

8. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-168 Highest Level Roles in Procurement Collaboration Order to Payment Customer Procurement Broker Supplier

9. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-169 Identifying High Level Protocols Interactions

10. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1610 Attach Protocols to Roles as ‘Ports’ Group transitions together into logical units

11. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1611 Specifying Interactions

12. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1612 Inner Protocols Protocols represent conversations between roles Conversations frequently have sub- conversations, detail about a specific subject These sub- conversations are inner protocols Inner protocols can also be reused in other protocols or even as top-level protocols Protocols can “nest” to any level of detail

13. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1613 Fully Elaborated Protocols This is an example of a protocol with the inner-protocols, document flows and types specified This level of detail is specified when we know it and visible when we need it

14. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1614 Co-managed Service Collaboration Specification

15. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1615 Summary High Level Collaboration Specification Simplified View - Level of detail is optional

16. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1616 Drilling Down into Customer Details Customer Project Manager Contracting Officer Financial Officer

17. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1617 Choreography of Process

18. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1618 Modeling Collaboration Data Fill in details of documents Focus on business information - not technology Interoperability Data Model (DRM) - Not an ODS information model May be derived from existing sources Includes –Composition –Type –Cardinality Document Object

19. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1619 Multiple Implementations of a Role Customer Role (Logical) DOL Customer Component (Implementation) DOI Customer Component (Implementation) Internal Customer Component (Implementation) The “Inside” can change as long as the external “contract” is satisfied

20. George Thomas, GSA OCIO Enterprise Architecture Group 12-Feb-1620 GSA FSS O2P ‘Punch Out’ Demo Benefits –Easy to compose collaborative alternatives, reusing roles and protocols in new scenarios –Provides an open standard BPR/SOA formal object model for recursive component decomposition (SRM granularity) –Stakeholders understand and provide feedback on the proposed process Communicates intent and validates correctness prior to budget/procurement Provides framework for optimizing metrics and generating EA artifacts, views, reports, docs, etc. –Technology platform is a deployment decision, adapting interface specifications to whatever – WS, EAI/MOM, J2EE/.NET, etc. Model simulation specifies how existing and planned systems interoperate (multiple heterogeneous), collapsing SDLC