2004-05-06 An integration methodology based on the Enterprise Architecture 1

““We need the integration up and running tomorrow. We need the integration up and running tomorrow.

Can you do it?Can you do it?””

An integration methodology based onthe Enterprise Architecture

UK Academy for Information Systems 2004

Marta Guerra (mncg@netcabo.pt)

Miguel Pardal (mflpar@yahoo.co.uk)

Miguel Mira Silva (mms@dei.ist.utl.pt)

May 6th 2004

LisbonPortugal

2004-05-06 An integration methodology based on the Enterprise Architecture 3

Overview

• Organizational environment

• Enterprise Architecture

• Methodology

• Conclusions

2004-05-06 An integration methodology based on the Enterprise Architecture 4

Organizational environment

• Adaptive Enterprise– Challenges from environmental changes

• Enterprise Application Integration– Share data between applications– Integration barriers

• Technology• Syntax• Semantics

2004-05-06 An integration methodology based on the Enterprise Architecture 5

Enterprise Architecture Steven Spewak (1993)Enterprise Architecture Planning,

John Wiley & Sons

2004-05-06 An integration methodology based on the Enterprise Architecture 6

Integration with Enterprise Architecture• Semantic context:

– Enterprise Architecture Data dictionary

• Organization, Managementand Technologyperspectives

• People-centric approach

• Consider future developments and organizational change

2004-05-06 An integration methodology based on the Enterprise Architecture 7

Methodology phases

2004-05-06 An integration methodology based on the Enterprise Architecture 8

A – Problem definition

2004-05-06 An integration methodology based on the Enterprise Architecture 9

Integration problem• Identify applications:

– Integrated School Management System (ISMS)– Student Portfolios– Teacher portal

• Identify goal:– Assure coherent view of student data between

Portfolios and ISMS– Login into Teacher portal using user name and

password from ISMS

2004-05-06 An integration methodology based on the Enterprise Architecture 10

B – Applications analysis

2004-05-06 An integration methodology based on the Enterprise Architecture 11

InterviewApplication: Student PortfoliosStakeholders: Artur Ferreira da Silva (business); Mira da Silva (development)

Meeting date: August 2003

Application Goals: Portfolio are extra-curricula activities students perform to obtain credits. The application allows sign in, mechanisms for proposalaprovals, notifications by email and activities publishing.

Users: DEI’s students and lecturers

Technological Platform: Windows Platform - Microsoft .Net; SQL Server;

Development history: August 2003 – product development;

Suggested integrations: get students list from ISMS, submitt Portfolio information to ISMS, issue reports with student and lecturer data, validate user access in ISMS;

Documentation received: database scripts and application source code

2004-05-06 An integration methodology based on the Enterprise Architecture 12

Data linkingStudent Portfolios

2004-05-06 An integration methodology based on the Enterprise Architecture 13

Functionality linkingStudent Portfolios

2004-05-06 An integration methodology based on the Enterprise Architecture 14

Application linkingNon-aligned items

Aligned items

EA application linking

2004-05-06 An integration methodology based on the Enterprise Architecture 15

Semantic linking for other applications• Teacher Portal• Integrated School

Management System

2004-05-06 An integration methodology based on the Enterprise Architecture 16

C – Specification

2004-05-06 An integration methodology based on the Enterprise Architecture 17

Specification perspectives

• ER-I – Entity-Relationship for Integration– Data model

• DFD-I – Data Flow Diagrams for Integration– Functional model

2004-05-06 An integration methodology based on the Enterprise Architecture 18

ER-I example

2004-05-06 An integration methodology based on the Enterprise Architecture 19

DFD-I example

2004-05-06 An integration methodology based on the Enterprise Architecture 20

Transformation• Convert source schema instance to a target schema instance

2004-05-06 An integration methodology based on the Enterprise Architecture 21

D – Implementation

2004-05-06 An integration methodology based on the Enterprise Architecture 22

Implementation

• Use specification schemas

• Choose integration engine

• Example: webMethods– Doctypes– Flows– Adapters

. . .

2004-05-06 An integration methodology based on the Enterprise Architecture 23

Methodology phases

2004-05-06 An integration methodology based on the Enterprise Architecture 24

Integration scenario evaluation• Methodology proved beneficial in the following aspects:

– Deciding data and ownership by applications– Detecting non-aligned functionalities– Avoid many-to-many transformations using Enterprise Architecture data dictionary– Graphical schemas for faster comparison of solutions and enhance communication

between the project team

• The integration scenario also revealed some limitations of the methodology:– Initial investment to develop an Enterprise Architecture– Some Enterprise Architecture assumptions can be hard to satisfy with reasonable costs– Commitment must be assured for critical issues such as availability of source code and

realistic data for testing– Production applications may need to be modified to achieve better user-interface results

2004-05-06 An integration methodology based on the Enterprise Architecture 25

Conclusions: main contributions

• Semantic framing with the Enterprise Architecture– Enterprise Architecture data dictionary– Make coherent integration decisions

• Effort proportional to problem size

• Long term vision, short term response

2004-05-06 An integration methodology based on the Enterprise Architecture 26

Conclusions: future work• Apply methodology to integration scenarios

from different industries with different needs and more data, processes and applications

• Adjust production applications according to Enterprise Architecture

2004-05-06 An integration methodology based on the Enterprise Architecture 27

Questions & AnswersQuestions & Answers

Thank you for your attention. More information on: http://mega.http://mega.istist..utlutl.pt/~.pt/~mflparmflpar//integrationintegration/download./download.htmlhtml

Managers are rarely trained to Managers are rarely trained to optimizeoptimize the performance of the the performance of the organization organization as a wholeas a whole, and often are , and often are not given the means to do so (not given the means to do so (……))

Enterprise systems must be guided by Enterprise systems must be guided by a a shared visionshared vision of the objectives.of the objectives.

in in LaudonLaudon & & LaudonLaudon (200(20022))