EAI / SOA Composite System

1. EAI / SOA Composite System A System Engineering Approach

2. Agenda • Establish Definition • Objectives • Genesis of Service Oriented Architecture • Key Applicable System Engineering Artifacts • Recommended System Engineering Practices

3. Definition of Service Oriented Architecture • As defined in commercial practice by products • IBM CICS • AT&T Tuxedo • Object Management Group’s Common Object Request Broker Architecture (CORBA) • TIBCO BusinessWorks • VitriaBusinessWare • IBM WebSphere • Oracle / Sun WebLogic • SOFTWAREagWebMethods • A software methodology facilitate composite application construction

4. Objectives • Establish a Common Understanding of • Enterprise Application Integration (EAI) • Service Oriented Architecture (SOA) • Identify Systemic Developmental Challenges In Implementing EAI / SOA / Composite Applications • Demonstrate Value of System Engineering In Addressing These Challenges

5. Genesis Of Service Oriented Architecture Genesis of ADP Customer Finance & Accounting Procurement Manufacturing Transportation Sales Company A

6. Genesis Of Service Oriented Architecture A Driving Business Practice: Mergers and Acquisitions Customer Finance & Accounting Finance & Accounting Procurement Procurement Sales Sales Transportation Transportation Manufacturing Manufacturing Company A Composite Company From Mergers and Acquisitions Company B

7. Genesis Of Service Oriented Architecture A Driving Business Practice: Outsourcing Finance & Accounting Finance & Accounting Procurement Procurement Sales Sales Transportation Transportation Manufacturing Manufacturing Company B Composite Company For Duration of One Business Transaction Company A

8. Genesis Of Service Oriented Architecture Discovering the Notion of a Business Service Price Information (EDI 879) Request for Quotation (EDI 840) Customer Finance & Accounting Procurement Manufacturing Transportation Sales Company A

9. Genesis Of Service Oriented Architecture Mechanization of the Business Service Request for Quotation (EDI 840) Motor Carrier Rate Proposal (EDI 107) Property Damage Report (EDI 112) Composite Enterprise Applications Provided Business Services Business Services Finance & Accounting Procurement Manufacturing Transportation Sales • Connectivity / Integration • Translation • Business Objects • Event Processing • Workflow Management • HMI • Business Performance Management

10. Where System Engineering Fits InThe Challenge • SOA – EAI • System Engineering Challenge • Define Encapsulated Business Services • Compose Applications from Encapsulated • Business Services • System Requirements Specifications • Factoring Into Services • (SW Components) • CONOPS • Business Process Analysis (Operational Activities) • System (Composite Application) Architecture CONOPS / Arch for Development CONOPS / Arch for Operations

11. Key Applicable System Engineering ArtifactsThe “Document” Tree System Engineering Management Plan System Architecture CONOPS System Requirements Specification Test Plans and Procedures System Maintenance Plan

12. Key Applicable System Engineering ArtifactsTopics to Address in the System Engineering Management Plan System Engineering Management Plan • Define • Composite Change Management • Define • Organization of Organizations • Define Composite Technical Management • Scheduling and Resource Management

13. Key Applicable System Engineering ArtifactsPreparation of System Architecture System Architecture • Date and Information Viewpoint • Capability Viewpoint • Services Viewpoint • Standards Viewpoint • Systems Viewpoint • Operational Viewpoint • Consistent with CONOPS define Composite Application / System Capabilities • Identify Composite Resources • Composite Business Objects • Relationships with Enterprise Application Data • Organization of the application donor Organizations • Business Activities of Composite Organization • Composite Performers • Composite Business Services (Can reference benchmarks like EDI, Rosettenet • Composite Behaviors / Conditions • Model (Service, Performer, Resource Capability) for the Composite Application / System) • Use products not standards • If standardize upon particular Enterprise Applications to provide particular Composite functions, structures or behaviors • Model the composite system, system elements and functions • Relate Composite Capabilities and Services to the Enterprise Systems or Applications

14. Key Applicable System Engineering Artifacts Preparation of the CONOPS CONOPS • Key Concepts • Problem Statement • Scenarios • System Capabilities • What is the Business Problem – What new business services are needed • Describe the existing business services and enterprise applications • Define the deficiencies resulting from lack of integration • Define the integration approach and postulate new business services • Define the proposed new business services • Define the new business behaviors enabled by the composite applications • Name and define the new composite application • Identify the participating organizations and describe how they will work together to create and maintain the composite application / business services • Organizations affected by new business services • Define capabilities of the proposed / new business services in terms of existing capabilities of the applicable enterprise applications • Identify and define the capability performance expectations • Define constraints, both technical and political • Define Service Management Concepts • Describe the business relationships created by the proposed composite system • Enumerate and describe the business scenarios supported by proposed composite system • Define maintenance scenarios • Define legal and political scenarios required to create and operate the composite applications

15. Key Applicable System Engineering Artifacts Preparation of the System Requirements Specification System Requirements Specifications • Define Constraints • Elaborate System Capabilities • Verification and Validation Methods • Define Business Process Requirements • Development • Operational • Define system functions in terms of the functions existing in the applicable Enterprise Applications / Capabilities / Resources • Define states and modes in terms of both composite capabilities and existing states, modes and functions • Focus is on the composite applications and resulting services • Legal constraints that govern the legal relationships among the contributing organizations • Composite application and business services reliability • Composite application and business services availability • Composite application and business services security • Composite application and business services maintainability • Composite level / business services functional and behavioral V&V • Composite organization maintenance V&V methods • Enterprise level contributing functional and behavioral performance V&V

16. Recommended System Engineering Practices Practical SOA / EAI System Engineering Principles • Behavioral Oriented (Event / Response) Establish Business Need For “Reuse” of Encapsulated Systems • Business Process Centric • (Composite) • Use Products • Not Standards • Define Services Verify and Validation Organization and Processes Define New System in Terms of Existing Systems • Level of Abstraction is Business Process NOT • Software Modularization • Start with SOA Management Capabilities • Define Services Implementation Organization and Processes • Transaction Centric (Business Service ≈ Business Transaction) • Use Modern Commercial Products and IDEs (SE is the programmer) • Define Design Rules To Exploit Services

17. Value of System Engineering • Insure Return on Investment in SOA • Change Business Processes to Yield Return • Cost of Services Acquisition / Operation Yields Return • Cost of SOA Development Method Yields Return • Cost of System Engineering Yields Return • Reduce Risk of Failure / Lost Business Opportunity • Business is Prepared To Exploit New ICT • Expected Composite Application Delivered • Privacy and Availability Goals are Met