BIAN Introduction
BY BABAK DARVISH ROUHANI (PHD) SALEH RAD
1
BIAN Introduction BY BABAK DARVISH ROUHANI (PHD) SALEH RAD 1 - - PowerPoint PPT Presentation
BIAN Introduction BY BABAK DARVISH ROUHANI (PHD) SALEH RAD 1 Enterprise Architecture 2 Enterprise Architecture Enterprise Architecture (EA) To align Business and Information Technology To integrate environment for enterprise EA
BY BABAK DARVISH ROUHANI (PHD) SALEH RAD
1Enterprise Architecture
Enterprise Architecture
3
Enterprise Architecture (EA)
EA define :
Enterprise Architecture (Cont)
EA comprise
4
Enterprise Architecture Framework (EAF) is
EA is designed, developed, managed, and maintained through implementation methodology. EA Implementation is effective when the intended EA’s goals are achieved.
Enterprise Architecture (Cont)
and Controlling
Enabling
API Platform
Developer Portal Scalable Runtime Security & Control Enterprise SOA Business Process Business Rules Integration withESB JavaScript/Java BPEL/WSDL/Java Linkage Deploy Banking APIs Supporting Services Customized Integration Banking Platform for APIs (Cloud or On Premise) Open Banking APIs Model Driven DevelopmentCase Study – Model Driven Approach to BankingAPIs
Overview
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.
able to break up the technologies that satisfy the capabilities. This results in a more component based, or service-oriented, deployment.
stay focused on how various vendors satisfy the capabilities desired.
15Using The BIAN Service Landscape to Define Scope
Business Scenarios
Wireframes
Feature Sets
Service Domain Payment Order - Payment order provides a structured service to oversee
and constraints
Non-functional 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 Order Feature Description Vendor A Vendor B Feature Types Functional 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 requirementsUsing BIAN as part of an RFI/RFP process
Illustrative Bank Example
Bank successfully defines scope and can assess vendor ability to meet the requirements of the
Overview
journey
framework and business transformation methodology
23The Banking Architecture Framework fromSAP: SPRINT – Leveraging BIAN
Business Architecture Business Process Message Flow Application Architecture Capability Model BIAN Service Landscape Business Object Model C u s tomer & S e g m e nt MICROSOFT CORPORATION E n t e r p r i s e S e r v i c e s P r o d u c t F a c t o r y C h a n n e l S e r v i c e s B a n k i n g S e r v i c e s a n d O p e r a t i o n s P r eSales Planning Execution
Business Case& Validation Design & Blueprint Realization Run & Optimization Vision & Strategyservice Provider.
both Banks and Vendors to clearly define their agreed migration strategy.
25RUP-SOMA
31RUP-SOMA (Cont)
32Bank - EA
34Thanks