1. business and industrial

Avancier
Avancier Methods (AM)
What is EA today?
and other FAQS
You may show this slide show
provided you commend avancier.co.uk to your audience
Copyright Avancier Ltd 2013
HLD directs and constrains LLD
► Higher level designers direct and constrain lower level designers
■ They set targets that lower level designers must aim to reach.
■ They describe designs in abstract and idealised forms that lower level
designers must elaborate and realise.
■ They set general principles, patterns and standards that lower level
designers should apply in specific cases.
Copyright Avancier Limited
Avancier
Design process
Architecture tends to the left in some or all ways below
Higher level design
Design dimension
Strategies and road maps
Longer time <--> Shorter time
Broader goals, longer processes and
coarser-grained subsystems
Composition <--> Decomposition
Avancier
Lower level design
Shorter term sprints and deadlines
Narrower requirements, shorter
process steps and finer-grained
components
Applications of standards,
Generic standards, principles,
Generalisation <--> Specialisation principles, patterns and reference
patterns and reference models
models
Business needs and idealised system
descriptions
External: services presented via
interfaces
Required behaviour: transient
services and processes
Idealisation <--> Realisation
Encapsulation < --> Realisation
Actions < --> Actors
Copyright Avancier Limited
Physical technology solutions
Internal: processes and components
Designed structure: persistent
components, roles and interfaces
In some or all of these ways
Avancier
► Enterprise architects direct and constrain solution architects
► Solution architects direct and constrain software architects and
other technical specialists
► Software architects direct and constrain software developers
Higher level design
Design dimension
Strategies and road maps
Longer time <--> Shorter time
Lower level design
Shorter term sprints and deadlines
Broader goals, longer processes and coarser-grained subsystems
Composition <--> Decomposition
Narrower requirements, shorter process steps and finer-grained
components
Generic standards, principles, patterns and reference models
Generalisation <--> Specialisation
Applications of standards, principles, patterns and reference models
Business needs and idealised system descriptions
External: services presented via interfaces
Required behaviour: transient services and processes
Idealisation <--> Realisation
Encapsulation < --> Realisation
Actions < --> Actors
Copyright Avancier Limited
Physical technology solutions
Internal: processes and components
Designed structure: persistent components, roles and interfaces
A major global service provider names key roles as below
► In the bid phase:
■
■
■
■
■
► In the delivery phase:
Solution Manager
Requirements Manager
Lead Solution Architect
Solution Architect(s)
+ other management roles
► A key output: the "Solution
Definition Doc."
■
■
■
■
■
Business Analyst(s)
Requirements Manager
Lead Technical Architects
Technical Architect(s)
+ other management roles
► A key output of High-Level Design
is the "Architecture."
Notice: no mention of an enterprise architect.
Assumed to be a strategic role within the customer organisation.
Also, a governance role, not employed to produce design docs.
Copyright Avancier Ltd 2013
Avancier
The history of EA frameworks
► Information system and enterprise architecture frameworks emerged during the
1980s out of "Business System Planning" methods.
► 1982 Zachman spoke of the need for "enterprise-level analysis" over and above the discrete
business system planning done to that date.
► 1986 “PRISM” was based on coordination of 4 domains: business, data, applications and
infrastructure.
► 1987 The Zachman Framework spread the same 4 domains over 6 columns and 6 rows.
► 1993 Stephen Spewak's "EA Planning" was based on coordination of the same 4 domains.
► 1996 The Zachman Framework was recast as EA framework.
► 2006 The popular "EA as Strategy" book was about coordination of the same 4 domains.
► 2011 The popular TOGAF v 9.1 is also about coordination of the same 4 domains during
business system planning.
Copyright Avancier Ltd 2013
Avancier
For over 30 years now
Avancier
► Every ISA framework and EA framework has been based on
coordination of the same 4 domains,
■
■
■
■
business,
data,
application software and
infrastructure.
► with a view to effective business system planning.
Copyright Avancier Ltd 2013
Mapping architecture domains to a business/operating model
Avancier
Drivers
Business
Model
Strategic
Management
Customer
Segments
Goals, Visions
& Initiatives
Channels
Products &
Services
Processes
and Data
OD
Operating
Model
HR
FM
Business
Arch
Organisation
Design
Applications
Human
Infrastructure
IT
Infrastructure
Offices
Data Centres
Copyright Avancier Ltd 2014
Data
Arch
Apps
Arch
IT
Arch
What is EA today?
Avancier
► TOGAF says: “Enterprise Architecture and Enterprise Architect are
widely used but poorly defined terms in industry today.”
► EA cannot reasonably be all things to all people.
► Do you expect executives to ask the EA team to lead the design
and planning of
■ a car production line?
■ a marketing strategy?
■ an IT data centre?
Copyright Avancier Ltd 2013
Silo thinking
Avancier
► A silo (or point solution) is an organisation unit or application that:
► is not standardised
■ does not follow the same rules or processes as another doing the same
thing
► is not integrated
■ does not share information with another doing something different
► does not share/reuse common services
■ at the business or technology level.
Copyright Avancier Ltd 2013
Enterprise-wide thinking
Avancier
► Zachman says EA objectives include integration, reuse, flexibility, and
reduced time-to-market.
►
►
►
►
►
“EA as Strategy” introduced an “operating model”
It helps people to position in a business in terms of its desire to
standardise and/or integrate business processes
which depends in turn on its ability to
standardise and integrate business data and business rules
“Operating model” for core business processes
High integration
Coordinated
Unified
Low integration
Diversified
Replicated
Low
standardisation
High
standardisation
“EA as Strategy” Ross, Weill and Roberston, 2006
Copyright Avancier Ltd 2013
The larger business, the more architect roles
Avancier
► The larger the enterprise
► The more distinct architect roles emerge
► The more likely there will be a central enterprise architecture team
A small selection from SFIA today
Role
Enterprise architecture
Solution architecture
Project management
Business analysis
Business modelling
Requirements definition and
management
System design
Database design
Software development
Database admin
Responsibility level
2
2
3
3
3
4
4
4
4
5
5
5
5
5
5
6
6
6
6
6
6
2
2
2
2
3
3
3
3
4
4
4
4
5
5
5
5
6
6
Copyright Avancier Limited
7
7
SA v EA
Avancier
► The motivation and ability to follow the same processes, share data
and share services will be
■ low if Solution Architects are given only narrow project or silo-based
objectives
■ higher if EAs have a strategy to optimise the wider enterprise.
► Of course, there are trade-offs between EA and SA; there are
benefits, costs and risks along both paths.
► So, silo-oriented Solution Architecture and enterprise-oriented EA
are complementary.
Copyright Avancier Ltd 2013
Most modern EA frameworks indicate that
Avancier
► The EA team is concerned with enterprise-wide optimisation of
business systems.
► With this in mind, EA values:
1.
2.
3.
4.
5.
Taking a cross-organisational view
Taking a strategic view
Enabling business via IS and IT
Focusing on the services systems deliver
Abstract system descriptions
► “TOGAF is intended to be a
framework … to establish the EA
team as having board-level,
strategic and cross-organisational
authority... needed for crossorganisational EA to be successful.”
Copyright Avancier Ltd 2013
Avancier
1.
2.
3.
4.
5.
Taking a cross-organisational view
Taking a strategic view
Enabling business via IS and IT
Focusing on the services systems deliver
Abstract system descriptions
Taking a cross-organisational view
“The purpose of enterprise architecture is to optimize
across the enterprise”
Copyright Avancier Ltd 2013
2001: FEAF: the US Chief CIO council
► “A practical guide to Federal Enterprise Architecture”
►
►
►
►
►
“An enterprise architecture (EA) establishes
the Agency-wide roadmap to achieve
an Agency’s mission through
optimal performance of its core business processes within an
efficient information technology (IT) environment.”
Copyright Avancier Ltd 2013
Avancier
2003: Zachman emphasised the breadth of EA
► EA has objectives over and above SA
► Zachman mentions
■
■
■
■
integration,
reuse,
flexibility, and
reduced time-to-market.
► “… The broader you define the analytical target, the better leverage
you are going to get on integration, reusability, interoperability, etc…
► If you draw the boundary more narrowly than your jurisdictional control,
you will disintegrate your Enterprise, that is, you will build a “legacy.”
Copyright Avancier Limited
Avancier
TOGAF’s 2009 view of EA as cross-organisational optimisation
Avancier
“The purpose of enterprise architecture is
► to optimize across the enterprise
► the often fragmented legacy of processes (both manual and automated)
► into an integrated environment…”
► “Conducting EA [can be defined as] managing the spectrum of change
required to transform an enterprise towards a target operating model
[defined by] the necessary level of
► business process integration and
► business process standardization.” “Operating model” for core business processes
High integration
Coordinated
Unified
Low integration
Diversified
Replicated
Low
standardisation
High
standardisation
“EA as Strategy” Ross, Weill and Roberston, 2006
Copyright Avancier Ltd 2013
The enterprise IT as a mess (rather than a system)
► “Commonly, solution architects in the design division are driven to
meet the immediate requirements of individual business units, with
the result that only tactical stand-alone solutions are developed and
implemented.”
► IT Business Edge
► “Organizations can use enterprise architecture and portfolio
management approaches to get the required knowledge [to]
streamline and rationalize the apps portfolio reduce redundancy,
consolidate IT capabilities define sound IT governance policies.”
► IT Toolbox
Copyright Avancier Ltd 2013
Avancier
“Common use applications” - an EA principle in TOGAF
► “Large corporations and government agencies may comprise
multiple enterprises, and may develop and maintain a number of
independent EAs to address each one.
Optimised core
No data redundancy
Enterprise systems (shared apps)
► However, there is often much in common about the information
systems in each enterprise, and there is usually great potential
for gain in the use of a common architecture framework.”
Copyright Avancier Ltd 2013
Avancier
“Navigate the stages of EA maturity” (after “EA as Strategy”)
Business
Function
4 Business modularity (6%)
Reusable modules
Avancier
Business
Function
Business
Function
3 Optimised core (34%)
No data redundancy
Enterprise systems (shared apps)
2 Standardised technology (48%)
Fewer platforms
Technology standards
Shared infrastructure
Application
Component
Application
Component
Application
Component
Technology
Component
1 Business silos (12%)
Local apps and infrastructure
Copyright Avancier Ltd 2013
Business
Function
Application
Component
Technology
Component
Technology
Component
Technology
Component
Navigate the stages of EA maturity - as in Avancier Methods
Avancier Methods for EA
4 Business modularity (6%)
Reusable modules
Business structure rationalisation
3 Optimised core (34%)
No data redundancy
Enterprise systems (shared apps)
2 Standardised technology (48%)
Fewer platforms
Technology standards
Shared infrastructure
Data store rationalisation
Application portfolio rationalisation
Technology portfolio rationalisation
1 Business silos (12%)
Local apps and infrastructure
Copyright Avancier Ltd 2013
Avancier
Avancier
1.
2.
3.
4.
5.
Taking a cross-organisational view
Taking a strategic view
Enabling business via IS and IT
Focusing on the services systems deliver
Abstract system descriptions
Taking a strategic view
“An enterprise architect… has professional relationships with
executives of the enterprise to gather and articulate the technical
vision, and to produce the strategic plan for realizing it.”
TOGAF
Copyright Avancier Ltd 2013
IBM view EA as a response to strategy
► EA works from strategy through business, IS and IT domains
Copyright Avancier Ltd 2013
Avancier
“EA as Strategy” Ross, Weill and Roberston, 2006
Avancier
A high-level process for:
► “C-level executives determined to get IT right”
► “a road map for the CIO and IT organisation to follow”.
► "improving strategy execution and lowering IT costs"
► "creating a foundation for business execution…
■ an IT infrastructure and digitised processes that implement your
company's core capabilities.”
“Operating model” for core business processes
High integration
Coordinated
Unified
Low integration
Diversified
Replicated
Low
standardisation
Copyright Avancier Ltd 2013
High
standardisation
Q) How does EA differ from Solution Architecture?
► “The Enterprise Architect has the responsibility for architectural
design and documentation at a landscape and technical reference
model level.”
► “The Enterprise Architect often leads a group of the Segment
Architects and/or Solution Architects related to a given program.”
► “elements in an enterprise architecture may still be considerably
abstracted from Solution Architecture, design, or implementation
views.” TOGAF
Copyright Avancier Ltd 2013
Avancier
EA and SA in the Skills Framework for the Information Age (SFIA)
► SFIA defines EA development in 16 sentences in which
■ “strategy”, “strategies” and “strategic” appear 18 times.
■ “setting strategies, policies, standards and practices” appears twice.
► SFIA defines SA as a leadership, guidance and coordination role in
relation to a specific system.
●
SA Level 6:
□
□
□
□
□
●
leads architectures for complex systems, manages the target design
ensures consistency with specified requirements
responsible for the balance between functional, non-functional and ITSM requirements
selection of solution components
co-ordinates design activities, promoting the discipline to ensure consistency.
SA Level 5:
□
□
□
□
□
logical models of components and interfaces
detailed component specifications
detailed designs for implementation using selected products
assists in technical plans and cooperates with business assurance and project staff
ensures relevant technical strategies, policies, standards and practices are applied.
Copyright Avancier Ltd 2013
Avancier
Reasonable contrasts that you can draw
EA is strategic and cross-organisational
SA is more tactical and local.
Solution Architecture
Enterprise Architecture












Tactical (where no EA)
Concrete
Local (function or unit)
Narrow (point solution)
Parochial processes
Parochial data definitions
Strategic
Abstract
Cross-organisational
Broad (integrated systems)
Standard processes
Standard data definitions
Copyright Avancier Ltd 2013
Avancier
Solution Architects as generalists
Avancier
► Typically, one Solution Architect
■ covers one solution holistically,
■ joins up the various specialists needed to
deliver the solution,
■ smells out where costs and risks are and
makes sure they are addressed.
■ the right hand man of the programme/project
manager.
■ experienced, a broad generalist
■ leads the specialists and joins up everything
from business to IT.
► Sometimes the EA team manager minds a
pool of SAs who are mostly loaned out to
play the SA role on specific projects, where
they may work with or without regard to the
longer-term and wider picture of the EA.
Copyright Avancier Ltd 2013
Solution Architect
Requirements
Specialists
Database
Specialists
Software
Specialists
Technology
Specialists
Team of Software Architects and Technical Specialists
Enterprise Architects as a team of specialists
► Specialist/domain EAs
Avancier
Team of Enterprise Architects
■ take the cross-organisational & strategic view.
■ come up with a road map for their own domain
(which may cut across other domain road maps
and business change plans)
■ not dedicated to any particular solution delivery.
Business
Specialists
Data
Specialists
App
Specialists
Technology
Specialists
Solution Architect
Requirements
Specialists
Database
Specialists
Software
Specialists
Technology
Specialists
Team of Software Architects and Technical Specialists
Team of Software Architects and Technical Specialists
Copyright Avancier Ltd 2013
Avancier
1.
2.
3.
4.
5.
Taking a cross-organisational view
Taking a strategic view
Enabling business via IS and IT
Focusing on the services systems deliver
Abstract system descriptions
Enabling business via IS and IT
“Enterprise Architecture…can be considered as a superset of
Business, Data, Application, and Technology Architecture.”
TOGAF
Copyright Avancier Ltd 2013
Cap Gemini’s Integrated Architecture Framework (IAF)
EA joins up Business, IS and IT
Copyright Avancier Ltd 2013
Avancier
IBM’s EA framework
AND
CSC’s six domains of change
Avancier
► Start with the Business need for Data
► Define Applications to provide that Data
► Define the Technology Platform needed by those Apps
CSC Domains of change
B
Process
Organisation
Location
IS
Data
Application
IT
Copyright Avancier Ltd 2013
Technology
Does EA = Business Architecture or IT Architecture?
Avancier
► It contains elements of both, but not all of either.
► Business management consultants address business
matters outside the remit of the EA team
Business
■ market research, product design, marketing strategy etc.
► IT infrastructure architects address operational matters
outside the usual remit of the EA team
■
data centre design, internet gateways, office LANs, firewalls, servers, virtualisation, storage,
back-ups, disaster recovery, configuration management, IT supplier management.
Copyright Avancier Ltd 2013
IT platform
Technologies
Q) Does EA = business architecture?
Avancier
► They are overlapping sets
► EA does not direct everything important to a business
■
■
■
■
■
Business strategy
Hardware product design
Production line design
Marketing strategy
Organisation design from a sociological perspective
Copyright Avancier Ltd 2013
Business
EA focuses on business activities that are systemisable
Avancier
► The variety of human activity is vast
■
■
■
■
■
■
Digging a road
Negotiating contractual terms
Acting in a play
Running a board meeting
Coaching a football team
Cooking food
► EA usually focuses on mission-critical business
processes that are “systemisable” because they
■ Deterministic enough
■ Repeated enough.
Copyright Avancier Ltd 2013
Business
Process
EA = Business Architecture with IS support
► Mission-critical business processes are “systemisable”
because they
■ Deterministic enough
■ Repeated enough.
Avancier
Business
Process
► Which commonly means they are
■ enabled or supported
■ monitored or directed
■ by information systems
Process
Information
Systems
Data
Copyright Avancier Ltd 2013
EA focuses on activities that are create or use data
► The current state of a business process can be and
often is recorded in a data record.
Avancier
Business
Process
► So an EA model is likely to feature both
■ processes that create and use data
■ data that processes create and use
Process
Information
Systems
Data
Copyright Avancier Ltd 2013
Q) Does EA deal with non-digital data processing?
► Non-software information systems can be OK
► But EA frameworks address only digital data
System
Man-made system (technology)
Model
Business Information System
Maintained Information System
Software Information System (Business Application)
Non-Software Information System (NI cards, BoBritain Control room)
Static Information System (Domesday book)
Process control system
Other kinds of model
Non-model technology
Software technology
Platform application (DBMS, OS)
Other kinds of software technology
Other kinds of non-model technology
Natural system
Biological system
Human actor
Non-human organism
Other kinds of natural system
Disorganised thing
Copyright Avancier Ltd 2013
Avancier
Business
Process
Paper forms
Card indexes
???
EA focuses on activities that are digitisable
Avancier
“EA as strategy” depends on business data
► Integration means data must flow between roles and processes.
► Standardisation means the meaning of data items must be agreed
and understood across the business.
Business data is stored and retrieved via applications
►
►
►
►
Most businesses rely on digital information systems
Most people use a business application during their work
The applications store and transmit data electronically.
Some applications enforce vital business rules
Applications depend on computers and networks
Copyright Avancier Ltd 2013
Business
Process
Process
Information
Systems
Data
IT platform
Technologies
Enterprises need better and quicker management information
► Managers cannot rely on communication up and down a
hierarchical management structure.
► They need good information to see trends and make
predictions.
► They need better and quicker information to handle:
■ Exponential Change
Business
Process
Process
●
Product and service categories change every one or two years.
●
Exponentially growing use of mobile devices and internet.
Information
Systems
Data
■ Hyper Competition
●
Avancier
Capable workers are available across the world to work at any
time of the day.
■ Global Knowledge Sharing
●
●
Intellectual Property is hard to protect
Cross-enterprise communities exchange information.
Copyright Avancier Ltd 2013
IT platform
Technologies
EA joins Business to IT by
Avancier
► extending up into the BA domain
■ focusing on roles and processes that are systemisable
■ create or use data that is digitisable
Business
Process
Process
► being centred on IS that
■ enable and support
■ monitor and direct
■ business roles and processes
► and ensuring a robust IT platform
Copyright Avancier Ltd 2013
Information
Systems
Data
IT platform
Technologies
“EA regards the enterprise as a system” TOGAF
Avancier
Business
Process
► Integration of activities
► across the breadth of the enterprise
► up/down the human-computer stack
Process
Information
Systems
Data
IT platform
Technologies
Copyright Avancier Ltd 2013
EA puts IT in a business context
► “Enterprise Architecture
► structures and gives context to activities delivering
concrete business outcomes, primarily but not
exclusively in the IT domain.” TOGAF
► enables “the effective management and exploitation of
information through IT” TOGAF
Avancier
Business
Process
Process
Information
Systems
Data
► In short, EA is about Business/IT alignment
■ A glib phrase but a reasonable generalisation.
■ Improving how IS supports the business
Copyright Avancier Ltd 2013
IT platform
Technologies
EA joins up Business, IS and IT
Avancier Methods – architecture work space
Avancier
Business view
Information/data view
Applications view
Infrastructure Platform
view
Enterprise/Business
Standardisation & integration
of business roles & processes
Business function/capability hierarchy
Business products & services catalogue
Business processes and roles
Etc.
Enterprise/Data
Data standardisation & integration
Data store & data flow catalogues
Maps data to business functions
Business data model & views of it
Canonical data model(s)
Core business data entity life cycles
Etc.
Enterprise/Apps
Business app standardisation &
integration
Business app portfolio/catalogue
Maps business apps to business functions
Business app life cycles and road maps
Etc.
Enterprise/Platform
Platform standardisation & integration
Platform technology portfolio/catalogue
Platform services portfolio/catalogue
(TRM)
Platform technology life cycles and road
maps
Etc.
Solution/Business
For a required system/solution:
Business services
Business processes and roles
Mappings to goals & locations
Requirements catalogues
Use case diagrams and definitions
Outline UI (or other I/O) designs
Etc.
Solution/Data
For a required system/solution:
Maps data to processes and roles
Logical data models
CIA requirements
Data qualities/meta data
Etc.
Solution/Apps
For a required system/solution:
Maps use cases to processes and roles
Maps business apps to use cases
Design for NFRs
Coarse-grained app components
Coarse-grained sequence diagrams
Etc.
Solution/Platform
For a required system/solution:
Maps platform to business apps
Platform technology definitions
Client & server node definitions
Design for NFRs
Outline deployment diagrams
Outline network diagrams
Etc.
Software/Business
Detailed use case definitions
Detailed UI designs
Governs UI implementation
Etc.
Software/Data
Detailed database design
Detailed message design
Governs database administration
Etc.
Software/Apps
Detailed (fine-grained) software design
Governs software development
Etc.
Software/Platform
Detailed deployment diagrams
Detailed network diagrams.
Governs platform and network
configuration
Etc.
Copyright Avancier Ltd 2013
Avancier
1.
2.
3.
4.
5.
Taking a cross-organisational view
Taking a strategic view
Enabling business via IS and IT
Focusing on the services systems deliver
Abstract system descriptions
Focusing on the services systems deliver
You may show this slide show
provided you commend avancier.co.uk to your audience
Copyright Avancier Ltd 2013
Architects take an external view first
► A human or computer activity system is:
■
■
■
■
a collection of roles or components (persistent structural elements)
organised so as to cooperate in
processes (transient or repeated behavioural elements)
to sustain the system itself and/or to deliver desired effects (services)
► EA encapsulates a system
► It considers its environment before its internal structure.
► It is service-oriented
Copyright Avancier Ltd 2013
Avancier
Definitions of “Service”
Avancier
► ArchiMate definition
► TOGAF definition
■ “a unit of functionality that a
system exposes to its environment,
■ hides internal operations,
■ provides a value,
■ accessible through interfaces.”
► ArchiMate examples
■ “an element of behaviour that
■ provides specific functionality in response to
requests from actors or other services”
■ “a logical representation of a repeatable
business activity, has a specified outcome, is
self-contained, is a ‘‘black box’’ to its
consumers.”
► TOGAF examples
Document
Printing
Document
Scanning
Check customer
credit
Policy Creation
Premium
Payment
Provide weather
data
Claim
Registration
Claim Payment
Consolidate
drilling reports
Copyright Avancier Ltd 2013
Beware “service” is a slippery concept
► In ArchiMate – a unit of functionality
► In TOGAF – an element... that provides specific functionality
► A singular function of an encapsulated system/component
■ Check credit
■ Register claim
► The response of a system to a discrete request or event
► Definable in a specific service contract.
► Beware that in other places, the term service is used loosely, or
to mean something else
► See the Unified/ArchiMate Modelling Language slide show
Copyright Avancier Ltd 2013
Avancier
The simple domains-as-layers picture
Avancier
► “The ArchiMate Language Primer” follows the convention of
defining three enterprise architecture domains as layers.
Lower layer used
by higher layer
Lower layer realises
services requested by
higher layer, rather than
the higher layer itself
Copyright Avancier Ltd 2013
ArchiMate’s notion of architecture domains as layers
Environment
Business
Services
Business layer
App
Services
Application layer
Platform
Services
Technology layer
Copyright Avancier Ltd 2013
Avancier
► Components and processes in
a higher layer require services
that are provided by
components and processes in
a lower layer
► So you may say
► a higher layer uses a lower
layer
► a lower layer serves a higher
layer
► a lower layer realises the
services requested of it.
You might consider the layers as nested systems
Avancier
Environment
Business
Services
Business layer
App
Services
Application layer
Platform
Services
Technology layer
Copyright Avancier Ltd 2013
► The simple layered model of
enterprise architecture is
common and useful.
► But it is naïve
► Reality is often more complex
But service provision can be distributed
► E.g. An enterprise can use services provided by application and/or
technology layers operated by another enterprise (perhaps in a remote
location)
Environment of Enterprise A
The business of
enterprise A
Service Provider
SaaS
Applications
Platform
Services
IaaS
Technology
► The architecture of enterprise A contains the services it requires,
but not the internal components and processes of the service
provider
Copyright Avancier Ltd 2013
Avancier
Service provision can be shared
Avancier
► Two or more enterprises may use the services (business, application or
technology) of the same service provider
Environment of the shared service provider
The business of
enterprise A
Shared Service Provider
SaaS
The business of
enterprise B
Applications
Platform
Services
IaaS
Technology
IaaS
► A shared service provider is can be (and often is), owned and
operated independently of its clients,
Copyright Avancier Ltd 2013
Inter-layer client-server roles may be reversed
Environment
► 1) An entity in the environment
(say a customer) requests a
service from directly from an
business application.
Business
Services
Business layer
► So, the app service becomes a
business service.
1
4
App
Services
Avancier
3
Application layer
Platform
Services
Technology layer
Copyright Avancier Ltd 2013
► 2) The application may then
request a service of an entity
(say an employee) in the
business layer.
2
To keep it simple: this is a useful mental model
Environment
contains entities and activities that the business monitors,
serves or directs
Business
Services
Business layer
usually a human activity system containing
people (actors) who play roles in processes
App
Services
Application layer
contains digital information systems
Platform
Services
Technology layer
contains infrastructure or platform applications used by
business applications
Copyright Avancier Ltd 2013
Avancier
► Think of architecture
domain/layers as related by
client-server relationships, not
always in this hierarchical way
► Each layer is a subsystem that
realises services requested of it.
Avancier
1.
2.
3.
4.
5.
Taking a cross-organisational view
Taking a strategic view
Enabling business via IS and IT
Focusing on the services systems deliver
Abstract system descriptions
Abstract system descriptions
““the EA is permanent and manages the EA artefacts
delivered by projects.” TOGAF
Copyright Avancier Ltd 2013
2003: Zachman emphasised the importance of documentation
► “If it gets so complex that you can’t remember everything all at the
same time, you have to write it down (Architecture).
► Then, if you want to change it (whatever it is), you start with what you
wrote down (Architecture), the baseline for managing change.
► If you are not observing the engineering design principles…, you are not
going to realize the engineering design objectives of alignment, integration,
reusability, interoperability, flexibility, reduced time-to-market, etc., etc.,
etc.
► … you are never going to appreciably reduce time-to-market until you have
something in inventory before you get the order.
► If you are not building (and storing, managing and changing)
primitive models, you are not doing Architecture. You are doing
implementations.
Copyright Avancier Limited 2103
Avancier
EA as a description – in a repository
► EA maintains an abstract description of business roles
& processes & the information systems &
technologies they use.
““the EA is permanent and
manages the EA artefacts
delivered by projects.” TOGAF
Avancier
Business
Process
Information
Systems
IT platform
Technologies
Copyright Avancier Ltd 2013
Generic EA description entities
► EA treats the enterprise as a system
► A system is a structure of components that cooperate in
processes to deliver services
► A component is a building block or subsystem that can be defined
■ Externally, by the services it offers
Services
Component
■ Internally, by the processes it performs to deliver those services
■ And for implementation, by the resources it needs
Copyright Avancier Ltd 2013
Avancier
Domains and entities - in TOGAF
► Such a 3-layer view is
commonplace in
architecture
frameworks
Avancier
Business
Services
Business
Business
Function
Business
Function
Business
Function
IS
Services
Services
Component
Business
Function
Information
Systems
Application
Component
Application
Component
Application
Component
Application
Component
Platform
Services
Technology
Technology
Component
Copyright Avancier Ltd 2013
Technology
Component
Technology
Component
Technology
Component
Domains and entities - in ArchiMate
► Such a 3-layer view is
commonplace in
architecture
frameworks
Avancier
Business
Services
Business
Business
Role
Business
Role
Business
Role
Application
Services
Services
Component
Business
Role
Applications
Application
Component
Application
Component
Application
Component
Application
Component
Infrastructure
Services
Node
Node
Technologies
Node
Copyright Avancier Ltd 2013
Node
Avancier
Copyright Avancier Ltd 2013
Core entities described in TOGAF
Avancier
► TOGAF makes much of separating logical components from physical components.
► Here, logical means vendor/technology-neutral (but sometimes means external view)
Business
Service
Business
Process
Business
Function
Business
Organisation
Role
IS
Service
Data Entity
Information
Systems
Platform
Service
Infrastructure
Technology
Passive Structure
Logical App
Logical Data
Component
Data
Component
Behaviour
Copyright Avancier Ltd 2013
Actor
Logical
Technology
Component
Physical App
Physical Data
Component
Physical
Technology
Component
Active Structure
A meta model for the BCS reference model for E&SA
External
Activity
Environment
Avancier
External
Entity
Business
Service
Business
Process
Business
Business
Function
Business
Activity
Organisation
Role
Actor
Data Entity
Use Case
Data Store
Automated
Service
Application
Platform
Service
Technology
Information
Systems
Infrastructure
Technology
Passive Structure
Behaviour
Copyright Avancier Limited 2013
Active Structure
Avancier
A few EA FAQS
You may show this slide show
provided you commend avancier.co.uk to your audience
Copyright Avancier Ltd 2013
Q) Does EA shape the business strategy or business model?
Avancier
► EA might inform strategic decisions,
■ say mergers and acquisitions,
► but does not usually initiate or conclude them.
► Enterprise architects can and do recommend business
changes,
► But usually of a kind, related to business roles and
processes that are repeated and deterministic enough to
be systematised and digitised.
Business
Process
Information
Systems
IT platform
Technologies
Copyright Avancier Ltd 2013
On the other hand,
Avancier
► The more business activities rely on information systems
► the more important the IT support function.
► There are data processing businesses
Business
Process
■ banks
■ government departments
► where the human operation of digital information systems
is core to the business.
Information
Systems
IT platform
Technologies
Copyright Avancier Ltd 2013
Q) Does EA respond only to business strategy?
► EA frameworks do start from business drivers, goals,
strategy and plans
► But there may be little strategy relevant to business
systems
► EAs can be self-starters who find and propose ways to
improve, rationalise, standardise and integrate business
systems.
► Power and politics matter.
► If EAs are recognised and respected by CxOs, then such
work is more likely to be approved.
Copyright Avancier Ltd 2013
Avancier
Business
Process
Information
Systems
IT platform
Technologies
Q) What is EA in the 21st century?
► Aligning IT with business needs remains a primary aim of EA.
► Since 1980, IT has been networked; so
■ employees carry devices and
■ customers connect from remote locations.
■ business managers have to worry more about availability and security of
business data.
► That doesn't mean EA has become IT centric
► EA is still about planning how best to support business roles and
processes with information systems.
► While recognising business processes now depend on a more
pervasive, invasive and complex IS and IT estate.
Copyright Avancier Ltd 2013
Avancier
Q) What is the modern EA manager?
►
►
►
►
“an exceptional senior management role with an opportunity
to join a business which is making significant investment
to create synergy between technology and growing business need,
with significant upcoming projects including a Global ERP Rollout.
► “The successful candidate will
► lead technical strategy across the business
► alongside delivery of enterprise architecture to meet business
requirements.
Copyright Avancier Ltd 2013
Avancier
The modern EA manager (2014)
► “Core Responsibilities:
► Definition and governance of architectural
frameworks effectively translating business need
to system requirements.
► Development, implementation and operation of
Enterprise Architecture
► Definition of architecture alongside timescale,
budget and roadmap to deliver effective use of
technology.
► Management of governance forums.
► Identification of future opportunities to make
commercial improvement and value to the
business in terms of technology.
► Optimisation of cost, quality and risk of IT
infrastructure capex investments through effective
capex planning and architectural management.
► Oversight of IT governance, planning, portfolio
management / support and performance
management.
Avancier
► “Experience
► The role holder will be able to display significant
breadth of experience of the above alongside a
proven track record of developing and
managing a team.
► Ideal candidates will be strong strategic thinkers
with exceptional skills across communication,
leadership and stakeholder management.
► Deep knowledge of IT Strategy.
► Experience of multiple delivery methodologies
ideally including Waterfall and Agile.
► Certification and experience in architectural
framework e.g. TOGAF.
► Knowledge of and interest in emerging trends
and technologies in areas like SaaS, SOA, IaaS
and PaaS.
► Degree level qualification or similar.”
Copyright Avancier Ltd 2013
Cross-organisational aims of EA today
Avancier
► To improve business systems
■ Improve business data quality, relevance and use
► To help understanding and change impact analysis
■ Maintain an abstract description of business roles and
processes and the systems they use
► To minimise business risks and maximise
opportunities
““the EA is permanent and
manages the EA artefacts
delivered by projects.” TOGAF
■ Keep an eye on information system & technology
evolution, and produce road maps where needed
“Operating model”
► To optimise business systems and increase agility
■ Tidy up the mess of duplicated and overlapping systems
by standardisation and integration.
Copyright Avancier Ltd 2013
Integrated
Coordinated
Unified
Diversified
Replicated
Standardised
An EA manifesto
Avancier
Favour
1. Taking a cross-organisational view - over many local views
■
(to reduce TCO and complexity).
2. Taking a strategic view – over tactical-only views
■
(to minimise risk, redundancy and disintegrity).
3. Enabling business via IS and IT – over single-domain thinking
■
(to maximise opportunities and minimise wasteful IT spend)
4. Focusing on the services systems deliver – over their internal
organisation
■
(to maintain an external view and ensure goals are met)
5. Abstract system descriptions - over very detailed or no documentation
■
(to facilitate understanding and change management).
Copyright Avancier Ltd 2013
So, EA is not the best label for
► IT architecture alone
■ without reference to business processes, roles and systems.
► Solution architecture alone
■ without reference to other solutions in the same enterprise.
► Business processes alone
■ undocumented and/or without reference to business information
systems.
Copyright Avancier Ltd 2013
Avancier
Enhancing TOGAF with Avancier Methods
Avancier
TOGAF’s ADM is a change management
framework that promotes the role of architects AM gives architects more specific
processes and documentation artefacts
Preliminary
Initiate
H
Architecture
Change
Management
A
Architecture
Vision
Establish capability
Establish directions....
Scope the endeavour
Get vision approved
B
Business
Architecture
Govern
G
Implementation
Governance
F
Migration
Planning
C
IS
Architecture
E
Opportunities
And solutions
D
Technology
Architecture
Respond to oper'l change
Monitor the portfolio(s)
Govern migration/delivery
Initiate (re)construction
Manage
Manage stakeholders
Manage requirements
Manage business case
Manage readiness & risks
Plan
Select suppliers
Plot migration path
Chart road map
Complete delivery plan
Copyright Avancier Ltd 2013
Architect
Understand the baseline
Review initiation products
Clarify NFRs
Design the target
Methods and resources
► Avancier Methods
are useful with all
architecture
frameworks that share
similar ends and
means
Avancier
BCS E&SA
reference model
ArchiMate
Language
Framework
► http://avancier.co.uk
TOGAF
The Open Group
Avancier
Methods
CSC’s domains of
change (POLDAT)
IBM’s view EA
EA as Strategy”
MIT
Copyright Avancier Ltd 2013
EA history 1980 to date (explained another slide show)
20th century sources
► Business Systems Planning , IBM
► PRISM
► The Zachman Framework
► EA Model, NIST
► EA Planning, Spewak
► IT Management Reform Act (Clinger Cohen Act)
21st century sources
► Federal EA Framework, Federal CIO council
► Enterprise edition of TOGAF, The Open Group
► Integrated Architecture Framework (IAF), Cap Gemini
► “EA as Strategy”, Ross, Weill and Robertson
► E&SA reference model, The British Computer Society
Copyright Avancier Ltd 2013
Avancier
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
References
Avancier
“Business Systems Planning” see the Wikipedia entry, and the web site of Robinson College of Business, Georgia State University.
"Business Systems Planning and Business Information Control Study: A comparison" (1982) John Zachman, in IBM Systems Journal 21(1).
p32.
"A Framework for Information Systems Architecture". (1987)John A. Zachman in IBM Systems Journal, vol 26, no 3. IBM Publication G3215298.
“Enterprise Architecture Model” (1989) National Institute of Standards and Technology
“Extending and formalising the information systems architecture framework”. Sowa & Zachman in IBM Systems Journal, Vol 31, No 3
“EA Planning” (1993) Stephen Spewak. See entry in Wikipedia for references.
“IT Management Reform Act” (Clinger Cohen Act) 1996
Zachman EA Framework. See entry in Wikipedia for references.
“Federal EA Framework” Federal CIO Council 1999/2001
“TOGAF” free to read at opengroup.org
“EA as Strategy” (2006) Ross, Weill and Robertson / MIT Center for Information System Research
“Avancier Methods” at avancier.co.uk.
“The British Computer Society’s reference model for enterprise and solution architecture” downloadable from www.BCS.org.
Copyright Avancier Limited