pragmatic enterprise architecture
DESCRIPTION
Pragmatic Enterprise Architecture sounds like a contradiction, right? We'll explain how an Enterprise Architect can contribute to innovation instead of focussing on control the IT assets.TRANSCRIPT
Pragmatic Enterprise Architecture
KdG
12 12 12
Erik Lenaerts E2 Partners - Cronos
Enterprise Architecture
Minutes
The basics
An Enterprise is an organization engaged in the trade of goods, services, or both to consumers.
Architecture
ISO/IEC/IEEE 42010 defines
requirements on the description of
system, software and enterprise
architectures. It aims to standardise
the practice of architecture description
by defining standard terms,
presenting a conceptual foundation
for expressing, communicating and
reviewing architectures and specifying
requirements that apply to
architecture descriptions, architecture
frameworks and architecture
description languages.
simple is beautiful
CEO Jeff Dunham
CFO George Henry
CIO Ted Cooper
VP Marketing & Sales Karina Smets
VP HR Stef Peeters
IT Director Kurt Cremers
IT Ops Director Geert Bergs
Enterprise Architect Steven Hills
Why Enterprise Architecture?
Increasing complexity
Variation leads to complexity
Nha, that's not what I meant !
Yep, that's who I meant
C C ?
Data quality?
Application Silo
If you don’t know where you are going, you'll end up somewhere else
Application Modernisation
Too many different...
Operating Systems Database Management Systems Server makes Network components Monitoring tools
Client computers Anti Virus software Firewall components Development languages
...
• Read Only • Focused on companies • Owning content • Directories - taxonomies
• Read Write • Focused on communities • Sharing content • Tagging - folksonomies
• Semantic web • Focused on individuals • Web of data • user engagement
Web 1.0
Web 3.0
The rise of the internet
Web 2.0
The Mobile World
What's your Architectural style?
Enterprise Architecture Approach
Where and when does an Enterprise Architect contribute?
Gain traction and momentum
Progressive insights
Kaizen
Channel your energy
Work through the layers of complexity
Business drives IT
1. Assess
Business Data Application Technology
Interviews
Understand the business
Pain points Needs
Determine impact - Finance, People, Process and tools
Application Inventory
Application Inventory
User efficiency
Meta Data models
Data models
Profiling
Technology Inventory
2. Incept
Standardisation
html5, css3, xml, soap, rest, rdf, owl, saml, sql, http,...
Design & prototype
Get your troops involved
Build your vision
3. Package
Occasional user
High end users Expert users
Loyal followers
Scope your work
Remember to work in increments !
Work within business project borders.
Get improvements on the IT roadmap
Percent of time Google employees can spend working on ideas and projects that interest them
Percent of Google's products that originated from the innovation Time Off
20%
50%
4. Sell
Features
Benefits
Align People
Prototype
Know your audience
Anticipate
Govern
Path of the Enterprise Architect
Skills of the Enterprise Architect
Treasure hunter
The generic specialist
Presentation skills
The diplomat
The salesman
