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

Slides:



Advertisements
Similar presentations
Presentation Title | Date | Page 1 Extracting Value from SOA.
Advertisements

Regnet Specification : Functional point of view REGNET.
Course: e-Governance Project Lifecycle Day 1
Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
INTRODUCING SOA AND WORKFLOW MODELING TO NON- TECHNICAL STUDENTS Bruce J. Neubauer University of South Florida.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 6 Initiating and Planning Systems Development Projects 6.1.
Viewpoint Consulting – Committed to your success.
Modern Systems Analysis and Design Third Edition
Analysis Concepts and Principles
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Waniwatining Astuti, M.T.I
Chapter 1: The Database Environment
Integrated Process Model - v2
Effective Methods for Software and Systems Integration
Tsinghua University Service-Oriented Enterprise Coordination Prof. Dr. Yushun Fan Department of Automation, Tsinghua University,
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 1 Chapter 5 Initiating and Planning Systems Development.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
CLEANROOM SOFTWARE ENGINEERING.
Requirements Analysis
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Chapter 6 Supporting Processes with ERP Systems Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 6-1.
Reducing ITS Project Risk By using and developing consensus based regional ITS architecture and a systems engineering process Robert S. Jaffe, Ph.D., CSEP.
Using Business Scenarios for Active Loss Prevention Terry Blevins t
Identify steps for understanding and solving the
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Michael deLamare Requirements Management Program Functions R-9.
SQI © T.P. Rout and Griffith University, 1996 A Unified Reference Model for the Processes of Software and System Life Cycles Terry Rout Software Quality.
Accounting Information System By Rizwan Waheed M.Com 710.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Service Oriented Architecture CCT355H5 Professor Michael Jones Suezan Makkar.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Company for Urban Innovative Transport (CUIT) 19/12/2007 Request for proposal.
1 July 26, 2008 Copyright © 2008 Joseph F Iaquinto, PE. All rights reserved. Enterprise Architecting For The System Engineer Introduction To ATutorial.
Message Broker
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
® IBM Software Group © 2004 IBM Corporation Developing an SOA with RUP and UML 2.0 Giles Davies.
Independent Insight for Service Oriented Practice Summary: Service Reference Architecture and Planning David Sprott.
NURHALIMA 1. Describe steps involved in the project initiation and planning process Explain the need for and the contents of a Statement of Work and Baseline.
Business ByDesign (Case Study) EGN 5621 Enterprise Systems Collaboration Fall, 2011.
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
Software Engineering Lecture 10: System Engineering.
Krishna Bakka 2/25/ OUTLINE: Understanding SOA Implementing SOA Current methodologies in SOA.
Information Systems Integration ERP EAI Source R. Meissonier How to rationalise the IS and business processes How to harmonize the several IT applications.
INCOSE IW12 MBSE Workshop 15 INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, PhD Raytheon
OUTCOMES OBJECTIVES FUNCTIONS ACTIONS TERRITORIES LOCATIONS MARKET SEGMENTS TIME LINESCHALLENGE IMPACT RESOURCESACTIVITIESCHANNELS RELATIONS PARTNERS CUSTOMERS.
Driving Value from IT Services using ITIL and COBIT 5 July 24, 2013 Gary Hardy ITWinners.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Enron Business Challenges EnronOnline has generated tremendous business value for Enron Maintaining liquidity is critical to sustaining value contribution.
ITEC 275 Computer Networks – Switching, Routing, and WANs
SQA project process standards IEEE software engineering standards
Supportability Design Considerations
Modern Systems Analysis and Design Third Edition
Chapter 6 Initiating and Planning Systems Development Projects
SQA project process standards IEEE software engineering standards
Rules within an Enterprise
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Lecture 6 Initiating and Planning Systems Development Projects
Modern Systems Analysis and Design Third Edition
Quality Assurance for Component-Based Software Development
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Chapter 6 Initiating and Planning Systems Development Projects
Presentation transcript:

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

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

© Joseph F Iaquinto, PE May 14, 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 – Vitria BusinessWare – IBM WebSphere – Oracle / Sun WebLogic – SOFTWARE ag WebMethods A software methodology facilitate composite application construction

© Joseph F Iaquinto, PE May 14, 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, Genesis Of Service Oriented Architecture Genesis of ADP Sales Finance & Accounting Procurement Manufacturing Transportation Customer Company A

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

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

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

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

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

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

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

© Joseph F Iaquinto, PE May 14, Key Applicable System Engineering Artifacts Preparation of System Architecture System Architecture Capability Viewpoint Date and Information Viewpoint Operational Viewpoint Services Viewpoint Standards Viewpoint Systems 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

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

© Joseph F Iaquinto, PE May 14, Key Applicable System Engineering Artifacts Preparation of the System Requirements Specification System Requirements Specifications Elaborate System Capabilities Define Constraints 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

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

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