Escolar Documentos
Profissional Documentos
Cultura Documentos
Software
ESTRUCTURA DEL CURSO
Sesiones
Sesiones
La falta de Aplicaciones
alineacin entre desintegradas
TI y el negocio (silos).
La falta de alineacin entre TI y el negocio
Duplicidad de datos y
funcionalidad
Organizacin funcional
de la empresa
Diferentes
departamentos para
diferentes funciones
Cada departamento
tiene su propio sistema
No existen procesos
Qu es Arquitectura Empresarial?
Arquitectura:
El Arte y Ciencia de disear para edificar y construir
Arquitectura Empresarial:
El Arte y Ciencia de disear estrategias de TI para las
empresas que innoven y agreguen valor
Por qu es necesaria Arquitectura Empresarial?
Requerimientos Stakeholders
logical layers,
Proceso tiers, Lenguaje
viewpoints/views
Modelos de Referencia
Requerimientos o Requisito
Seleccionar
Proyectos
Administrar Crear
Arquitectura Arquitectura
Comunicar
Arquitectura
Lenguajes y Modelos
http://msdn.microsoft.com/en-us/library/bb466232.aspx
Por qu se necesita un Framework?
AS-IS TO-BE
Arquitectura de Negocio Arquitectura de Negocio
proyecto
TO - BE
Proyectos
Arquitectura Empresarial
Business Architecture - Arquitectura de Negocio
Procesos
Objetivos
Entidades
Actores de
Informacin
Procesos en la Organizacin
Excelencia Operativa
Estandarizacin e
Integracin
Simplificacin
Digitalizacin de Procesos
Autoservicio
Empresa 5 ceros
0 Inventario
0 Papel
0 Retardo
0 Desperdicio
0 Errores
Que es un proceso de negocio o Business Process ?
La informacin es el mayor
activo de la empresa
Existen diferentes Master Data
Metadata
Analtica
dominios de informacin
Data
El modelo relacional y SQL no Data Data No
es lo nico que existe Estructurada Estructurada
Arquitectura de Informacin
Ontologas
MOF
Meta Modelo de Datos
ECORE
Entity framewo
Master Data
Metadata
Analtica
Data
Data Data No
Estructurada Estructurada
Application Architecture - Arquitectura de Aplicaciones
Cliente
GUI
Aplicacin
Monoltica Lgica
Servidor BD
Archivos
Describir la
infraestructura
tecnolgica
Servidores
Sistemas operacionales
Bases de Datos
Middleware
Redes
Canales
Routers
Firewalls
Ejemplo: Venta en mostrador
Descripcin de Negocio
Venta directa de productos especializados como:
empanadas, arepas, etc. Con una receta original
No existe ningn sistema de informacin
El segmento de clientes las personas que pasan
por la tienda
Propuesta de valor: la receta original y la atencin
por parte del dueo
Ventas diarias de 200 unidades
Ejemplo: Venta en mostrador
TO-BE
Proyecto N
AS-IS Proyecto 2
Proyecto 1
Acceso Web
Dispositivos Electrnicos
Tendencias Tecnolgicas
Anlisis de Brechas
Anlisis de Brechas
Hoja de Ruta y Gestin de Portafolio de Proyectos
Project Portfolio Management (PPM)
IBM Rational Software Conference 2009
Planificacin y
establecimiento de
roadmaps/planes de
proyectos de alto nivel
Project Portfolio Management (PPM)
Los proyectos son trabajos relacionados en el tiempo que
producen un nico resultado
Los programas son grupos de proyectos que pueden ser
gestionados en conjunto
Recursos compartidos
Dependencias
Fase 4
Valor
Valor
Fase 3
Optimizacin del Portfolio
Project lifecycle Cost/ROI
Valor y Riesgo del Proyecto
Fase 2 Resource capacity/demand
Proyectos/Programas redundantes
Proyectos no estratgicos
Proyectos de poco valor o de alto riesgo
Entorno de TI
Fundamentos
Conceptuales Requerimientos, Atributos de Calidad
Diseo
Dinmicas Humanas
TOGAF
An Overview of
TOGAF Version 9.1
44 Montgomery Street
Suite 960
San Francisco, CA
94104 USA
56
What is
TOGAF ?
TOGAF, an Open Group Standard:
A proven enterprise architecture methodology and framework used by the world's
leading organizations to improve business efficiency
The most prominent and reliable enterprise architecture standard, ensuring
consistent standards, methods, and communication among enterprise architecture
professionals
Enterprise architecture professionals fluent in TOGAF standards enjoy greater
industry credibility, job effectiveness, and career opportunities
TOGAF helps practitioners avoid being locked into proprietary methods, utilize
resources more efficiently and effectively, and realize a greater return on investment
The Origins of TOGAF
A customer initiative
A framework, not an architecture
A generic framework for developing architectures to meet
different business needs
Not a one-size-fits-all architecture
Originally based on TAFIM (U.S. DoD)
Member (End User) Driven
Customer members demand architecture standards
Customer members select TAFIM as preferred starting point
DoD Information Systems Agency (DISA) donate TAFIM as base
TOGAF first published
93 94
TOGAF 7 Technical Edition
96
01 02 03 TOGAF 9 Enterprise
06 09
11
Edition
TOGAF 9.1
TOGAF 8.1.1
The Interoperable Enterprise TOGAF 8 Enterprise Edition
Business Scenario First TOGAF Certification
first published Program Launched
Why TOGAF ?
A comprehensive Vendor, tool and
general method technology neutral
open standard
Complementary to, not
competing with, other Avoids re-inventing the
frameworks wheel
Tailorable to meet an
organization and Based in best practices
industry needs
Possible to participate
Available under a free in the evolution of the
perpetual license framework
TOGAF Momentum
More than 100,000 downloads
More than 220 corporate members of The Open Group Architecture Forum
61
TOGAF 9 Market Drivers
Ongoing quest for Boundaryless Information Flow
In a survey of members, the three most prominent views:
The need for closer alignment with the business
The desire for simple implementation, greater usability
The next version of TOGAF should be an evolution rather than a revolution
Consideration for different architectural styles, e.g. SOA
Security is an increasing concern for CIOs and Enterprise Architects due to disappearance
of traditional boundaries
Need for greater detail on Architecture Development Method (ADM)
62
Introducing TOGAF 9
Developed, reviewed and approved by a collaborative of 300 members from
some of the worlds leading IT customers and vendors
An evolution from TOGAF 8.1.1 that preserves existing investments
The core Architecture Development Method
Existing investment in people - knowledge and skills
Existing investment in tools
Expanded detail and clarification of existing proof points
Restructured for better usability
More focused on holistic enterprise change
Clear links between business and IT objects
Increased consistency of output
63
TOGAF 9.1
TOGAF 9.1 was released in December 2011
It is the first maintenance update to TOGAF 9
It is an upwards-compatible evolution from TOGAF 9, addressing
usage feedback and comments raised
It addresses over 400 comments received
Contains over 450 changes
TOGAF 9 Technical Corrigendum 1 (Document U112) is available
describing each change in detail
The TOGAF 9.1 Standard
Part I - Introduction
Example Guideline
Applying the ADM
Across the Architecture Landscape
Example Guideline
Categories of Stakeholder
Example
Technique
Architecture Content Framework
Provides a detailed model of architectural
work products, including Deliverables,
Artifacts within deliverables, and the
Architecture Building Blocks (ABBs) that
deliverables represent.
It drives for greater consistency in the
outputs of TOGAF
It provides a comprehensive checklist of
architecture outputs
It promotes better integration of work
products
It provides a detailed open standard for
how architectures should be described
It includes a detailed metamodel
Deliverables, Artifacts and Building Blocks
Full Content Metamodel with Relationships
The Enterprise Continuum
Architecture Repository
TOGAF Reference Models
Zachman Framework
Support or
Guidance
TOGAF 9
Other Frameworks
Federal Enterprise Architecture Framework
Complementary
ITIL
Framework, method
and resources
IT Service Management
Best Practice
TOGAF 9
COBIT
Modeling languages
Governance and and notation
control
Summary
TOGAF, an Open Group Standard, is
An effective, industry standard framework and
method for enterprise architecture.
Complementary to, not competing with, other
enterprise frameworks
A repository of best practice
Vendor, tool, and technology neutral
A framework and method for achieving the
Boundaryless Information Flow vision
For More Information . . .
P
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
For More Information . . .
P
P