+ All Categories
Home > Documents > Webinar: Integrating the TOGAF® Standard with the BIAN ... · PDF fileTOGAF is the Leading...

Webinar: Integrating the TOGAF® Standard with the BIAN ... · PDF fileTOGAF is the Leading...

Date post: 03-Feb-2018
Category:
Upload: vudiep
View: 213 times
Download: 0 times
Share this document with a friend
32
Webinar: Integrating the TOGAF® Standard with the BIAN Service Landscape Dave Banko, BIAN Programme Manager Paul Bonnie, ING, on behalf of BIAN Thomas Obitz, KPMG, on behalf of The Open Group November 18, 2013
Transcript

Webinar: Integrating the TOGAF® Standard with the BIAN Service Landscape

Dave Banko, BIAN Programme Manager Paul Bonnie, ING, on behalf of BIAN Thomas Obitz, KPMG, on behalf of The Open Group November 18, 2013

Copyright BIAN 2013 | Banking Industry Architecture Network

Webinar Agenda

§ BIAN Welcome & Introduction §  Integrating the TOGAF® Standard with the BIAN Service Landscape

§ The BIAN Organization

§ How to Become a Member?

§ Wrap-up & Closure

§ Appendix: Detailed mapping of BIAN deliverables on TOGAF framework

2

Copyright BIAN 2013 | Banking Industry Architecture Network

A Warm Welcome to YOU – Dialing in From:

India

Germany Switzerland

Mongolia Netherlands

Ireland

UK

U.S.

Greece

Venezuela

Romania

Spain

Iceland

Italy

Belgium

Poland

France

Honduras

Canada

Mexico

Greece

Croatia

Germany Norway Sweden

Canada

USA

Netherlands

India

Denmark

Belgium Poland

Czech Republic

Spain

Switzerland

Colombia

UK

Ireland

Romania

Russia

Australia South Africa

Austria

Argentina

Costa Rica

Italy

New Zealand

Iceland

Mexico

Brazil

Qatar

Malaysia

Hungary

Moldavia

Portugal

Slovenia

Slovakia

Philippines

3

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN’s Mission

Central objectives for IT in the banking industry are the reduction of integration costs and the utilization of the advantages of a service oriented architecture (SOA). BIAN is defining a common yet exceedingly flexible SOA framework for the banking industry with the goal of establishing a common language. Based on broad consensus within the banking industry, this will enable faster, more efficient strategic and operational changes in banks while helping banks to address the key market imperative to drive cost reductions through greater efficiency and organizational flexibility. BIAN is a global, open, independent and unique community where banks, software providers and system integrators openly exchange Banking IT requirements with regard to SOA.

4

Copyright BIAN 2013 | Banking Industry Architecture Network 5

BIAN Vision

Today BIAN envisions a SOA-enabled banking industry with both internal and industry-wide agility and flexibility. BIAN supports banks to define their internal services based on industry collaboration and best practices.

2014 Banks are enabled to develop their

semantic service definitions on a consistent basis through BIAN to enable internal and

commercial SOA-based solutions according to a standardized industry model.

Indu

stry

SO

A-F

ocus

Standard

Internal SOA-Focus Proprietary Best practices

BIAN 2014

Inte

rnal

E

xter

nal

Indu

stry

SO

A-F

ocus

Standard

Internal SOA-Focus Proprietary Best practices

Inte

rnal

E

xter

nal Majority

of Banks BIAN today

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN Members BIAN  &  Financial  Ins.tu.ons   BIAN  &  Partners  

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN and other standards are complementary

BIAN key points §  Distinct application to application (A2A)

focus, which complements the business-to-business (B2B) focus of IFX and SWIFT

§  Total focus on semantic definitions - technical definitions are excluded from official work products (helps to balance other industry efforts that, while not excluding semantics, have historically focused on technical specifications)

§  BIAN, IFX, and the OMG Finance Domain Task Force recognize ISO 20022 standard and the SWIFT-administered ISO 20022 Repository key to keeping standards bodies in the finance sector aligned with one another

§  Service-oriented, whereas IFX, SWIFT, and ISO 20022 are message-oriented

§  UML is a foundational technology, heavily used in the financial services industry

A B = A aligns with B

A B = A contributes to B

BIAN

IFX IFX

ISO 20022 Repository

(SWIFT Administered)

OMG Finance DTF

ISO 20022 Core Standard

OMG UML

A2A B2B

Business Content: Technical

Business Content: Semantic

Modeling Languages/ UML Profiles

= Service Oriented

= Message Oriented

= Process Oriented

7

EDM Council FIBO

= Language Oriented

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN Service Landscape Roadmap

June 2012 February 2013 Q1 2014 Q1 2015

SL 1.6 17 Service Domains

defined Revised / simplified “How

to Guide” Metamodel Aligned

SL 2.0 Total of 63 Service Domains defined

Metamodel Aligned All deliverables

available in HTML and UML

SL 3.0 Total of 210 Service

Domains defined (All bank functionality)

Banking Domains Completed

Metamodel Aligned Results of new Working Groups in the Business

Support Area New Set-up of the “How to

Guide”

SL 4.0 All Service Domains

defined

All Banking Functionalities

Defined

8

September 2013

SL 2.5 Total of 93

Service Domains defined

Metamodel Aligned

All deliverables available in

HTML and UML

NEW

Copyright BIAN 2013 | Banking Industry Architecture Network

Webinar Agenda

9

§ BIAN Welcome & Introduction §  Integrating the TOGAF® Standard with the BIAN Service

Landscape

§ The BIAN Organization

§ How to Become a Member?

§ Wrap-up & Closure

§ Appendix: Detailed mapping of BIAN deliverables on TOGAF framework

Integrating the TOGAF® Standard with the BIAN Service Landscape Paul Bonnie, ING, on behalf of BIAN Thomas Obitz, KPMG, on behalf of The Open Group November 18, 2013

Copyright BIAN 2013 | Banking Industry Architecture Network

The current challenges in the banking landscape require Enterprise Architecture to manage change

11

Significant challenges in the Banking ecosystem

Transformational changes are inevitable

Enterprise Architecture is key in enabling change

Bring together two industry frameworks for content

and methodology to speed up work and improve quality and consistency

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN – A Business Service Model for the Banking Industry

12

BIAN Service Landscape

BIAN Meta Model

BIAN Service Domain

Definitions

Community of banks, service providers and software vendors

Industry-wide consensus regarding SOA for banking systems, aligned

with the business objectives of agility and reduced cost

Vision

BIAN Business scenarios

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN – Service Landscape 2.0

13

Business Area

Business Domain

Service Domain

The

BIA

N S

ervi

ce L

ands

cape

is a

refe

renc

e fr

amew

ork

cont

aini

ng a

ll of

the

iden

tifie

d B

IAN

Se

rvic

e D

omai

ns o

rgan

ized

for e

ase

of a

cces

s

Copyright BIAN 2013 | Banking Industry Architecture Network 14

BIAN – HTML View of the Service Landscape 2.0

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN – Business Scenario

15

BIA

N B

usin

ess

Scen

ario

: An

exam

ple

of h

ow

sele

cted

BIA

N S

ervi

ce D

omai

ns m

ight

wor

k to

geth

er in

the

hand

ling

of s

ome

busi

ness

eve

nt

Copyright BIAN 2013 | Banking Industry Architecture Network

TOGAF is the Leading Framework for Enterprise Architecture

16

•  TOGAF adoption has grown tremendously over the years

•  Created and continuously developed by the Open Group, an industry consortium

•  TOGAF is industry independent

•  TOGAF includes •  Process •  Content •  Governance •  Reference Models

(technical)

Copyright BIAN 2013 | Banking Industry Architecture Network

Key components of TOGAF are the ADM, the Content Framework and the Enterprise Continuum

17

The Architecture Development Method is

the core of TOGAF. It describes how to develop and manage an Enterprise

Architecture

The content framework provides a structural model for architectural content that allows the major products an architect creates to be

consistently defined, structured, and presented.

The Enterprise Continuum describes a view of the Architecture Repository, classifying architecture products, showing how

these products evolve, and how they can be leveraged

and re-used.

Copyright BIAN 2013 | Banking Industry Architecture Network

The BIAN Deliverables integrate with the TOGAF Content Metamodel

18

BIAN Business Scenarios

BIAN Business Objects

BIAN Service

Landscape

BIAN Service Domain & Service

Landscape design

principles

Copyright BIAN 2013 | Banking Industry Architecture Network

The BIAN deliverables align well with the phases of the ADM

19

Consider BIAN as framework

(part of) Overall BIAN Service Landscape

BIAN Business Scenarios and BIAN Service Landscape (Business areas &

Business domains)

BIAN Service Domains (Reusable building blocks related to application

components and data entities)

BIAN Service Landscape to assess compliance of vendor packages

Copyright BIAN 2013 | Banking Industry Architecture Network

Webinar Agenda

20

§ BIAN Welcome & Introduction §  Integrating the TOGAF® Standard with the BIAN Service Landscape

§ The BIAN Organization

§ How to Become a Member?

§ Wrap-up & Closure

§ Appendix: Detailed mapping of BIAN deliverables on TOGAF framework

Copyright BIAN 2013 | Banking Industry Architecture Network

The BIAN Organization

New Working Groups

21

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN Board of Directors

22

David Vander General Manager of Services APAC,

Microsoft Corp.

Steve Van Wyk (Chairman) Executive Vice President, Head of

Operations and Technology, PNC Financial Services Group, Inc.

Jochen Schneider Head of SunGard

Retail Banking SunGard Financial Systems

DonTrotta Global Head of Banking Industry Development ,

SAP AG

Chae An Vice President Financial Services Solutions

IBM Software Group

Peter van Buuren Global CIO Commercial Banking Services ,

ING Bank

Copyright BIAN 2013 | Banking Industry Architecture Network

Webinar Agenda

23

§ BIAN Welcome & Introduction §  Integrating the TOGAF® Standard with the BIAN Service Landscape

§ The BIAN Organization

§ How to Become a Member?

§ Wrap-up & Closure

§ Appendix: Detailed mapping of BIAN deliverables on TOGAF framework

Copyright BIAN 2013 | Banking Industry Architecture Network

BIAN’s Internal Wiki and Official Homepage

24

Copyright BIAN 2013 | Banking Industry Architecture Network 25

Intellectual Property and Membership Fees

Intellectual Property § BIAN Intellectual property policy

§ WG membership triggers IPR Policy

§ Members surrender IP on contributions to WG’s

§ Members warrant that all WG contributions are their IPR

§ BIAN deliverables are royalty free

Fees (annual membership) Software / Tech vendors / Integrators §  (250 employees or more)

§  EUR 30.000,- / $ 40,000.=*

Banks / FI’s that are not vendors §  EUR 20.000,- / $ 27,000.=*

Software / Tech vendors / Integrators §  (less than 250 employees) §  EUR 10.000,- / $ 13,500.=*

Federal Banks / Central Banks §  EUR 10.000,- / $ 13,500.=*

Academic Partners §  EUR 0,- Visit www.bian.org

* Depending on the exchange rate

Copyright BIAN 2013 | Banking Industry Architecture Network 26

Model for Gradually Increased Engagement in BIAN

§  See above – in addition: §  Active engagement in 1 Service Definition Working Group / 1 Architecture Working, for

example:

§  Service Definition Group: WG Business Partner or Lending §  Architecture: Service Landscape (alternatively: Architecture Framework and

Foundation)

§  Active engagement in area relevant to Member

§  In addition approx. 20 §  PDs*) per working group per

year (mainly virtual collaboration)

§  *) PDs = Person Days

Engagement Level 3: Active Contribution

§  6-9 PDs*) per member representative per year

§  Member contributing membership fee to support funding of third party resources §  Access to BIAN internal wiki, including work in progress (e.g. documents currently under

review)

§  Engagement limited to participation in physical BIAN Core Team Meetings §  Upcoming BIAN Introduction Day: March 25, 2014 at SWIFT, New York City §  The BIAN CoreTeam Meeting: March 26 - 28, 2014 at SWIFT, New York City §  If you are interested in joining us: please send an email to: [email protected]

Engagement Level 1: Membership and Limited Engagement §  Financial and Marketing Support

§  Network

§  See above – in addition: §  Participation in Document reviews – Contribution to Quality Assurance

§  Virtual or physical review sessions with other subject matter experts §  Recently finalized documents prior to final approval and publication

§  Guidance through Participation in Reviews

§  In addition approx. 2 §  PDs*) per expert review:

Prep., guidelines, review)

Engagement Level 2: Participation in (virtual) Reviews

Copyright BIAN 2013 | Banking Industry Architecture Network 27

Questions?

Copyright BIAN 2013 | Banking Industry Architecture Network 28

Appendix Detailed mapping of BIAN deliverables on TOGAF

framework

Copyright BIAN 2013 | Banking Industry Architecture Network

Leveraging BIAN Deliverables with TOGAF (III) Details: Relating BIAN to the phases of the ADM (I)

29

Consider BIAN as framework: •  The existence of the BIAN network contributes to the awareness and

acceptance of an architectural approach; •  The use of the BIAN SOA Design framework and related deliverables

may be prescribed by the architecture; •  Decide whether or not to use BIAN input and principles during the

architecture work. (part of) Overall BIAN Service Landscape:

•  Assess the relevance and fitness-for-purpose of BIAN deliverables for this architecture work;

•  Use the relevant parts of the BIAN Service Landscape and BIAN Business scenarios to identify possible stakeholders;

•  Use the BIAN Service Landscape to identify architecture developments in related areas of the organization.

Copyright BIAN 2013 | Banking Industry Architecture Network

Leveraging BIAN Deliverables with TOGAF (IV) Details: Relating BIAN to the phases of the ADM (II)

30

BIAN Business Scenarios and BIAN Service Landscape (Business areas & Business domains)

•  Use the BIAN Business Scenarios as a starting point in defining the Baseline and Target Business Architecture;

•  Match the BIAN Business Scenarios to the internal (Baseline and Target) processes at the bank and determine potential gaps;

•  The BIAN Service Landscape is structured according to a common reference hierarchy: a business breakdown in Business Areas and Business Domains. Next to the BIAN Business Scenarios, also the BIAN Service Landscape can be used as a starting point for the set-up of the Target Business Architecture.

Copyright BIAN 2013 | Banking Industry Architecture Network

Leveraging BIAN Deliverables with TOGAF (V) Details: Relating BIAN to the phases of the ADM (III)

31

BIAN Service Domains (Reusable building blocks related to application components and data entities):

•  The BIAN Service Landscape can be used as a reference point for defining or assessing the Target Application Architecture;

•  The structure of the BIAN Service Landscape (Business Areas, Business Domains, Service Domains) can be applied to structure the Target Application Architecture;

•  The principles applied in constructing the BIAN Service Landscape can be translated into application and data principles;

•  The BIAN Service operations in the Target Application Architecture can be related to the Target Business Architecture, to relate business processes and applications, and to relate business objects and data;

•  The other way around, BIAN could benefit from this phase by updating the BIAN Service Landscape and the BIAN Business Scenarios with the output of this phase.

Copyright BIAN 2013 | Banking Industry Architecture Network

Leveraging BIAN Deliverables with TOGAF (VI) Details: Relating BIAN to the phases of the ADM (IV)

32

BIAN Service Landscape to assess compliance of vendor packages:

•  Are BIAN services, leveraged in previous ADM phases, also physically available in the market as COTS software solutions or application components?

•  The BIAN Service Landscape and BIAN Business Scenarios can be used as enablers for designing COTS software products for the financial industry;

•  The BIAN Service Landscape and BIAN Business Scenarios can be used in requirements gathering and vendor and package selections, assessing compliance of vendors and products with BIAN.


Recommended