ICT

Integrated Enterprise Service Architecture

CE 2005 – Session S3 Enterprise Architecture Solutions for

Interoperability

Brian Elvesæter1, Rolf Kenneth Rolfsen1, Frank Lillehagen2, Dag Karlsen2

1 SINTEF ICT, P. O. Box 124 Blindern, N-0314 Oslo, Norway {brian.elvesater, rolf.k.rolfsen}@sintef.no 2 Troux Technologies AS, P.O. Box 482, N-1327 Lysaker, Norway {frank.lillehagen, dag.karlsen}@troux.com

ICT

Outline

Motivation 4-layered view of an enterprise Integrated Enterprise Service Architecture (IESA)

Service infrastructure and infrastructure services Business services Enterprise Knowledge Architecture (EKA) services Model-configured User-composable Platform (MUP) services

Conclusions

ICT

Motivation

Enterprise Challenges

Business agility Flexibility and adaptability

Enterprise architecture frameworks + Holistic approach + Different views of an enterprise as

related (visual) knowledge models - Current enterprise architectures are only

blueprints

ICT Challenges

Inflexible and difficult to adapt Enterprise application integration (EAI)

Service-oriented architecture (SOA) + Loosely coupled systems + Horizontal integration between different

business domains + Use case oriented service composition +/- Web services (enabling technology) - Discussion about architectural style

Requirements Enterprises require operational enterprise architectures ICT solutions must be designed to be inherently interoperable

ICT

4-layered view of an enterprise Business Operational Architecture

Enterprise Knowledge Architecture (EKA)

Information and Communication Technology (ICT) Architecture

Sem

antic

s

Software platforms

EKA services Business and user services

Modeling tools

Infrastructure services

Management tools

Nomenclatures Classifications

Ontology tools

Ontology services

Dictionaries Ontologies

Business terms Laws, rules, principles

Agreed norms and practices

Operations Strategy

Procedures and routines

Governance

Enterprise models

Metamodels and languages

Enterprise templates

Enterprise methodology

Reference architectures

Product models

ICT

Integrated Enterprise Service Architecture (IESA)

ICT

IESA: Service Infrastructure

Service Interoperability Management

Service Evaluation & Negotiation

Execution Environment 1

Service Interconnection Bus

Execution Environment N

Interoperability Management: Provides a standardized way of accessing and using services. A first version will be based on Web service technology.

Evaluation & Negotiation: evaluate and negotiate incoming service requests, make use of underlying infrastructure services, and direct requests to the appropriate service deployed on an execution platform.

Execution Environment: Concrete platform that is able to execute specific models, e.g. Business Process Execution Language (BPEL), Agent, or Composed Service models.

Service Interconnection Bus: provides middleware services for integrating the various execution platforms.

Examples of infrastructure services

QoS & security Resource mgt. Brokering Dynamic binding Repository

Intelligent agents Negotiation Service composition Matchmaking Registry

ICT

IESA: Enterprise (software) services

Business services provide the ‘units of business’ that represent value propositions within a value chain or within business processes. Fine-grained services can be used in the composition of higher-level business services required by different business use cases.

Legend

Shared and network-visible

service layer

Service consumers

a

User- composable service layer

Service providers

b c r

s t x y z

a b t z y r

x Business service providing functionality ‘x’ Traceability through layers

[used by | composed of | provided by]

Service composition

s

Integrated Web portal Rich client

y

z

c

Service dependency

1 … n m

Examples of business services (Product Portfolio Management)

Simulators Product dev. Monitor resources Project finance Project planning

Human resources Contract mgt. Team management Sales data Project management

ICT

IESA: Enterprise (software) services

EKA services allow enterprises to develop, maintain and evolve models and metamodels that fits the actual business operations.

Examples of EKA services

Business service link Property structures Type hierarchies Design patterns Metamodeling

Behavior Class structures Model views Templates Enterprise modeling

ICT

a y r SCM

z

SM

a

b

BPM1 BPMM1

a

b

a y r

z

Integrated PBM1 & SCM

SMM

SCMM

Model of business service

Model of service composition

Model of business process

Model of information object

Model – metamodel relationship

Reference to other metamodel

Legend SM: Service Model

SMM: Service Metamodel

SCM: Service Composition Model

SCCM: Service Composition Metamodel

BPM: Business Process Model

BPMM: Business Process Metamodel

a y r

Scenario: Combining different

metamodels, e.g. for modeling services, service compositions and business processes, which allows us to create integrated models where relationships between business processes and services can be described.

IESA: Example of EKA service (1)

Metamodel Integration

Service

Integrated BPMM1 & SCMM

ICT

IESA: Example of EKA service (2)

a

b

BPM1

Partial View1

b

c

BPM2

Partial View2

a c

b

Integrated View2

BPMM1 BPMM2

a

b

c

Integrated View1

Model of business process

Model of information object

Model of business process

Model of information object

Legend

BPM: Business Process Model

BPMM: Business Process Metamodel Model – metamodel relationship Reference to other metamodel

View Handling Service

Metamodel Mapping Service

BPMM12 Mapping

Scenario: Two client applications (e.g. modeling tools) used by two different users are used for monitoring/detailing overlapping business process models.

Metamodels mapping service is used to map two different metamodels of business process models. This mapping could be used in exchanging knowledge models between two different business process modeling tools.

View handling service can be used to manage different views of the same or overlapping business process models.

ICT

IESA: Enterprise (software) services

MUP services make use of knowledge models to generate business-oriented and context-aware graphical user interfaces specific to the roles defined within an enterprise.

Examples of MUP services

Rich client link Task views Workflow views User interaction

Reports Graphs Charts Web forms Generation of (Web) GUI components

ICT

IESA: Example of MUP service

Retrieve Project

Data Service

Business service EKA service MUP service

Legend Import Model Data

Service

Project Organization Model

Gantt Chart Model

Model Mapping Service

Class

Class1

Class2

Class3

Class4

Class5

*

*

*

*

AggregationPrefixClass1

0..1

*

Web Template for Gantt Charts

ID Task Name Start Finish Durationapr 2005

11 12 13 14 15 16 17 18 19 20 21 22 23 24

1 1d2005-04-112005-04-11Task 1

2 1d2005-04-112005-04-11Task 2

3 1d2005-04-112005-04-11Task 3

4 1d2005-04-112005-04-11Task 4

5 1d2005-04-112005-04-11Task 5

Web Form

Generation Service

Web Gantt Chart

XSLT

Scenario: How MUP, EKA and business services are combined in generating MGW GUI components, e.g. Gantt charts.

A business service is used to retrieve project data.

The project data is imported into the knowledge space of the IESA using the import model data service which creates a project organization model.

The data contained in the project organization model is mapped to a Gantt chart model using the model mapping service.

The Gantt chart model is used by the Web form generation service to generate the Web Gantt chart according to a Web template for Gantt charts.

ICT

IESA: User platforms

ICT

IESA: Model-generated workplace (MGW) M

GW

Kno

wle

dge

laye

r

100 90 80 70 60 50 40 30 40 50

ID Task Name Start Finish Durationapr 2005

11 12 13 14 15 16 17 18 19 20 21 22 23 24

1 1d2005-04-112005-04-11Task 1

2 1d2005-04-112005-04-11Task 2

3 1d2005-04-112005-04-11Task 3

4 1d2005-04-112005-04-11Task 4

5 1d2005-04-112005-04-11Task 5

GraphsGanttcharts

Webforms Reports

…

MUPservices

Knowledgemodels

b

c

a c

b

BPMM2

BPM2

Partial View2

Integrated View2

a

b

a yra yr

z

IntegratedBPMM1 & SCMM

IntegratedPBM1 & SCM

a yra yrSCM SCMM

z

SM SMM

MUPService

MUPService

MUPService

MUPService

ICT

Tools (as Rich Clients)

Integrated Enterprise Service Architecture

ATHENA Integrated Execution Infrastructure

Business Services

External System

EKA Services

(& Ontology Services)

MUP Services

Other Services

ATHENA Integrated Execution Infrastructure

Infrastructure Services

Legacy System

Commercial- off-the-shelf

MGWs (as Web Portals)

Model-Generated Web User Interfaces

Other Tools

Modeling Tools

(& Ontology Tools)

Service Interoperability Management

Service Evaluation & Negotiation

Execution Environment 1

Service Interconnection Bus

Execution Environment N

Repository Services

Registry Services

Tech

nica

l vie

w o

f an

IESA

ICT

Conclusions SOA approach to develop, change, and maintain ICT systems improves

interoperability Autonomous, shared, network-visible services Allows composition of higher-level services meeting user and business needs

Integrated Enterprise Service Architecture (IESA) Technical service-oriented software platform Specifies an integrated modeling and execution platform

Two mandatory enterprise service categories in any IESA EKA services are required services for developing and managing enterprise

knowledge assets MUP services are required in order to develop and manage model-generated

workplaces (MGWs) IESA enables enterprise architectures to be operational business tools Interoperability can be achieved on the knowledge layer through the use of

EKA services Align different knowledge representations through their metamodels

Future work includes finalizing the specification of the EKA, MUP and infrastructure services that constitute the core components of the IESA.

ICT

Questions?