Enterprise Interoperability Basic Concepts and Definitions David Chen IMS-LAPS University Bordeaux 1 FRANCE.

Slides:



Advertisements
Similar presentations
Using Ontology for Improving Database Utilization This short presentation is merely about the benefits of ontology approach for database applications.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Doc.: IEEE /416r1 Submission November 2000 Richard Kennedy, Compaq Computer CorporationSlide 1 Items for Discussion SCOPE OF THIS EFFORT CRITICAL.
Enterprise Integration Architecture IPMA Professional Development Seminar June 29, 2006 Scott Came Director, Enterprise Architecture Program Washington.
0 General information Rate of acceptance 37% Papers from 15 Countries and 5 Geographical Areas –North America 5 –South America 2 –Europe 20 –Asia 2 –Australia.
28 October 2008CIS 340 # 1 Topics (continuing) To develop the concepts guiding SOA To define SOA components.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
6/2/2015Enterprise e-Support Inc.1 SoA (Service Oriented Architecture) Overview.
Standards & Enterprise Architecture for E-Governance Dr P.Madhav Institute for Electronic Governance.
Distributed components
Software Engineering Techniques for the Development of System of Systems Seminar of “Component Base Software Engineering” course By : Marzieh Khalouzadeh.
Thee-Framework for Education & Research The e-Framework for Education & Research an Overview TEN Competence, Jan 2007 Bill Olivier,
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Web Services Andrea Miller Ryan Armstrong Alex. Web services are an emerging technology that offer a solution for providing a common collaborative architecture.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Non-functional requirements
You’ve Built The Pieces, Now Integrate Your Enterprise! Mid-Atlantic Regional Conference January 17, 2003 Patty Gertz, Princeton University
Web Services Michael Smith Alex Feldman. What is a Web Service? A Web service is a message-oriented software system designed to support inter-operable.
ADML A result of cooperation and leverage! The Open Group W3C OMG MCC CMU.
Securing Legacy Software SoBeNet User group meeting 25/06/2004.
THE NEXT STEP IN WEB SERVICES By Francisco Curbera,… Memtimin MAHMUT 2012.
David Chen IMS-LAPS University Bordeaux 1, France
TDT4252/DT8802 Exam 2013 Guidelines to answers
DMSO Technical Exchange 3 Oct 03 1 Web Services Supporting Simulation to Global Information Grid Mark Pullen George Mason University with support from.
Enterprise Interoperability Basic Concepts, Definitions and Approaches
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Web Services Architecture1 - Deepti Agarwal. Web Services Architecture2 The Definition.. A Web service is a software system identified by a URI, whose.
CSE 303 – Software Design and Architecture
UNIT – II ARCHITECTING WEB SERVICES. WHAT ARE WEB SERVICES ? Web Services are loosely coupled, contracted components that communicate via XML-based interfaces.
® IBM Software Group © 2007 IBM Corporation J2EE Web Component Introduction
Introduction To System Analysis and Design
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
The Grid System Design Liu Xiangrui Beijing Institute of Technology.
7-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
SOA: An Approach to Information Sharing BJA Regional Information Sharing Conference Houston, TX February 7, 2007 Scott Came Director of Systems and Technology.
1 CIM OSA CIMOSA Computer Integrated Manufacturing Open System Architecture 1 David CHEN IMS-LAPS, University Bordeaux 1.
Illustrations and Answers for TDT4252 exam, June
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
W HAT IS I NTEROPERABILITY ? ( AND HOW DO WE MEASURE IT ?) INSPIRE Conference 2011 Edinburgh, UK.
SEMANTIC AGENT SYSTEMS Towards a Reference Architecture for Semantic Agent Systems Applied to Symposium Planning Usman Ali.
PDE3 – Frameworks for interoperability of Product Data in SME based environment Lecturer: Ricardo Gonçalves.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
United States Department of Justice Achieving Information Interoperability and Business Agility The Justice Reference Architecture:
Semantic Web: The Future Starts Today “Industrial Ontologies” Group InBCT Project, Agora Center, University of Jyväskylä, 29 April 2003.
ANKITHA CHOWDARY GARAPATI
GLOMAR Adaptive Consistency Control for Distributed File Systems Issues Current Distributed File Systems (DFS) are implemented on a mix of hardware platforms,
CS551 - Lecture 11 1 CS551 Object Oriented Middleware (III) (Chap. 5 of EDO) Yugi Lee STB #555 (816)
IT Service Specification Synchronicity Carl Mattocks OASIS BCM TC,co-Chair ebXMLRegistry Semantic Content SC, co-Chair ITIL Knowledge.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
A Mediated Approach towards Web Service Choreography Michael Stollberg, Dumitru Roman, Juan Miguel Gomez DERI – Digital Enterprise Research Institute
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
Cooperation & Interoperability Architecture & Ontology.
WG2 Roadmap Discussion Denise Warzel May 25, 2010 WG2 Convenor SC32 WG2N1424SC32 WG2N1424.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
Interoperability: Issues, Challenges, Solutions Bill Lober, MD MS Associate Professor, Health Informatics and Global Health Schools of Medicine, Nursing,
1 Acquisition Automation – Challenges and Pitfalls Breakout Session # E11 Name: Jim Hargrove and Allen Edgar Date: Tuesday, July 31, 2012 Time: 2:30 pm-3:45.
Managing Enterprise Architecture
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
Object Oriented Systems Design
Unit – 5 JAVA Web Services
Software Testing and Maintenance Designing for Change
مقدمه اي بر مهندسي نيازمنديها
CIGRE D2.24 Information Architecture ** where CIM fits in **
Inventory of Distributed Computing Concepts
Tools for Composing and Deploying Grid Middleware Web Services
Component--based development
System architecture, Def.
Presentation transcript:

Enterprise Interoperability Basic Concepts and Definitions David Chen IMS-LAPS University Bordeaux 1 FRANCE

Various views on interoperability The ambiguous definition of interoperability User’s expectations IT provider’s concepts Society view of interoperability Dream eBusiness eGouv ERP/CRM/SCM Collaborative work Seamless interactions Methodology Networked enterprise Service Oriented Architecture Agent technology XML/ebXML Middleware Integration Standards

Interoperability – general view Oxford: ‘able to operate in conjunction’. Webster: “ability of a system to use the parts of another system” Generally, “Inter-operate” implies that one system performs an operation on behalf of (or for) another system.

Interoperability - IEEE Definition Ability for two (or more) systems or components to exchange information and to use the information that has been exchanged IEEE standard computer glossaries (1990)

Interoperability – software view Two co-operating software can easily work together without a particular interfacing effort. It also means establishing communication and sharing information and services between software applications regardless of hardware platforms. In other words, it describes whether or not two software that were developed with different tools and from different vendors can work together.

Interoperability vs. portability the ease with which a system, component, data, or user can be transferred from one hardware or software environment to another. a quality metric that can be used to measure the effort to transport or convert the software for use in another environment The concept of interoperability is closely related to the concept of portability. TOGAF defined the portability as: Portability is the ability of data or system to be moved, and interoperability is the ability of software or systems to understand and use information coming from other software or systems.

Interoperability vs. interchangeability Interoperable ≠ interchangeable Interchangeable => replace a system or component to provide a same service with an equivalent behaviors (ex. response time) Interoperable => simply ability to exchange service without necessity to have the same behaviors.

Interoperability – system view Reversibility: Even if the implementation of the interoperability between partners leads to an adaptation or a modification of the systems, these systems have to be able to come back to their initial state at the end of the interoperation E1E2E1E2E1E2 Initial stateInteroperabilityInitial state

Interoperability vs. integration Interoperability has the meaning of co-existence and co- operation, while integration relates to the notion of collaboration and uniformalisation. In (Vernadat, 1996), interoperability is defined as the ability to communicate with another system and use the functionality of the other system => Interoperability = communication + interaction However, integration is more large and broad => Integration = communication + co-operation + co- ordination

Interoperability vs. integration INTEGRATIONINTEROPERABILITY Consistency between local and global objectives Do not seek for consistency Tightly coupled Two parts are inter-dependent loosely coupled Two parts are independent Decrease differences (languages, methods, tools,...) Identity and diversity preserved Intra-enterprise (Merge, restructuration, etc.) Inter-enterprise (Networked enterprise,…)

Interoperability ≠ collaboration Interoperability => has no direct business mission / goal => does not directly solve any business problem Two interoperable enterprises may not have any collaboration project Two enterprises in collaboration may have serious interoperability problems Interoperability vs. collaboration

Enterprise interoperability Ability of interaction between enterprises (or part of it). The enterprise interoperability is achieved if the interaction can, at least, take place at the three levels: data, application and business process with the semantics defined in a business context IDEAS Project