Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Everything you wanted to know about Enterprise Architecture,
Transcript of Everything you wanted to know about Enterprise Architecture,
- Tidy up the mess that point solutions have left the enterprise with
- Portfolio management – prioritisation of changes
- Consolidation and integration
Business and technical agility
– Faster and cheaper change by imposition of standards and commonality
– Reuse assets across the enterprise
Enterprise wide transformation
– Treat the whole enterprise as a system
– Build a cross-organisational picture of the enterprise
Plan the future
- Roadmaps aligned with business strategy and priorities
Improved alignment of business and IT in line with Company’s business strategy
Better understanding of solution cost of ownership and opportunities for cost containment
Business and technical agility
Long term planning – strategic view of IT activity, movement away from tactical,
silo based solutions to strategic solutions implemented in accordance with a corporate architecture governance process
Reduction in number of project ‘failures’ / overruns due to selection and usage of inappropriate solutions
Documented solution design decisions matched to business requirements
De-duplication of applications and technologies
Change impact assessment capabilities
Application and technology lif-cycle management
Industry and technology innovation awareness
Enterprise Architecture - Value Proposition
The structure and behaviour of a business system. Covers business functions or capabilities, business processes, the roles of the actors involved.
Use Case Diagrams
Function Decomposition Diagrams
Process Flow Diagrams
Data Flow Diagrams
The definition of, storage and movement of data within an organisation. How data is used by the business and/or its applications.
The structure and behaviour of applications used in a business and how they interact with each other and with business users or actors.
The structure and behaviour of the technology platform and services that underpins user applications
Where to start?
Establish baseline portfolios
Projects - in flight and pipeline
Application Portfolio Management
Capture various attributes for each application...
Number of Users
Capital and ongoing costs
Locations used at
Capture the main inter application data flows and data exchange with external actors
Map applications to the business capabilities/functions that they facilitate and support
Analyse the application portfolio
Determine what application attributes are important
- Cost - licence costs, external / internal support costs
- Business fitness - does it do the job for the business?
- Technical fitness - does it fit with overall technical strategy
- Risk - is it supported by the supplier, is skilled support resource available
Identify multiple applications providing similar business functionality
Candidates for rationalisation, but...
- Be aware of specific application dependencies
- Wider enterprise ("corporate") viewpoint
- Cost of rationalisation, licencing, development, data conversion, etc.
Identify potential gaps in the application portfolio, where business functionality is poorly supported by existing IT systems
Is there a business driver to fill the gap?
Assign a strategic action to each application
- leave the application alone, i.e. no further development or enhancements
- update and enhance the application in response to business needs and supplier maintenence releases
- redevelop an existing bespoke application which is reaching end of life
- system no longer used, or functionality has been superseded
- replace an existing packaged solution with another package
Develop application portfolio roadmap
Roadmaps aligned to business strategy
Cannot develop an application portfolio roadmap in isolation. Must take into account...
- technology platform strategy
- existing project portfolio
- articulated business priorities
Utilise baseline application portfolio and MURDeR categorisation as starting point
Combine with application "gaps" where there is a business case
Sanity conformance with architectural principles and holistic enterprise viewpoint
Apply known budgetary and resourcing constraints
Produce initial application portfolio roadmap
Revalidate against business strategy and priorities - an iterative process
We are only here to help you!
Where to apply governance?
as point solutions
Changes planned on a holistic basis
The pace of change
Internet of Things
Not an option to
stand still and ignore
Time to 5 million users
Radio 38 years
TV 13 years
Internet 4 years
iPOD 3 years
iPAD 2-3 months
200 million users in < 1year
Predicting technology is hard
"The PC is just an executive toy" - 1984
"Who needs mobile phones when there is a phone box on every corner" - 1990
"The internet will never be considered a serious business tool" - 1997
"I think there is a world market
for maybe five computers"
Tomas J. Watson (IBM 1943)
"640k of memory should
be enough for anybody"
Bill Gates (Microsoft 1981)
"Larry Page and Sergey Brin
wanted $1M, George offered $750k,
and Google walked"
George Bell (Excite, 1999)
"Twitter is a Poor Man's
Eric Schmidt (Google 2009)
Maintain an Awareness
London market / insurance industry
- LMA Systems Group, etc
- TINtech, etc
- Genesis, E-Accounts, Placing Platform, Central Services Refresh, Service Company Direct Reporting, etc
Standards / Trends
Competitor use of technology
Social media - marketing, new distribution models
"Big Data" - analytics
To optimise across the enterprise, current and
future processes and IT capabilities so that they are responsive to change and supportive of the business strategy.