BRO 110: Reference Architecture

Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
1
Session: Reference Architectures
Reference Architectures
Open Group Reference Architecture

2
Welcome
in
An investment in knowledge
always pays the best interest
--- Benjamin Franklin

3
Objectives
✔ Get a general idea about :
➢ What a Reference Architecture might be good for
➢ An example of a Reference Architecture

4
Module
Reference Architecture(s)

5
It's getting harder
In all domains one can identify two simultaneous trends:
✔ Increasing complexity, scope and size of the system of interest, its
context and the organizations
creating the system
✔ Increasing dynamics and integration:
shorter time to market,
more interoperability, rapid changes
and adaptations in the field.

6
Reference Architecture
Is there a consistent notion of what this actually is:
✔ What is a Reference Architecture?
✔ Why do we need Reference Architectures?
➢ what is their value,
➢ what is the benefit of creating and
maintaining them?
✔ How do you capture a Reference
architecture?
➢ how do you visualize it,
➢ what is the appropriate level of
abstraction,
➢ how is it used?

7
What is it about?
✔ captures the essence of the architecture of a collection of
systems.
✔ provides guidance for the development of architectures for new
versions of the system or extended systems and product families.
✔ is created by capturing the essentials of existing architectures
and by taking into account future needs and opportunities, ranging
from specific technologies, to patterns to business models and
market segments.
A resource containing a consistent set of architectural best practices for use
by all the teams in your organization.
--- IBM, developerWorks

8
Business Architecture
More than a technical view
Customer Context Technical Architecture
Design PatternsEnterprise Users
Business Models
Design Patterns
Requirements

9
How to ...
Reference Architecture:
✔ Is based on proven concepts.
✔ Is more than just technologies and patterns
✔ Most often preceding architectures are
mined for these proven concepts.
✔ For architecture renovation and innovation validation
and proof can be based on reference implementations
and prototyping.
But:
✔ Reference Architectures are often associated with big
and inflexible frameworks
Gerrit Muller

10
How to ...
Existing
architectures
Architecture
Patterns
Customer &
Business
needs
Further
requirements
Reference
Architecture
mining
proven concepts vision
analysis
evolution triggering

11
Who?
✔ The Chief Architect (Business + Technical) owns the Reference
Architecture. Ownership is a critical success factor for a Reference
Architecture.
✔ Sponsorship of business managers for Reference Architectures is a
prerequisite. Such sponsorship works only if the Reference
Architecture provides value for the business.
✔ Reference Architectures are often related to organization
structures. This relationship between organization and architecture
is already a heated subject of discussion for actual architectures:
➢ Should the architecture follow the organization structure, or vice versa?
➢ Should we compromise architectural integrity to align better with the
organization?
➢ Or should we adapt the organization to serve the desired architecture?

12
Criteria for good Reference Architecture
✔ understandable for broad set of stakeholders
✔ accessible and actually read / seen by
majority of the organization
✔ addresses the key issues of the specific
domain
✔ satisfactory quality
✔ acceptable
✔ up-to-date and maintainable
✔ adds value to the business

13
Module
„It is not the strongest of the species that survive or the most
intelligent, but the ones most responsive to change“
--- Carles Darwin
Open Group

14
The Open Group
✔ Vendor- and technology-neutral consortium
✔ Vision to enable access to integrated information within and
between enterprises based on open standards and global
interoperability.
✔ Members:
Almost all majors including
➢ Capgemini (Netherlands)
➢ Hewlett-Packard (USA)
➢ IBM (USA)
➢ SAP (Germany)
➢ Sun Microsystems (USA)
➢ ...

15
Ups, so what is this?

16
So, what do we have here
Nine layers representing nine key clusters of considerations and
responsibilities that typically emerge in the process of designing an
solution or defining an enterprise architecture standard.
✔ Three of the layers address the implementation and interface
with a service (the Operational Systems Layer, the Service
Component Layer, and the Services Layer).
✔ Three layers support the consumption of services (the Business
Process Layer, the Consumer Layer, and the Integration Layer).
✔ Four layers support cross-cutting concerns of a more supporting
(sometimes called non-functional or supplemental) nature (the
Information Layer, the Quality of Service Layer, the Integration
Layer, and the Governance Layer).

17
Typical interaction between the layers
Consumer
Consumer
Layer
Integration
Layer
Business Process
Layer
Services
Layer
Component
Layer
OS
Layer

18
OS Layer
Capabilities:
✔ Service Delivery:
This category of capabilities is required for delivery of the
functional elements including the finding of the components
implementing the services, the wrapping and the composition/
decomposition of the underlying services, and the implementation
of the services.
✔ Runtime Environment:
This category of capabilities is required for providing a runtime
environment representing runtime infrastructure
✔ Virtualization and Infrastructure Services:
This category of capabilities provides underlying infrastructure such
as computing power, network, storage, etc. in native or a
virtualized manner.

19
Component layer
✔ This layer contains software components, each of which provides
the implementation or ―realization for services and their
operations
✔ The layer also contains the functional and technical components
that facilitate a service component to realize one or more services.
✔ Each service component fulfils the following goals:
➢ Realizes one or more services
➢ Provides an enforcement point for service realization
➢ Enables IT flexibility by strengthening the decoupling in the system, by
hiding volatile implementation details from service consumers

20
Component layer
Package X
Application Y
Service
Component
A
Application B
XML via http
Layer #1Layer #2

21
Services layer
✔ The Services Layer contains software components, each of which
provides the implementation or ―realization for services
and their operations.
that facilitate a service component to realize one or more services
✔ Services can be discovered and invoked,
or possibly choreographed to create
a composite service.
✔ Services are functions that are
accessible across a network via
well-defined interfaces of the
Services Layer.

22
Business Process Layer
Business processes are realized as compositions
(orchestrations, choreographies) of elements on services layer
✔ process representation and composition
✔ building blocks for aggregating loosely-coupled services as a
sequencing process aligned with business goals.
✔ enable interactions between services and business processes.
✔ within an enterprise
or across multiple
enterprises.

23
Consumer Layer
Provides capabilities to deliver required functionality and data
to service consumers
✔ Service consumers may be human users and applications
✔ Users may have preferences on how to
interact with functionality provided
➢ Portals
➢ Rich Internet Applications, RIA
➢ Interactive Voice Response, IVR
➢ API

24
Integration Layer
Realizes „communication infrastructure“ between service
requester/consumer and service provider
✔ Between service requester and provider
requests must be
➢ mediated
➢ transformed
➢ routed, and
➢ transported
✔ Business rules are made available consistently through all layers
(„cross-cutting architectural concern“)
✔ Centralization of management of business rules in this layer
prevents divergence or loss of consistent rules

25
What we will focus on ...
Consumer
Consumer
Layer
Integration
Layer
Business Process
Layer
Services
Layer
Component
Layer
OS
Layer

26
Review
Session Review:
✔ What is the purpose of a reference architecture?
✔ What is key to success for a reference architecture?
✔ Can you name some of the layers of the SOA reference
architecture?

Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 1
1
Session: Reference Architectures
Reference Architectures
Open Group Reference Architecture

2
Welcome
in
An investment in knowledge
always pays the best interest
--- Benjamin Franklin

3
Objectives
✔ Get a general idea about :
➢ What a Reference Architecture might be good for
➢ An example of a Reference Architecture

4
Module
Reference Architecture(s)

5
It's getting harder
In all domains one can identify two simultaneous trends:
✔ Increasing complexity, scope and size of the system of interest, its
context and the organizations
creating the system
✔ Increasing dynamics and integration:
shorter time to market,
more interoperability, rapid changes
and adaptations in the field.

6
Is there a consistent notion of what this actually is:
✔ What is a Reference Architecture?
✔ Why do we need Reference Architectures?
➢ what is their value,
➢ what is the benefit of creating and
maintaining them?
✔ How do you capture a Reference
architecture?
➢ how do you visualize it,
➢ what is the appropriate level of
abstraction,
➢ how is it used?

7
What is it about?
✔ captures the essence of the architecture of a collection of
systems.
✔ provides guidance for the development of architectures for new
versions of the system or extended systems and product families.
✔ is created by capturing the essentials of existing architectures
and by taking into account future needs and opportunities, ranging
from specific technologies, to patterns to business models and
market segments.
A resource containing a consistent set of architectural best practices for use
by all the teams in your organization.
--- IBM, developerWorks

8
Business Architecture
More than a technical view
Customer Context Technical Architecture
Design PatternsEnterprise Users
Business Models
Design Patterns
Requirements

9
How to ...
Reference Architecture:
✔ Is based on proven concepts.
✔ Is more than just technologies and patterns
✔ Most often preceding architectures are
mined for these proven concepts.
✔ For architecture renovation and innovation validation
and proof can be based on reference implementations
and prototyping.
But:
✔ Reference Architectures are often associated with big
and inflexible frameworks
Gerrit Muller

10
How to ...
Existing
architectures
Architecture
Patterns
Customer &
Business
needs
Further
requirements
Reference
Architecture
mining
proven concepts vision
analysis
evolution triggering

11
Who?
✔ The Chief Architect (Business + Technical) owns the Reference
Architecture. Ownership is a critical success factor for a Reference
Architecture.
✔ Sponsorship of business managers for Reference Architectures is a
prerequisite. Such sponsorship works only if the Reference
Architecture provides value for the business.
✔ Reference Architectures are often related to organization
structures. This relationship between organization and architecture
is already a heated subject of discussion for actual architectures:
➢ Should the architecture follow the organization structure, or vice versa?
➢ Should we compromise architectural integrity to align better with the
organization?
➢ Or should we adapt the organization to serve the desired architecture?

12
Criteria for good Reference Architecture
✔ understandable for broad set of stakeholders
✔ accessible and actually read / seen by
majority of the organization
✔ addresses the key issues of the specific
domain
✔ satisfactory quality
✔ acceptable
✔ up-to-date and maintainable
✔ adds value to the business

Java EE 5 Workshop - Brockhaus GmbH © 2009 - 13
13
Module
„It is not the strongest of the species that survive or the most
intelligent, but the ones most responsive to change“
--- Carles Darwin
Open Group

14
The Open Group
✔ Vendor- and technology-neutral consortium
✔ Vision to enable access to integrated information within and
between enterprises based on open standards and global
interoperability.
✔ Members:
Almost all majors including
➢ Capgemini (Netherlands)
➢ Hewlett-Packard (USA)
➢ IBM (USA)
➢ SAP (Germany)
➢ Sun Microsystems (USA)
➢ ...

15
Ups, so what is this?

16
So, what do we have here
Nine layers representing nine key clusters of considerations and
responsibilities that typically emerge in the process of designing an
solution or defining an enterprise architecture standard.
✔ Three of the layers address the implementation and interface
with a service (the Operational Systems Layer, the Service
Component Layer, and the Services Layer).
✔ Three layers support the consumption of services (the Business
Process Layer, the Consumer Layer, and the Integration Layer).
✔ Four layers support cross-cutting concerns of a more supporting
(sometimes called non-functional or supplemental) nature (the
Information Layer, the Quality of Service Layer, the Integration
Layer, and the Governance Layer).

17
Typical interaction between the layers
Consumer
Consumer
Layer
Integration
Layer
Business Process
Layer
Services
Layer
Component
Layer
OS
Layer

18
OS Layer
Capabilities:
✔ Service Delivery:
This category of capabilities is required for delivery of the
functional elements including the finding of the components
implementing the services, the wrapping and the composition/
decomposition of the underlying services, and the implementation
of the services.
✔ Runtime Environment:
This category of capabilities is required for providing a runtime
environment representing runtime infrastructure
✔ Virtualization and Infrastructure Services:
This category of capabilities provides underlying infrastructure such
as computing power, network, storage, etc. in native or a
virtualized manner.

19
Component layer
✔ This layer contains software components, each of which provides
the implementation or ―realization for services and their
operations
that facilitate a service component to realize one or more services.
✔ Each service component fulfils the following goals:
➢ Realizes one or more services
➢ Provides an enforcement point for service realization
➢ Enables IT flexibility by strengthening the decoupling in the system, by
hiding volatile implementation details from service consumers

20
Component layer
Package X
Application Y
Service
Component
A
Application B
XML via http
Layer #1Layer #2

21
Services layer
✔ The Services Layer contains software components, each of which
provides the implementation or ―realization for services
and their operations.
that facilitate a service component to realize one or more services
✔ Services can be discovered and invoked,
or possibly choreographed to create
a composite service.
✔ Services are functions that are
accessible across a network via
well-defined interfaces of the
Services Layer.

22
Business Process Layer
Business processes are realized as compositions
(orchestrations, choreographies) of elements on services layer
✔ process representation and composition
✔ building blocks for aggregating loosely-coupled services as a
sequencing process aligned with business goals.
✔ enable interactions between services and business processes.
✔ within an enterprise
or across multiple
enterprises.

23
Consumer Layer
Provides capabilities to deliver required functionality and data
to service consumers
✔ Service consumers may be human users and applications
✔ Users may have preferences on how to
interact with functionality provided
➢ Portals
➢ Rich Internet Applications, RIA
➢ Interactive Voice Response, IVR
➢ API

24
Integration Layer
Realizes „communication infrastructure“ between service
requester/consumer and service provider
✔ Between service requester and provider
requests must be
➢ mediated
➢ transformed
➢ routed, and
➢ transported
✔ Business rules are made available consistently through all layers
(„cross-cutting architectural concern“)
✔ Centralization of management of business rules in this layer
prevents divergence or loss of consistent rules

25
What we will focus on ...
Consumer
Consumer
Layer
Integration
Layer
Business Process
Layer
Services
Layer
Component
Layer
OS
Layer

26
Review
Session Review:
✔ What is the purpose of a reference architecture?
✔ What is key to success for a reference architecture?
✔ Can you name some of the layers of the SOA reference
architecture?

BRO 110: Reference Architecture

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie BRO 110: Reference Architecture

Ähnlich wie BRO 110: Reference Architecture (20)

Mehr von Brockhaus Consulting GmbH

Mehr von Brockhaus Consulting GmbH (15)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

BRO 110: Reference Architecture