Enterprise Architecture - E

Transcript

Enterprise Architecture - E
E. Somma
Enterprise Architecture
13/12/2007
1 / 28
Enterprise Architecture
Emmanuele Somma1
13 December 2007
c 2007 – Emmanuele ’exedre’ Somma
riproduzione integrale permessa con qualsiasi mezzo
1
Bank of Italy - Research Area Computer Support
E. Somma
Enterprise Architecture
13/12/2007
2 / 28
Part I
Enterprise Architecture
E. Somma
Enterprise Architecture
13/12/2007
3 / 28
What
from Wikipedia: Enterprise Architecture is the description of the (current/future)
structure
behaviour
of an organization’s
processes,
information systems,
personnel and
organizational sub-units,
aligned with the organization’s
core goals and
strategic direction.
E. Somma
Enterprise Architecture
13/12/2007
4 / 28
What
EA is associated strictly with information technology, but it relates more
broadly to the practice of business optimization in that it addresses
business architecture,
performance management,
organizational structure and
process architecture as well.
E. Somma
Enterprise Architecture
13/12/2007
5 / 28
Who
Modelling the Enterprise Architecture is becoming a common practice
within the U.S. Federal Government to inform the Capital Planning and
Investment Control (CPIC) process. The Federal Enterprise Architecture
(FEA) reference models serve as a framework to guide Federal Agencies in
the development of their architectures. The primary purpose of creating an
enterprise architecture is to ensure that business strategy and IT
investments are aligned. As such, enterprise architecture allows traceability
from the business strategy down to the underlying technology.
Companies such as BP, Intel and Volkswagen AG also have applied
enterprise architecture to improve their business architectures as well as to
improve business performance and productivity.
E. Somma
Enterprise Architecture
13/12/2007
6 / 28
FEA Business Reference Model
E. Somma
Enterprise Architecture
13/12/2007
7 / 28
FEA PMO
E. Somma
Enterprise Architecture
13/12/2007
8 / 28
FEA Compartments
E. Somma
Enterprise Architecture
13/12/2007
9 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
Zachman Framework for Enterprise Architectures, a taxonomy, really
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
Zachman Framework for Enterprise Architectures, a taxonomy, really
The Open Group Architectural Framework (TOGAF), a process, really
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
Zachman Framework for Enterprise Architectures, a taxonomy, really
The Open Group Architectural Framework (TOGAF), a process, really
The Federal Enterprise Architecture, a proscriptive methodology, really
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
Zachman Framework for Enterprise Architectures, a taxonomy, really
The Open Group Architectural Framework (TOGAF), a process, really
The Federal Enterprise Architecture, a proscriptive methodology, really
The Gartner Methodology, an enterprise architectural practice, really
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
IT systems that have become unmanageably complex and increasingly
costly to maintain.
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
IT systems that have become unmanageably complex and increasingly
costly to maintain.
Mission-critical information that is consistently out-of-date and/or just
plain wrong.
(Problem 2) Poor business alignement
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
(Problem 2) Poor business alignement
The organization isn’t able to respond to current and future market
conditions in a timely and cost-effective manner due IT systems.
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
(Problem 2) Poor business alignement
The organization isn’t able to respond to current and future market
conditions in a timely and cost-effective manner due IT systems.
A culture of distrust between the business and technology sides of the
organization.
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
(Problem 2) Poor business alignement
The organization isn’t able to respond to current and future market
conditions in a timely and cost-effective manner due IT systems.
A culture of distrust between the business and technology sides of the
organization.
(Promises) The same ever
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
reducing IT cost and complexity
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
(Long lasting approach) Twenty years of methodologies
(Problem 1) System Complexity
(Problem 2) Poor business alignement
(Promises) The same ever
reducing IT cost and complexity
increasing business value and effectiveness
E. Somma
Enterprise Architecture
13/12/2007
10 / 28
EA Timeline
E. Somma
Enterprise Architecture
13/12/2007
11 / 28
Thoreau Cabin
E. Somma
Enterprise Architecture
13/12/2007
12 / 28
Busan Lotte Tower - South Corea
E. Somma
Enterprise Architecture
13/12/2007
13 / 28
Zachman Framework Standard
E. Somma
Enterprise Architecture
13/12/2007
14 / 28
Part II
EA in Bank of Italy
E. Somma
Enterprise Architecture
13/12/2007
15 / 28
Modello di riferimento dei compiti della Banca d'Italia
Servizi per i
cittadini
Metodi di fornitura
Politica monetaria
Sistemi di pagamento
Banconote e monete
Statistiche
Formazione Economica e Finanziaria
Biblioteca
Museo della Moneta
Archivio Storico
Tesoreria per conto dello Stato
Cambio delle banconote e delle monete
Emissione e pagamento dei vaglia cambiari
Servizi di deposito
Esame delle banconote sospette di falsità
Centrale di Allarme Interbancaria
Centrale dei rischi
Servizi finanziari
Fornitura di servizi
Assistenza Finanziaria
Credito e Assicurazione
Trasferimenti allo stato
Servizi diretti ai cittadini
Creazione e gestione della conoscenza
Creazione e gestione di beni pubblici
Conformità e applicazione delle leggi
Supporto alla
fornitura dei servizi
Relazioni Legislative
Affari Pubblici
Sviluppo dei Regolamenti
Pianificazione e Allocazione delle Risorse
Gestione delle
Risorse Aziendali
E. Somma
Gestione della Catena di Fornitura
Gestione delle Risorse Umane
Gestione Finanziaria
Controlli e Supervisione
Riscossioni
Gestione dei Rischi
Gestione Amministrativa
Gestione dell'Informazione e della Tecnologia
Enterprise Architecture
13/12/2007
16 / 28
Modello di riferimento dei compiti
Modello di riferimento dei componenti di servizio
Di competenza della
Direzione Tecnica
Modello di riferimento dei dati
Modello di riferimento tecnico
E. Somma
Enterprise Architecture
13/12/2007
Architettura basata su componenti
Approccio guidato dai compiti
Modello di riferimento delle prestazioni
Di competenza dei
Proprietari delle
Linee di Business
17 / 28
Canali di Accesso e Trasmissione
Processi di
Business
Misure di
Performance
Servizi ai Clienti
Tipi di servizio
Servizi di Automazione dei Processi
Servizi di di Gestione del Business
Servizi di
Supporto
Servizi per gli Asset Digitali
Servizi di Analisi del Business
Servizi di Back Office
Componenti di Servizio
E. Somma
Enterprise Architecture
13/12/2007
18 / 28
Part III
EA in Research Area
E. Somma
Enterprise Architecture
13/12/2007
19 / 28
E. Somma
Enterprise Architecture
13/12/2007
20 / 28
E. Somma
Enterprise Architecture
13/12/2007
21 / 28
E. Somma
Enterprise Architecture
13/12/2007
22 / 28
E. Somma
Enterprise Architecture
13/12/2007
23 / 28
E. Somma
Enterprise Architecture
13/12/2007
24 / 28
E. Somma
Enterprise Architecture
13/12/2007
25 / 28
E. Somma
Enterprise Architecture
13/12/2007
26 / 28
E. Somma
Enterprise Architecture
13/12/2007
27 / 28
Enterprise Architecture
[email protected]
E. Somma
Enterprise Architecture
13/12/2007
28 / 28

Documenti analoghi

avviso di seminario

avviso di seminario degli elementi della strategia di business, del modello di business e delle tecnologie, politiche e infrastrutture di supporto. Esistono ormai alcune affermate metodologie per l'EA tra cui "The Open

Dettagli

Sul framework di Zachman

Sul framework di Zachman Sul framework di Zachman In http://en.wikipedia.org/wiki/Zachman_framework viene presentato il framework e la sua versione grafica con la spiegazione; da esso e’ tratto quanto segue: “The Zachman F...

Dettagli

ENTERPRISE ARCHITECTURE Parte II ENTERPRISE

ENTERPRISE ARCHITECTURE Parte II ENTERPRISE Enterprise Architecture è fondamentale per permettere a una Enterprise di assimilare i cambiamenti interni in risposta alle dinamiche e alle incertezze esterne. Non solo costituisce una base per la...

Dettagli