Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
BIANIntroduction
BY
BABAK DARVISH ROUHANI (PHD)
SALEH RAD
1
2
Enterprise Architecture
Enterprise Architecture
3
Enterprise Architecture (EA) To align Business and Information Technology
To integrate environment for enterprise
EA define :
As-Is Architecture
To-Be Architecture
Migration Plan
Enterprise Architecture (Cont)
EA comprise
Framework
Methodology
4
Enterprise Architecture Framework (EAF) is
logical structure
Enterprise model
EA is designed, developed, managed, and maintained through
implementation methodology.
EA Implementation is effective when the intended EA’s goals are achieved.
5
Enterprise Architecture (Cont)
BIAN 8
6
7
8
- Enterprise Management and Controlling
- Product and Service Enabling
- Enterprise Enabling- Bank Operation- Customer and Sales- Channels
9
Developer Perspective
10
11
BIAN Business Services
DevOps Repository
IFW Tooling for REST API
Channel Apps
Leg
acy
Syste
ms
API Connect Tooling
Swagger/Stub
IFW Tooling
3rd PartyApps
AP
IP
latform
Develo
per
Port
al
Scala
ble
Runtim
e
Security
&
Contr
ol
Enterprise SOABusiness Process
Business Rules
Integration withESB
JavaScript/Java
BPEL/WSDL/JavaLinkage
Deploy
Banking APIsSupporting Services
Customized Integration
Banking Platform for APIs (Cloud or On Premise)
Open Banking APIs Model Driven Development
Case Study –
Model Driven Approach to BankingAPIs
13
Bank Perspective
14
Overview The BIAN Service Landscape provides a taxonomy of all business capabilities within a bank. Within
BIAN, each business capability is known as a Service Domain. The taxonomy enables the bank to
identify what technologies are satisfying a business capability. Often, a technology will span multiple
business capabilities. Depending on the desired result, this can be good or bad.
By leveraging interactions between Service Domains in order to satisfy a business process, banks are
able to break up the technologies that satisfy the capabilities. This results in a more component based, or
service-oriented, deployment.
Using the Service Domains of BIAN to establish the scope of an RFI/RFP enables a bank is able to
stay focused on how various vendors satisfy the capabilities desired.
15
16
Using The BIAN Service Landscape to Define Scope
17
Business Scenarios
18
Wireframes
19
Feature SetsService Domain Payment Order - Payment order provides a structured service to oversee
one or more payment transactions for a customer, taking into account customer specificrules
and constraintsN
on
-fu
ncti
on
al
Operational Features
Technical Architecture
Features
Key:Gap
Needs
Work
Covered
Dual operations control and user access configuration Extended office hours
Configurable workflow High availability/security High connectivity
Payment OrderFeature Description Vendor
A
Vendor
BFeature Types
Fu
ncti
on
al
Initialize & Register
Automated order capture (mutiple sources) Order details verification Batch/scheduled payment order capture (e.g. client ACH files) Deferred payment order capture (warehousing)
Invocation & Execution
Order repair Batch/scheduled payment order update ` ` Reversed order handling Network availaility update
Maintain & Analyze
Customer payment order entitlements/rules Payment order return for resubmission * OFAC/regulatroy checks/ Risk/limit checks and daylight overdraft/offset rules & off-line host support Maintain rule/format requirements (content/minimum requirements) Payment execution with payment preferences
Report & Notify
Customer payment order activity User defined reporting and UI field definition Notify rule/format requirements
Using BIAN as part of an RFI/RFP processIllustrative Bank Example
RFI/RFP approaches
“Are you BIAN compliant?”; “Are you BIAN certified?”
Structuring the RFI by BIAN service domains
Lessons learned from a vendor
Provides vendor a straight forward approach to understandscope
Quick and powerful communication vehicle for the vendor
Strong involvement of the bank’s architecture management teamhelpful
Look out for Core Banking analysts adopting BIAN
20
By leveraging the Service Landscape, Business Scenarios, Wireframes, and Feature Sets, a
Bank successfully defines scope and can assess vendor ability to meet the requirements of the
organization in a component based, or service-oriented approach.
21
Vendors Perspective
22
Overview
BIAN is ready to be used as a structural element within a bank’s business transformation
journey
From a vendor perspective BIAN helps articulating scope and strength of a vendors solution
It offers vendors the opportunity to utilize BIAN as a structural element of the vendor’s architecture
framework and business transformation methodology
23
24
The Banking Architecture Framework from SAP: SPRINT – Leveraging BIAN
Business Architecture
Business Process
Message Flow
Application Architecture
Capability Model
BIAN Service Landscape
Business Object Model
Customer
&
Segment
MICROSOFT
CORPORATION
En
te
rp
ris
eS
er
vic
es
Pr
od
uc
tF
ac
to
ry
Ch
an
ne
lS
er
vic
es
Ba
nk
in
gS
er
vic
es
an
dO
pe
ra
tio
ns
Pre-Sales
Assisted
Channels
Direct
Channels
Servicing
Pa
ym
en
ts
Origination
Sales / Cross Sale
Customer Information
Management
Operational Data ProductServices Mgmt. Management
Lending Products Deposit Products Trade Products
Billing and Merchant
Products
CapitalMarkets
Products
StrategyandMarket Financeand Risk
Technology & Operations Support
Analysis Accounting Management Marketingand
Communications
HumanResources
Mo
de
l B
an
k -
Bu
sin
es
s C
ap
ab
ilit
y
Mo
de
l
(Sa
mp
le V
iew
ON
LY
)
This model
and related
content is
property of
SAP.
Please do
not
distribute
outside
SAP.
Enhance
Foundati
onal
New
EoL/
Replace
Gap
# Initiative
Number
Business Capability
Heat-Map
Products
MaturityAnalysis
Introductory
Stage
Growth
Stage
Maturity
StageDeclineStage
Total
LifeCycle
Time
Dis
trib
uti
on
Ch
an
ne
lsA
na
lys
is
Sales Planning Execution
Business Case &
ValidationDesign & Blueprint Realization Run & OptimizationVision & Strategy
By using the BIAN deliverables you create a common language between the Bank and the
service Provider.
The BIAN Service Landscape provides a comprehensive “Bank on a Page” that enables
both Banks and Vendors to clearly define their agreed migration strategy.
25
Case Study
26
27
Business
Area
Business
Domain
Service
Domain
Business
Role TYPE
Service Operation
Full Name
Input
ParametersOutput
Parameters Comment
RUP- SOMA
30
RUP-SOMA
31
RUP-SOMA (Cont)
32
Discussion
33
Bank - EA
34
Q&A
35
36
Thanks