experiences with enterprise architecture using togaf and ibm rational system architect at dn b nor

June 5–9 Orlando, Florida

Experiences with Enterprise Architecture using TOGAF 9 and IBM Rational System Architect at the Norwegian Bank DnB NOR

James Dzidek, Ph.D.IT Consultant, Enterprise [email protected]

Lars JørgensenEnterprise Architect at DnB [email protected]

mailto:[email protected]


The Premier Event for Software and Systems Innovation

2© 2011 IBM Corporation

Outline

Short background on DnB NOR

DnB NOR’s expectations for Enterprise Architecture

Progress Status

Framework

How we explain our objectives and contribution

Where do we fit in the organization and existing processes?

Metamodel

What are we actually documenting, why and how?

Tool

How we use IBM Rational System Architect

Practical Challenges & Advice

Summary & Next Steps



Curriculum Vitae

CosmopolitanPoland, Italy, Canada, Norway, …? (somewhere warm)

EducationB. Eng. in Computer SystemsM. Eng. in Software QualityPh. D. in Software Engineering @ Simula Research Laboratory -

Thesis on the costs and benefits of using modeling techniques and tools

PositionsSystems Engineer @ Nortel NetworksTechnical Presales @ TelelogicTechnical Presales @ IBM Independent Consultant – Enterprise Architecture



Norway's leading financial services group

Total combined assets > 2 100 billion NOK

More than 2.3 million retail customers

Norway's largest Internet banks, dnbnor.no and postbanken.no, with more than 1.5 million users

More than 200 000 corporate customers

Norway's most extensive distribution network for financial services

Norway's largest life and pension insurance company with around 1 000 000 customers

Norway's largest asset management operation with more than 600 000 mutual fund customers in Norway and 283 institutional clients in Norway and Sweden

Norway's largest capital markets operation

Norway's leading real estate broker

More than 14 000 full-time positions (incl. DnB NORD)



….and the most international

Partner for Norwegian companies abroad and for large international companies in Norway

International network of 13 branches and representative offices

Private banking in Luxembourg

Operations in Poland and the Baltic states through DnB NORD

Presence in North-East Russia through DnB NOR Monchebank

Norway's leading foreign exchange bank

One of the world's foremost shipping banks

A major international player in the energy sector

http://intranett.dnbnor.no/NR/rdonlyres/04CC66E5-8249-4FB2-BA27-2CABCAAFA057/0/ICMglobusogkart.ppt



Maneuvered well through the financial crisis

Source: J.P.Morgan

No. 38

No. 22



A History of Mergers & Acquisitions

Merger 1990

Acquisition 1996

Merger 1999

Acquisition 2002

Acquisition 2003

Acquisition 1992

Merger 1990

Merger 2003

GjensidigeNOR ASA

DnCDnC

Bergen BankBergen Bank

Four large savings banksFour large savings banks

SparebankenABCSparebankenABC

DnB

ForenedeForsikringForenedeForsikring

VitalVital

DnBDnB

Postbanken

DnB

Skandia AMSkandia AM

DnB

GjensidigeLiv

GjensidigeLiv

Nordlands-banken

Nordlands-banken

DnB

SparebankenNOR

SparebankenNOR

DnB

Gjensidige NOR

SparebankenNOR

Den norskeHypotekforening

Gjensidige Bank/ Elcon Finans

Gjensidige NORSparebank

SparebankenOslo/AkershusSparebankenOslo/Akershus

FellesbankenFellesbanken

Merger 1985

Real KredittRealkreditt

Acquisition 1992

Gjensidige NORSpareforsikringGjensidige NORSpareforsikring

Acquisition 1992

Merger2002

Acquisition 1993

Acquisition 1999

De-mutualisation

De-mutualisation

Aquisition2005/2010

Aquisition2005



DnB NOR’s Expectations for Enterprise Architecture

See the various IT initiatives in context

Ability to translate business strategies in into optimal IT solutions

Help deal with frequently changing customer and business requirements

Expectation of faster completion of analysis since individual projects can utilize already-available data

Commitment to this effort:o Process governed and owned by the chief architect

o Involvement all the way from business decision-makers, via business architects, to solution architects and developers

o Team: project manager, subject matter experts, enterprise architects, consultants

o Dedicated Enterprise Architecture Tools



Progress Status

Tool Acquisition

Project Replanning

Pilot Phase Phase 1 Phase 2

• Initial Screening• RFP• Vendor negotiations• Vendor Selection

• Tool Deployment• Initial EA Training (selected resources)• Pilot Project Search

• 1 Pilot Project• Metamodel v 0.9• Tool

customization• Gain experience•EA Ground work (EA infrastructure)

• +2 pilot projects• Metamodel 1.0• Tool customization

•Plan “steady state”•Metamodel 2.0•Tool customization•General framework for accepting new projects

•Setting up reporting and publishing infrastructure



The Enterprise Architecture trinity

Framework Metamodel Tool EA trinity



Framework

Meta

model

Tool

EA trinity



Technology is an increasingly important competitiveness driver

Mobile Services

Collaboration & Mobility

CRM &

Business Intelligence

Sourcing

Architecture

Standardized Processes

http://www.google.no/imgres?imgurl=http://www.unc.edu/world/College_Updates_2009/world-globe.jpg&imgrefurl=http://www.careerealism.com/category/about-careerealism/&usg=__Oq_Y2ZnyMLMtb03Ggg2q8KsGuPk=&h=813&w=813&sz=125&hl=no&start=9&zoom=1&itbs=1&tbnid=xXDh0rVzONuoCM:&tbnh=144&tbnw=144&prev=/images?q=globe+future&hl=no&gbv=2&tbs=isch:1

http://www.google.no/imgres?imgurl=http://img.gfx.no/644/644293/mobiltkontor_topp.788x524!.jpg&imgrefurl=http://www.amobil.no/artikler/tele2_lanserer_surfepakker/72712&usg=__ctJf2c_vFSv05WhYnH2yxtQ8dU8=&h=524&w=788&sz=385&hl=no&start=31&zoom=1&itbs=1&tbnid=-uGujDyQ61KCrM:&tbnh=95&tbnw=143&prev=/images?q=mobilt+kontor&start=21&hl=no&sa=N&gbv=2&ndsp=21&tbs=isch:1

http://www.google.no/imgres?imgurl=http://www.auburnwa.gov/Assets/Administration/AuburnWA/Images/Twitter+logo.jpg&imgrefurl=http://www.auburnwa.gov/&usg=__zyipja7aYE2UqIVCGTI40ikE_Ic=&h=256&w=256&sz=59&hl=no&start=5&zoom=1&itbs=1&tbnid=DsqBAhl-uLAvBM:&tbnh=111&tbnw=111&prev=/images?q=twitter+logo&hl=no&gbv=2&tbs=isch:1

http://www.google.no/imgres?imgurl=http://www.textually.org/tv/archives/2010/06/07/facebook-logo.png&imgrefurl=http://www.textually.org/tv/archives/cat_youtube.html&usg=__NH5Bo4NRihOMyiQOPVmsfSWw0bQ=&h=256&w=256&sz=23&hl=no&start=4&zoom=1&itbs=1&tbnid=KFICJaE2iv0AvM:&tbnh=111&tbnw=111&prev=/images?q=facebook+logo&hl=no&gbv=2&tbs=isch:1



DnB NOR – Software dev. method



§§

Project 2

Project 1

Project 4

Project 3

E.Opportunities & Solutions

Project-DrivenArchitecture

Project 3

Project 2

Project 1

Architecture-DrivenProject Development



The TOGAF model in a system engineering model

Project 1

Project 2

Project 3

Project 4



TOGAF in the DnB NOR organization

• Enterprise architecture

• Long term perspective; 3-10 years

• Defines constraints, principles and goals for the blueprint groups

EA

• Portfolio different business areas with 0-3 years perspective

• TOGAFs segment architecture

• Defines required projects and their scope

• Secure that projects deliver in accordance to target blueprints

Portfolio Blueprint Group

• Deliver in accordance to specified scope and premises

• Projects are followed up by blueprint group with respect to defined constraints, goals etc.

Projects



Our message to the solution architects

EA is not about each project “looking at its neighbors”

It is not about coordinating project initiatives and governing them at group level

It is a holistic, top-down approach to implement the business strategy



Framework

Meta

model

Tool

EA trinity



DnB NOR’s Approach to Metamodeling

1. Start with usage scenarios – which questions do we need to answer in our Enterprise Architecture work?

2. Analyze which common information elements contribute to answering the usage scenarios

3. Seek to find the proper elements in the TOGAF 9 content metamodel or the built-in elements in the tool (Rational System Architect)

4. If not found – create a new element on basis of existing knowledge/resources

5. Specify the definition or adapt the default definition to our own organization

6. Define the associations between the elements



DnB NOR Metamodel

<<internal>>Appl ication

POS IDPOS Name

Subject Matter ExpertSystem Owner

Maintenance ResponsibleIT Unit

Last Update

<<togaf>>Organization Unit

Color Legend

<<togaf>>Technology Component

Platform Services

<<togaf>>BusinessProcess

<<togaf>>Business Function

<<internal>>Integration

<<togaf>>Business Service

SLA

<<internal>>Appl ication Service

<<internal>>Message

<<togaf>>Principle

<<internal>>Information

SystemProcess

<<togaf>>Constraint

InformationSystemProcessDiagram

<<internal>>Technology

Platform

<<togaf>>Information

System Service

BusinessProcessDiagram

<<internal>>Manual Activi ty

<<internal>>FunctionGroup

<<internal>>FunctionDomain

<<internal>>Architecture

Blueprint

<<internal>>Automated

Activi ty

<<togaf>>Role

<<togaf>>Actor

<<togaf>>Data Enti ty

<<togaf>>Product

Physical Service modelBlue Association: Transcends Business / IT

Border

supported byhas particluar importance for

constrains / directs

based on

1..*

deployed on

deployed on 0..*

bui l t up by

depends on

interacts via

travels across

1 1..*

provides and receives via an interface

1 1..*

depicted by1 1

belongs to

**

supported by **

performed by

contains

contains

conceptual ly depicted by

refined by

conceptual associations

participates in

owns

orchestrates0..*

produces

composed of

supports

can support

composed of

0..*

produces & distributes containsparticipates in

implemented by

serves/handles

involves

involves

is supported by

executed by

1..*

composed of

offers

supports

cal ls

0..*

A Function Group can belong to one and only one Function Domain.



BusinessArchitecture(Process / Org)

InformationArchitecture(Data / App)

TechnicalArchitecture

(Middleware / Platform / Network)

The Metamodel in Context

Color Legend



SLA

<<internal>>Application

POS IDPOS Name

Subject MatterExpert

System Ow nerMaintenance

<<togaf>>Function

<<togaf>>Information System

Service


Usage Prof ile

<<internal>>Function Group


Service


<<togaf>>Actor

<<togaf>>Process

<<togaf>>Product

<<togaf>>Role

<<togaf>>Data Entity

Light Grey: Ternary association

Physical Service model

Blue Association: Transcends Business / IT Border

interfaces associations

participates inowns

distributes

orchestrates

0..*

produces

composed of

supports

supports

composed of

0..*

producescontains

participates in

implemented by

serves/handles

involves

involves

is supported by

executed by

1..*

composed of

offers

supports

calls

0..*



Advantages of having an explicit metamodel

Greatly aids understanding

Greatly aids communication

Forms the basis for reports

Forms the basis for constraints



Principles

The metamodel will never be “complete”o Start with the most important projects and their analytical needs

o Projects can extend the metamodel for specific needs

o Harvest experience from the projects to corporate metamodel

Simplicity and maintainability over absolute truth

Minimize ambiguity and inconsistency

Base it on TOGAF 9’s content metamodel

Involve the customer (i.e. the projects)

If a repository should at the same time contain data at conceptual, logical and physical levels, there will be inconsistencies. In particular, models will not be perfect for all stakeholders, for all points of view, at all points in time.



Framework

Meta

model

Tool

EA trinity



International IT AS-IS

203 IBIS

ASAP-LC!

Zenit

921 TBI

405 Liquidity modul

580 DnB NOR Online

238 GL 161

Local reportingReporting

Norkom AML

Kalkmotor

711

KVH

Classify& index

Local printing

StorQM

Archiveservice

DocArc

Prang

Cross-key

789 Msg HUB/EPP

523 Merva479 WBI-FN

794 ProPay

406 Exchange rate

234 WallStreet 221 Wallis

890 Limit exposure

039 Input

023 Customer/004 Account

075/6 Acc.hier.

821 Limit check

255 IMEX

381 Aegis

Felix

811 Telebank

893BlueBox

Branches Customer

Corp.Lending

Finance

Trade Finance

CashPool

FX/MM

Payments-international

Internetbank

Payments-local

Archive /doc. production

DataWarehouse

Compliance

Reporting

183 ProSwitch

BACS UK

BEC Denmark

Inter bank transferSweden

BGC Sweden

Postgirot Sweden

LZB Germany

Finland

ACH Singapore

ACH (Wachovia) US

ACH US

ACH Chile

ACH China

ICP

FX/MM



International IT TO-BE

Int. HUB

ASAP-LC!

Zenit

580 DnB NOR Online

238 GL


Norkom AML

Kalkmotor KVH

Classify& index Archive

service

DocArc

Prang

Cross-key

789 Msg HUB/EPP

523 Merva479 WBI-FN

794 ProPay

406 Exchange rate


890 Limit exposure

039 Input


075/6 Acc.hier.

821 Limit check

255 IMEX

381 Aegis

Felix

811 Telebank

DLA

OnDemandDialogue

Branches Customer

Corp.Lending

Finance

Trade Finance

CashPool

FX/MM


Internetbank

Payments-local


DataWarehouse

Compliance

Reporting

542 C2B

183 ProSwitch

FLEXCUBE UBSFinArch?

BACS UK

BEC Denmark


BGC Sweden

Postgirot Sweden

LZB Germany

Finland

ACH Singapore

ACH (Wachovia) US

ACH US

ACH Chile

ACH China

ICP



“Architecting” in PowerPoint

Advantageso Quick and Easy: almost no training necessary

o Availability

o Flexibility

That’s great, but…o Alterations are difficult to perform

o Analysis are very difficult to perform: various views (dimensions)

o Inconsistency

o Ambiguity

o Version Control

o Collaboration

o Reuse of assets



ICP

Metamodel: What are we actually trying to model?

Int. HUB

ASAP-LC!

Zenit

580 DnB NOR Online

238 GL


Norkom AML

Kalkmotor KVH

Classify& index Archive

service

DocArc

Prang

Cross-key

789 Msg HUB/EPP

523 Merva479 WBI-FN

794 ProPay

406 Exchange rate


890 Limit exposure

039 Input


075/6 Acc.hier.

821 Limit check

255 IMEX

381 Aegis

Felix

811 Telebank

DLA

OnDemandDialogue

Branches Customer

Corp.Lending

Finance

Trade Finance

CashPool

FX/MM


Internetbank

Payments-local


DataWarehouse

Compliance

Reporting

542 C2B

183 ProSwitch

FLEXCUBE UBSFinArch?

BACS UK

BEC Denmark


BGC Sweden

Postgirot Sweden

LZB Germany

Finland

ACH Singapore

ACH (Wachovia) US

ACH US

ACH Chile

ACH China

<<internal>>ApplicationLandscapeAssociation


POS IDPOS Name

<<internal>>Scenario

containscontains




Associating Scenarios with Application

Interface toGL

161



Application Landscape: The Template



Application Landscape: Baseline



Application Landscape: Target



Management of Scenarios



Metamodeling


POS IDPOS Name



Last Update


Color Legend

<<togaf>>Technology Component

Platform Services

<<togaf>>BusinessProcess

<<togaf>>Business Function

<<internal>>Integration


SLA

<<internal>>Application Service

<<internal>>Message

<<togaf>>Principle

<<internal>>Information

SystemProcess

<<togaf>>Constraint

InformationSystemProcessDiagram

<<internal>>Technology

Platform

<<togaf>>Information

System Service

BusinessProcessDiagram

<<internal>>Manual Activity

<<internal>>Function

Group


<<internal>>Architecture

Blueprint

<<internal>>Automated

Activity

<<togaf>>Role

<<togaf>>Actor

<<togaf>>Data Entity

<<togaf>>Product

Physical Service modelBlue Association: Transcends Business / IT

Border

supported byhas particluar importance for

constrains / directs

based on

1..*

deployed on

deployed on 0..*

built up by

depends on

interacts via

travels across

1 1..*


1 1..*

depicted by1 1

belongs to

**

supported by **

performed by

contains

contains

conceptually depicted by

refined by


participates in

owns

orchestrates0..*

produces

composed of

supports

can support

composed of

0..*

produces & distributes containsparticipates in

implemented by

serves/handles

involves

involves

is supported by

executed by

1..*

composed of

offers

supports

calls

0..*



The Metamodel in SA Publisher



Message Sequence Diagram<<internal>>Application

POS IDPOS Name



Last Update

<<internal>>Application Service

<<internal>>Message

Physical Service model


1 1..*

offers

calls

0..*

App Service 2App Service 1

Get Customer Details Message



Workspace Strategy

Baseline v1

Architecture Development

v1.1


v1.2

Architecture Decided v1.1

Projects A

Project B

Production External Data System Development Baseline v2


v2.1

Production

External Data

System Development

Project B (Decided v1.1)




The EA repository will never be the only source of documentation. The metamodel must take this into account, by, for example, specifying where the documentation “master data” resides.o To have control, one must have a single metamodel that describes where all information

resides.

o Strategies for synchronization with those repositories must be put in place.

It is very difficult to guess what the corporate metamodel should be. It is better to establish a skeleton and then work with real projects.

Both, top-down and bottom-up approaches should be used when populating the repository.

EA must acquire a critical mass before clear benefits can be observed, first projects may not see all benefits

Must have a strategy for keeping content up to date

Avoid the tool-secretary trap! Instead create a framework where project members are trained and supported to use the tool themselves.



Summary & Next Steps

Short background on DnB NOR

DnB NOR’s expectations for Enterprise Architecture


Next Steps SA XT: Highly customized lightweight interface allowing passive users to update the

repository.

IBM Cognos Business Intelligence: Audit Reports

Framework

Metamodel

ToolEA

trinity



www.ibm/software/rational



© Copyright IBM Corporation 2011. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.




Contact Information

Lars JørgensenEnterprise Architect at DnB NOR

[email protected]

+47 9525 7514

James DzidekIndependent Consultant, Enterprise Architecture

[email protected]

+47 4889 4576





Daily iPod Touch giveaway

Complete your session surveys online each day at a conference kiosk or on your Innovate 2011 Portal!

Each day that you complete all of that day’s session surveys, your name will be entered to win the daily IPOD touch!

On Wednesday be sure to complete your full conference evaluation to receive your free conference t-shirt!

SPONSORED BY

experiences with enterprise architecture using togaf and ibm rational system architect at dn b nor

Documents