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
ICT
 Challenges
 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
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
Operations
Strategy
Governance
Laws, rules,
principles
Agreed norms
and practices
Procedures
and routines
Business terms
Enterprise
methodology
Enterprise
models
Enterprise
templates
Metamodels
and languages
Product
models
Reference
architectures
Semantics
Enterprise Knowledge Architecture (EKA)
Dictionaries
Ontologies
Nomenclatures
Classifications
Information and Communication Technology (ICT) Architecture
Business and
user services
Infrastructure
services
EKA services
Ontology
tools
Software
platforms
Modeling
tools
Management
tools
Ontology
services
ICT
Integrated Enterprise Service Architecture
(IESA)
ICT
IESA: Service Infrastructure
Service Interoperability Management
Service Evaluation & Negotiation
Execution
Environment 1
Execution
Environment N
Service Interconnection Bus
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
Registry
Matchmaking
Service composition
Negotiation
Intelligent agents
Repository
Dynamic binding
Brokering
Resource mgt.
QoS & security
ICT
IESA: Enterprise (software) services
Rich
client
Service
consumers
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.
Usercomposable
service layer
r
a
Shared and
network-visible
service layer
a
Integrated Web portal
y
b
c
b
r
s
s
y
t
t
c
x
y
z
z
z
Service
providers
1
Legend
Business service
x providing
functionality ‘x’
Service
composition
…
n
m
Service dependency
Traceability through layers
[used by |
composed of |
provided by]
Examples of business services (Product Portfolio Management)
Project management
Sales data
Team management
Contract mgt.
Human resources
Project planning
Project finance
Monitor resources
Product dev.
Simulators
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
Enterprise modeling
Templates
Model views
Class structures
Behavior
Metamodeling
Design patterns
Type hierarchies
Property structures
Business service link
ICT
IESA: Example of EKA service (1)
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.
SM
SMM
Integrated
BPMM1 & SCMM
z
SCM
SCMM
r
a
Metamodel
Integration
Service
y
a
BPM1
BPMM1
r
y
b
a
Integrated
PBM1 & SCM
b
Legend
SM: Service Model
SMM: Service Metamodel
SCM: Service Composition Model
SCCM: Service Composition Metamodel
BPM: Business Process Model
BPMM: Business Process Metamodel
a
a r y
Model of business service
Model of service composition
Model of business process
Model of information object
Model – metamodel relationship
Reference to other metamodel
ICT
z
IESA: Example of EKA service (2)
Scenario: Two client applications
(e.g. modeling tools) used by two
different users are used for
monitoring/detailing overlapping
business process models.
BPMM12 Mapping
BPMM1
BPM1
BPMM2
BPM2
Metamodel
Mapping
Service
a
b
b
c
Partial View1
Partial View2
a
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.
c
b
View
Handling
Service
a
c
b
Integrated View1
Integrated View2
Legend
BPM: Business Process Model
BPMM: Business Process Metamodel
Model – metamodel relationship
Reference to other metamodel
Model of business process
Model of information object
Model of business process
Model of information object
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
Generation of (Web)
GUI components
Web forms
Charts
Graphs
Reports
User interaction
Workflow views
Task views
Rich client link
ICT
IESA: Example of MUP service
Scenario: How MUP, EKA and
business services are combined in
generating MGW GUI components,
e.g. Gantt charts.
Task Name
2005-04-11
2005-04-11
1d
2
Task 2
2005-04-11
2005-04-11
1d
3
Task 3
2005-04-11
4
Task 4
2005-04-11
2005-04-11
1d
5
Task 5
2005-04-11
2005-04-11
1d
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.
Class3
*
Class4
*
*
Duration
Task 1
Class5
Class2
Finish
1
*
Class
Start
0..1
*
AggregationPrefixClass1
Class1
2005-04-11
apr 2005
11
12
13
14
1d
Web
Form
Generation
Service
Gantt
Chart
Model
16
17
18
19
20
21
22
23
24
Web
Gantt
Chart
Web Template for
Gantt Charts
Model
Mapping
Service
Retrieve
Project
Data
Service
15
XSLT
ID
Project
Organization
Model
Legend
Business service
Import
Model
Data
Service
EKA service
MUP service
ICT
IESA: User platforms
ICT
Knowledge layer
MGW
IESA: Model-generated workplace (MGW)
Gantt
charts
Start
Finish
Duration
1
Task 1
2005-04-11
2005-04-11
1d
2
Task 2
2005-04-11
2005-04-11
1d
3
Task 3
2005-04-11
2005-04-11
1d
4
Task 4
2005-04-11
2005-04-11
1d
5
Task 5
2005-04-11
2005-04-11
1d
ID
Task Name
Web
forms
Graphs Reports
12
13
14
15
16
17
18
19
20
21
22
23
24
100 90
80 70
60 50
40 30 40 50
MUP
Service
MUP
Service
MUP
Service
MUP
Service
SMM
z
BPM2
b
SCM
a
SCMM
r
a
a
r
c
y
y
Partial View2
b
Integrated
PBM1 & SCM
MUP
services
BPMM2
Integrated
BPMM1 & SCMM
SM
…
apr 2005
11
z
a
Knowledge
models
c
b
Integrated View2
ICT
Technical view of an IESA
Tools (as Rich Clients)
Modeling Tools
(& Ontology Tools)
MGWs (as Web Portals)
Other
Tools
Model-Generated
Web User Interfaces
ATHENA Integrated Execution Infrastructure
Business
Services
Service Interoperability Management
Other
Services
Service Evaluation & Negotiation
Infrastructure
Services
EKA Services
(& Ontology
Services)
MUP
Services
Execution
Environment 1
Execution
Environment N
Registry
Services
Repository
Services
Service Interconnection Bus
ATHENA Integrated Execution Infrastructure
Integrated
Enterprise
Service
Architecture
External
System
Legacy
System
Commercialoff-the-shelf
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?
ICT