1 EAI SOA Composite System A System Engineering

1 EAI / SOA Composite System A System Engineering Approach © Joseph F Iaquinto, PE May 14, 2012

2 Agenda • • • Establish Definition Objectives Genesis of Service Oriented Architecture Key Applicable System Engineering Artifacts Recommended System Engineering Practices © Joseph F Iaquinto, PE May 14, 2012

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 Business. Works – Vitria Business. Ware – IBM Web. Sphere – Oracle / Sun Web. Logic – SOFTWAREag Web. Methods • A software methodology facilitate composite application construction © Joseph F Iaquinto, PE May 14, 2012 3

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 © Joseph F Iaquinto, PE May 14, 2012

5 Customer © Joseph F Iaquinto, PE May 14, 2012 Finance & Transportation Manufacturing Procurement Accounting Sales Genesis Of Service Oriented Architecture Genesis of ADP Company A

Genesis Of Service Oriented Architecture A Driving Business Practice: Mergers and Acquisitions © Joseph F Iaquinto, PE May 14, 2012 Sales Finance & Accounting Company A Transportation Manufacturing Procurement Finance & Accounting Sales Customer Company B Composite Company From Mergers and Acquisitions 6

Sales Finance & Accounting Company A Transportation Manufacturing Procurement Finance & Accounting Sales Genesis Of Service Oriented Architecture A Driving Business Practice: Outsourcing Company B Composite Company For Duration of One Business Transaction © Joseph F Iaquinto, PE May 14, 2012 7

Genesis Of Service Oriented Architecture Discovering the Notion of a Business Service Request for Quotation (EDI 840) © Joseph F Iaquinto, PE May 14, 2012 Finance & Transportation Manufacturing Procurement Accounting Customer Sales Price Information (EDI 879) Company A 8

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

Where System Engineering Fits In The Challenge 10 SOA – EAI System Engineering Challenge Define Encapsulated Business Services Business Process Analysis (Operational Activities) Factoring Into Services (SW Components) CONOPS / Arch for Operations CONOPS / Arch for Development © Joseph F Iaquinto, PE May 14, 2012 Compose Applications from Encapsulated Business Services System (Composite Application) Architecture CONOPS System Requirements Specifications

Key Applicable System Engineering Artifacts The “Document” Tree System Engineering Management Plan System Architecture © Joseph F Iaquinto, PE May 14, 2012 CONOPS System Requirements Specification Test Plans and Procedures System Maintenance Plan 11

Key Applicable System Engineering Artifacts Topics to Address in the System Engineering Management Plan Define Organization of Organizations © Joseph F Iaquinto, PE May 14, 2012 Define Composite Change Management Scheduling and Resource Management Define Composite Technical Management 12

Key Applicable System Engineering Artifacts Preparation of System Architecture 13 System Architecture Capability Viewpoint • Consistent with CONOPS define Composite Application / System Capabilities • Identify Composite Resources © Joseph F Iaquinto, PE May 14, 2012 Date and Information Viewpoint • Composite Business Objects • Relationships with Enterprise Application Data Operational Viewpoint Services Viewpoint Standards Viewpoint Systems Viewpoint • 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

Key Applicable System Engineering Artifacts Preparation of the CONOPS 14 CONOPS Problem Statement • 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 © Joseph F Iaquinto, PE May 14, 2012 Key Concepts • 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 System Capabilities • 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 Scenarios • 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

Key Applicable System Engineering Artifacts Preparation of the System Requirements Specification 15 System Requirements Specifications Elaborate System Capabilities • 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 © Joseph F Iaquinto, PE May 14, 2012 Define Constraints • 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 Verification and Validation Methods • Composite level / business services functional and behavioral V&V • Composite organization maintenance V&V methods • Enterprise level contributing functional and behavioral performance V&V

Recommended System Engineering Practices Practical SOA / EAI System Engineering Principles Behavioral Oriented (Event / Response) Establish Business Need For “Reuse” of Encapsulated Systems Define New System in Terms of Existing Systems Use Products Not Standards Define Services Verify and Validation Organization and Processes Start with SOA Management Capabilities Level of Abstraction is Business Process NOT Software Modularization 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 Business Process Centric (Composite) © Joseph F Iaquinto, PE May 14, 2012 16

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 © Joseph F Iaquinto, PE May 14, 2012