Scribd
Upload
333 views24 pages

8-Simplified Enterprise Architecture

This document provides an overview of enterprise architecture and how it can be applied. It discusses key concepts like business capabilities, people, processes, technology, and information. The document then outlines the typical layers of an enterprise architecture - business architecture, application architecture, data architecture, technology architecture, and roadmap. For each layer, it discusses what should be defined or addressed. Finally, it provides samples of how enterprise architecture could be applied, including a sample project definition plan, roadmap plan, and risk log (RAID). The overall summary is that the document outlines a framework for developing an enterprise architecture, including defining each layer and providing iterative planning processes and examples.

Uploaded by

saifulaziz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
333 views24 pages

8-Simplified Enterprise Architecture

This document provides an overview of enterprise architecture and how it can be applied. It discusses key concepts like business capabilities, people, processes, technology, and information. The document then outlines the typical layers of an enterprise architecture - business architecture, application architecture, data architecture, technology architecture, and roadmap. For each layer, it discusses what should be defined or addressed. Finally, it provides samples of how enterprise architecture could be applied, including a sample project definition plan, roadmap plan, and risk log (RAID). The overall summary is that the document outlines a framework for developing an enterprise architecture, including defining each layer and providing iterative planning processes and examples.

Uploaded by

saifulaziz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

Dr. Ir. Heru Purnomo Ipung M.

Eng (July 2020)


Sample Usage
of Enterprise
Architecture
Architecture
Context can be
Business Drivers,
Gools, Issues,
Objectives,
Benchmark
Sample Usage
of Enterprise
Architecture
Key Points
Organization is a collection of business capabilities

Business Capabilities mainly consist of People, Process,


Technology and Information

There is NO IT Initiatives, buT ALL are business


initiatives. It is just happened that need IT and Digital
Technology
Sample:
Business
Capability Map
Sample:
A new
capability
model for
the
unsecured
lending
market
DATA (AS OF BIG DATA) CONNECTED TO
BUSINESS, APPLICATION AND TECHNOLOGY
CHALLENGES
Business

Data Application

Technology
Infrastructure

SOURCE: TOGAF
Towards a
Big Data
Reference
architecture.

A reference
architecture for big
data taken from
Soares [202, p.
239]
Steps
• Architecture Vision
• Business Architecture
• Application Architecture
• Data Architecture
• Technology Architecture / Infrastructure
• Roadmap
Architecture Vision
Solutions
Business, Application, Data and Technology

Value
Benefits, Cost, Risk

Internal
Stakeholders External
(Management, Employee,
(Customer, Market, Regulators etc)
Shareholders etc)
Business Architecture
Challenges Ranges
Readiness, Capacity,
Core/Non Core
Process - External / Internal

Business Time, Availability People - Structure, Skills, Organization

Capabilities Volume, Speed


Technology - Manual, Semi Manual,
Automated, Intelligent
Information - Data, Information,
Availability, Strategic
Knowledge
Transformation Needs

Maturity - Where we are, Where to go Complexity - What are the Gaps


Application Architecture : Enterprise Systems,
Software

ERP BPM CRM SCM PLM BI


(Enterprise (Business (Customer (Product
(Supply Chain (Business
Resources Process Relationship Lifecycle
Management) Intelligence)
Planning) Management) Management) Management)

When the When the What kind of What kind of What kind of What kind of
processes are processes are interaction interaction product transaction and
standards ? NOT standards ? tocustomers ? supply chain ? challenges ? analytics ?

Capability Needs
Functionality - Functions to support Feature - Level of implementation
business capability sophistication
Data Architecture
Data
Data
Business Business Transactional
Capability
Mapping Drivers Capabilities and Analytic
Capabilities

Data
Data
Capability Data Strategy Data Quality Data Analytic
Improvement Integration

Analytic
Capability Descriptive Data Diagnosis Predictive Prescriptive
Needs
Technology Architecture
Technology
Capability Mature, New, Emerging (Network, Server, Security)

Technology
providers External (Cloud, Outsource) Internal

Architecture IT Operation Qualities (Availability, Performance, Serviceability, Scalability,


Quality Reliability, Flexibility, Security etc)
Roadmap
List of Initiatives

Priority Management

Budget and Resources

RAID (Risks, Assumptions, Issues, Dependencies) Program and Change


Management
Sample Blueprint
• Architecture Vision
• Business Architecture
• Application Architecture
• Data Architecture
• Technology Architecture / Infrastructure
• Roadmap
Iterative Steps Architecture Process Planning Process
Strategy • Key Deliverables• Objectives and Goals
Business Objectives / Value
(Week 1) Propotitions • Key Initiatives
• Key Capabilities • Key Issues
• Migration Planning
Business Layer • Enterprise Capabilities • Business Capabilities (Business
(Week 1) • Application List Model Canvas)
• PPTI (People, Process, Technology
and Information)

Application Layer • Application Architecture • Identified Application Capabilities


(Week 2) • Data Architecture (New, Replace, Enhance and
Dismiss)
• Identified Data needed

Technology Layer • Technology Architecture (List) • Identified Technology Needed


(Week 2)

Roadmap • Key Initiatives • Architecture Gaps (Business,


(Week 3) • Roadmap (Iterative: Priority, Application and Technology)
Urgency, Constraint) • Identified Initiative to fill the gap

Finalization • Program Management • Project Definition Plan


(Week 4) • RAID (Risk, Assumptions, Issue,
Dependencies)
Strategy
to
Blueprint
Business
and IT
Alignment
Layered
Approach

Layer 0 Layer 1
(Initial Workshop) (Continous Learning / Coaching)
Project Description Issues/Gaps Addressed
nCurrently, the company does not support debit card product
Objective
Enhance core banking deposit application to
support marketing division to sell a debit card
facility to its customers. Benefits Risk
Scope nImprove bank image nChanges in Debit card
nDesign debit card functionality requirements nImprove customer service business requirement
nBuild and test nIncrease low cost of funds nHigh gap with issuer’s
proportion requirement (MAESTRO,
nRollout
VISA Electron)
Major Functions
nEnable customers to make purchase in
Dependencies
merchant site and use their debit card to debit
their funding accounts immediately nCore banking system implementation has been started.
nThe rationalization of Tandem to Stratus system
nDebit card can also be used to withdraw money

Sample: from ATM


Key Assumption
Project nAvailability of skilled personel
Estimated Effort
Estimated duration : 4 months
Definition
n
n Estimated Mandays : 200 mandays

Plan n Estimated Cost : USD 50,000


Sample:
Roadmap Plan
Visit Website : A Portal for Collaboration where all shareholders can
Sample: RAID collaborate, report and manage
Log
THANK YOU
Dr. Ir. Heru Purnomo Ipung M.Eng

You might also like