William El Kaim
Sustainable IT Conference – Paris 2009
Resilient Enterprise ArchitectureExtending ACMS with Resilient Enterprise
Architecture …
General information
• This talk covers
• Software Intensive system
• You can contact me
• architect-tonic-at-resilient-it.com
• http://blog.resilient-it.com/
• Reference this talk
• “William El Kaim, Resilient Enterprise
Architecture, Sustainable IT conference,
Paris 2009”.
2Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Disclaimer: All opinions presented here are mine as an individual and can not be
associated in any way to my current employer or any other community or organization
Sustainable ITACMS Methodology
• Approach tailored for IT overhaul where data are the
foundation for rebuilding agility and coherence
• Follow a Model Driven approach
• Business rules are described externally and exhaustively
and not encapsulated in code or DBMS
• Not model based unfortunately
• Promote BPM
• Not a software engineering practice!
• Managed by a business person: someone who understand the
“business” and decides upon a strategy for doing that business
• Business process improvement can benefit from work already
done and proved to work (Six Sigma, lean, etc.)
3Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Sustainable ITEmbrace and Extend ACMS
• Integrate ACMS in a Enterprise Architecture Vision
• Ensure EA is promoting and ensuring resilience
• Increase approaches to project development in ACMS
• Promote agile (short term tactical artifact)
• Promote product line (long term asset based)
• Leverage fully OMG work done
• Profiles: new on MDM, Integrate (SOAML, TestML, SysML)
• Benefit from current evolution around platform and web as a
platform (“x”aaS to implement MDA (PIM to PSM)
• Change Management and communication
• supporting new features is about "injecting new models"
rather then coding for them4
Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
What is Enterprise Architecture?What makes it « resilient »
• Understand and document
• My Information System patrimonial
• Its organization, its structure
• its components, its interactions
• Its information managed and data
exchanged
• Its relationships with others
(ecosystem and B2B dialects)
• Manage
• Analysis, KPI, IT Portfolio
• Govern
• Bring under control Cost, IS
Performance and evolution risks
5
Deliver value with/to the business
on time and on market
(Tailored EA framework like eTom,
Agile, Lean, MDx, xaaS, BPx, etc.)
Agile and elastic platform and
Infrastructure to support all
architecture, “ilities” and
deployment needs
(ITIL, PaaS, Virtualization, SAN, etc.)
Resilient EAUse EA as a control tower for
assessing and ensuring resilience
Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Resilient Enterprise ArchitectureDescribed via a layered approach
6
Strategy
Technology
Resilient EA
Methodology, policies and rules
should be applied at all layers
Resilient EA = more agile and
dynamic (not only static
description) – Follow ACMS
principles
Holistic
Views
Security
Master data
and
Information
Integration
SOA
Business
Architecture
Application
Portfolio
Application
Architecture
Technical
Architecture
Business
Model
Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Resilient Enterprise ArchitectureMapping with Praxeme
7
Semantic, Pragmatic, Geographic
Logical, Software Model
Technical,Physical and Material
PRAXEME
Resilient EA
Use Praxeme as EA resilient Methodology and implement
your project with the development process of your choice
Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Resilient Enterprise Architecture Some Other Deliverables (DSL, not UML)
Business Architecture
(cartographie des métiers)
Process Architecture
(cartographie des processus)
Functional Architecture
(cartographie fonctionnelle)
Application Landscape
(cartographie applicative)
Application Architecture
(cartographie architecture
technique)
Business(Métier)
Function(Fonctionnelle)
IS(Informatique)
Plan d’occupation des sols
Décomposition fonctionnelle
Projection fonction/application
schéma d’architecture logique
Master data et référentiels
Couverture fonctionnelle de
l’application
schéma inter-applicatif
schéma d’architecture logique
Schéma d’architecture de
contexte technique, de
composants, de données
applicatives, d’architecture
technique (n-tiers, couches)
Description des processus
opérationnels, des activités, des
objets métiers
Organigramme, acteurs
Infrastructure Architecture
(cartographie architecture
technique)
Schéma d’architecture
d’infrastructure, de déploiement
Information
and Data
Architecture
Modèle d’information
et règles de gestion
Master Data
Schéma de description
des échanges
Schéma conceptuel de
données
Schéma de données
techniques
Glossaire de termes
Métier, Description
des objets métiers
8Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Extend ACMSStay Agile at Project Level
• Greenfield development (Whaow)
• Fun for developer, new projects, excitement
• Brownfield development (Beurk)
• Modernization, migration, maintenance
• Eat all the innovation/new product budget
• IT on diet – No more development (psss)
• Maintenance mode only - terrible effects
• Kill application (Agghhh)
9
Resilient EA
Need a unified EA Methodology
Policies, patterns and rules
should be applied at all layers
Make EA more dynamic (not only
static description)
Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Extend ACMSAdopt a product-line approach
• Designed for reuse
• Customize existing Methodologies, standard, patterns, tools and technologies to build product lines
• Distinguish “commonly reusable artifact (called assets) from ones that can vary (hook, flexi-point, variability point, etc.)
• Leverage Model Driven approach and code generation techniques
• Designed with reuse
• Reuse product lines assets to produce specific products by fixing variability
• Need to be flexible enough to accommodate custom logic without a bolt on solution for each need.
• Reuse tools and operational procedures to enable time to market in days or hours instead of weeks
10
Product Line Engineering as a
way to build agile IT product
fabric, by defining commonalities
and variabilities
Agility factor = ratio variable asset
vs. common assets
Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
Extend ACMSLeverage MDA, especially PIM to PSM mapping
11Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
• Promote forward engineering and reverse engineering only for migration. Forbid run-trip engineering
• Govern “ilities” as assets
• Leverage platform commoditization, and Infrastructure Elasticity to provide automation chain (PSM)
• Use tools in an agile way to avoid waste and improve velocity when valuable
Conclusion
• 2010: Models for the mass
• UML - Microsoft enters the game
• Community: SustIT is one of them – we need you!
• IT Proletarization
• Some IT jobs will lead to new proletarian (low value work,
repetitive tasks, low salary)
• Most of IT people will move to new business role
• Web as a platform (variability in the large)
• VM are now the deployment target
• Dynamic language, executable models (BPMN) will grow
• xAAS, open source and Open API will dominate
• Automation, elasticity, self healing (raise of the machines)
12Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009
ConclusionA new community and business around ACMS?
• Ecosystems needs to emerge to provide assets for model
driven approach, especially on the Business side
• OMG subscription model should be extended to integrate the very small innovative
EU company ready to deliver open sourced MDA work (within eclipse?)
• Libraries of MOF compliant Meta-models should be open sourced / sold and
available on an ACMS market / repository web site
• Tooling is still complex, too fragmented, not cost effective
• if possible with integration to M2M or M2C generator
• Working with several UML Profiles – risk is to have complex models
• Integration with EA tool is key
• Casewise will be UML 2 native soon, Mega 2009 (buy it) or using an open source
solution based on eclipse
• Each application sold on the market should provide its description in term of models
(not only doc in PDF)
13Resilient Enterprise Architecture - William El Kaim - Sustainable IT Conference 2009