Approach To It Strategy And Architecture
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Approach To It Strategy And Architecture as PDF for free.
More details
- Words: 1,413
- Pages: 26
Approach to IT Strategy and Architecture Alan McSweeney
The Adaptive Enterprise Business and IT synchronised to capitalise on change
Business
Information Technology Business benefits: simplicity, agility, value November 26, 2009
2
Learn to love what you’ve been taught to fear… Change is constant • Everyday events send ripples throughout the organisation, and the IT that supports it. Change is unexpected • A merger, new market opportunity, sudden shift in competitive landscape, new partner. Change is disruptive • The goal is to minimise the impact of disruptions with an IT environment that is synchronised with the business. Change presents opportunities • The ability to adapt to change is a key advantage in business. To survive, compete and win, enterprises must adapt. November 26, 2009
3
Darwin Reference Architecture Business strategy
Business processes
Applications
Infrastructure
November 26, 2009
Management
•
Brings standardisation to the entire IT environment
•
Eliminates vertical islands
•
Embraces heterogeneity and legacy IT environments
•
Uses automation to scale and reduce complexity
•
Virtualises all IT assets
•
Helps convert fixed costs to variable costs
4
Adaptive Enterprise Design Principles • Reduce number of elements
Simplification
• Eliminate customisation • Automate change
+ • Use standard technologies and interfaces
Standardisation
• Adopt common architectures • Implement standard processes
+ • Break down monolithic structures
Modularity
• Create reusable components • Implement logical architectures
Applied consistently across: •
Business processes
•
Applications
•
Infrastructure
+ • Link business and IT
Integration
• Connect applications and business processes
within & outside the enterprise November 26, 2009
5
How Do We Define Solution Architecture? Solution architecture is the essential, unifying concept of an information system and its effective deployment into an operational environment to solve a key business problem. • Benefits
− Aligns business and information contexts with architectural decisions − Ensures the solution that is built matches requirements, and will evolve with changing business needs − Provides a complete, clearly-scoped solution November 26, 2009
6
CIO Balancing Act Increase agility: •
Maximise return: •
Improve business results; grow revenue and earnings, cash flow, and reduced cost of operations
Enable the business organisation and operations to adapt to changing business needs
Improve performance: Mitigate risk: •
Ensure security and continuity of internal business operations, while minimising exposure to external risk factors
November 26, 2009
Improve business operations performance end-to-end across the enterprise • Increase customer and employee satisfaction •
7
Solution Architecture Bridges the Business and IT Gap Solution Architecture
Business Problem
IT Solution Business/IT Alignment
November 26, 2009
8
Architecture Scope
Building architecture
Information system architecture
November 26, 2009
Discrete (project)
Initiative (program)
Enterprise
Examples: e-procurement, email
Examples: CRM, KM
Example: extended value chain 9
Solution Architecture is Not Just… •A
detailed implementation plan
•A
set of product standards
• For
infrastructure
• Concerned • An
only with technology
end in and of itself
These are parts of an architecture, but they are not an architecture by themselves.
November 26, 2009
10
Approach • Approach
is a mature, fully supported suite of methodologies that enable the delivery of offerings and services that provides: − A set of best-in-class methodologies to support for the management and delivery of business − One-stop shop for methods, tools, and techniques − Guides and templates
November 26, 2009
11
Approach to ITSA − Based on stakeholder participation − Organised as a set of four fundamental views
Business view Functional view
Stakeholders
Technical view
Implementation view
November 26, 2009
12
The Four ITSA Views — Building a House Analogy Business view Why do I want a new house?
Technical view How will it be built?
• residence, entertainment, business • affordability • location • independence • image
• foundation, framing, heat/ac, plumbing, ... • utilities: - electric, water, comms, roads • security systems • controls • materials
Functional view What should the new house give me?
Implementation view With what will it be built?
• • • •
• sourcing - suppliers - specific models • financing • phasing • moving
uses / room layouts peace & quiet, security garden, trees garage, pet needs
November 26, 2009
13
Business View Why are we doing this? ty ili Ag
• Key
questions: oS Q st Co
− What are the internal and external drivers? − What are the business models and processes? − Who participates in the business processes? − What are the project goals? − How will the success of the solution be measured?
sk Ri
November 26, 2009
14
Functional View What should the solution do? ty ili Ag
Key questions:
st Co
• How will it be used and what services will it provide? • What information will it provide? To whom?
oS Q
• What will the completed solution do?
• What qualities must the solution have? sk Ri
November 26, 2009
15
Technical View How should the solution work? ty ili Ag
Key questions: • What are the interfaces and other constraints?
oS Q
• How will the system be structured and constructed? • What applications and data are needed?
st Co
• What does the infrastructure look like? • What standards will apply?
November 26, 2009
sk Ri
• How will the system qualities be achieved?
16
Implementation View
ty ili Ag
With what will the solution be built? Key questions:
sk Ri
November 26, 2009
st Co
• How will the system be developed and deployed? • What validation methods will be used? • How will it be managed? • What is the source of funding?
oS Q
• What specific products and components, from which vendors, are needed to build the system?
17
ITSA Framework and Methodologies
ITSA Methodologies Solution Architecture Concept
Solution Architecture Blueprint
ITSA Framework
November 26, 2009
18
ITSA Framework The fundamental architectural elements of the ITSA framework are: •Business drivers, goals, and metrics (closely associated with the business view •Principles, models, and standards (associated with each of the four views)
November 26, 2009
19
In Summary The approach for creating solution architecture is: − Based on stakeholder participation − Organised as a set of four fundamental views − Motivated by key business drivers, goals, and metrics − Expressed as a set of principles, models, and standards − Linked to actions to ensure timely progress − Supported by an extensible framework of methods, tools, and techniques November 26, 2009
Business view Functional view Technical view Implementation view
20
Contrasting Solution Architecture and Project management Solution Architecture • Defines engagement scope • Articulates the essential elements of the solution and work to be done • Defines resources needed to complete the work • Defines acceptance criteria for solution iterations and phases • … o d to t ha W
November 26, 2009
Project Management • Keeps engagement within scope • Ensures the work breakdown structure covers all the essential elements • Ensures staffing, funding, and resources are available to support the work • Defines milestones, and schedule and ensures acceptance criteria are met • … ne o d t i et g to w Ho 21
Contrasting Solution Architecture and Traditional Engineering Solution Architecture • Finds satisfactory system concepts for ill-defined problems • More art than science, heuristic in nature
n o d ds e s cu t nee o F en cli
November 26, 2009
Traditional Engineering • Finds optimal solutions to wellunderstood problems • More science than art, algorithmic in nature on d se ry u e c Fo eliv d
22
Solution Architecture Concept •A
rapid review of the key elements of a proposed solution, examining each of the four views − Focus on business drivers/goals, principles, models, and standards − Determine feasibility of an effective solution based on obstacles and constraints − Purpose: define solution’s conceptual architecture to facilitate well-informed, rapid decisions and get shared stakeholder understanding of, and commitment to, the proposed solution
November 26, 2009
23
Solution Architecture Blueprint
•A
detailed architectural description of a project, initiative, or enterprise architecture.
• Works
with you to:
− Establish an agreed-to, sufficient solution concept − Define, design, and document all essential features of the solution − Analyse the feasibility of the solution − Plan the implementation of the solution
November 26, 2009
24
IT Strategy and Architecture Framework Business drivers Goals
November 26, 2009
Business view
Functional view
Technical view
business principles
functional principles
technical principles
Implementation view implementation principles
rationales
rationales
rationales
rationales
implications
implications
implications
implications
obstacles
obstacles
obstacles
obstacles
Actions
Actions
Actions
Actions 25
More Information Alan McSweeney [email protected]
November 26, 2009
26
The Adaptive Enterprise Business and IT synchronised to capitalise on change
Business
Information Technology Business benefits: simplicity, agility, value November 26, 2009
2
Learn to love what you’ve been taught to fear… Change is constant • Everyday events send ripples throughout the organisation, and the IT that supports it. Change is unexpected • A merger, new market opportunity, sudden shift in competitive landscape, new partner. Change is disruptive • The goal is to minimise the impact of disruptions with an IT environment that is synchronised with the business. Change presents opportunities • The ability to adapt to change is a key advantage in business. To survive, compete and win, enterprises must adapt. November 26, 2009
3
Darwin Reference Architecture Business strategy
Business processes
Applications
Infrastructure
November 26, 2009
Management
•
Brings standardisation to the entire IT environment
•
Eliminates vertical islands
•
Embraces heterogeneity and legacy IT environments
•
Uses automation to scale and reduce complexity
•
Virtualises all IT assets
•
Helps convert fixed costs to variable costs
4
Adaptive Enterprise Design Principles • Reduce number of elements
Simplification
• Eliminate customisation • Automate change
+ • Use standard technologies and interfaces
Standardisation
• Adopt common architectures • Implement standard processes
+ • Break down monolithic structures
Modularity
• Create reusable components • Implement logical architectures
Applied consistently across: •
Business processes
•
Applications
•
Infrastructure
+ • Link business and IT
Integration
• Connect applications and business processes
within & outside the enterprise November 26, 2009
5
How Do We Define Solution Architecture? Solution architecture is the essential, unifying concept of an information system and its effective deployment into an operational environment to solve a key business problem. • Benefits
− Aligns business and information contexts with architectural decisions − Ensures the solution that is built matches requirements, and will evolve with changing business needs − Provides a complete, clearly-scoped solution November 26, 2009
6
CIO Balancing Act Increase agility: •
Maximise return: •
Improve business results; grow revenue and earnings, cash flow, and reduced cost of operations
Enable the business organisation and operations to adapt to changing business needs
Improve performance: Mitigate risk: •
Ensure security and continuity of internal business operations, while minimising exposure to external risk factors
November 26, 2009
Improve business operations performance end-to-end across the enterprise • Increase customer and employee satisfaction •
7
Solution Architecture Bridges the Business and IT Gap Solution Architecture
Business Problem
IT Solution Business/IT Alignment
November 26, 2009
8
Architecture Scope
Building architecture
Information system architecture
November 26, 2009
Discrete (project)
Initiative (program)
Enterprise
Examples: e-procurement, email
Examples: CRM, KM
Example: extended value chain 9
Solution Architecture is Not Just… •A
detailed implementation plan
•A
set of product standards
• For
infrastructure
• Concerned • An
only with technology
end in and of itself
These are parts of an architecture, but they are not an architecture by themselves.
November 26, 2009
10
Approach • Approach
is a mature, fully supported suite of methodologies that enable the delivery of offerings and services that provides: − A set of best-in-class methodologies to support for the management and delivery of business − One-stop shop for methods, tools, and techniques − Guides and templates
November 26, 2009
11
Approach to ITSA − Based on stakeholder participation − Organised as a set of four fundamental views
Business view Functional view
Stakeholders
Technical view
Implementation view
November 26, 2009
12
The Four ITSA Views — Building a House Analogy Business view Why do I want a new house?
Technical view How will it be built?
• residence, entertainment, business • affordability • location • independence • image
• foundation, framing, heat/ac, plumbing, ... • utilities: - electric, water, comms, roads • security systems • controls • materials
Functional view What should the new house give me?
Implementation view With what will it be built?
• • • •
• sourcing - suppliers - specific models • financing • phasing • moving
uses / room layouts peace & quiet, security garden, trees garage, pet needs
November 26, 2009
13
Business View Why are we doing this? ty ili Ag
• Key
questions: oS Q st Co
− What are the internal and external drivers? − What are the business models and processes? − Who participates in the business processes? − What are the project goals? − How will the success of the solution be measured?
sk Ri
November 26, 2009
14
Functional View What should the solution do? ty ili Ag
Key questions:
st Co
• How will it be used and what services will it provide? • What information will it provide? To whom?
oS Q
• What will the completed solution do?
• What qualities must the solution have? sk Ri
November 26, 2009
15
Technical View How should the solution work? ty ili Ag
Key questions: • What are the interfaces and other constraints?
oS Q
• How will the system be structured and constructed? • What applications and data are needed?
st Co
• What does the infrastructure look like? • What standards will apply?
November 26, 2009
sk Ri
• How will the system qualities be achieved?
16
Implementation View
ty ili Ag
With what will the solution be built? Key questions:
sk Ri
November 26, 2009
st Co
• How will the system be developed and deployed? • What validation methods will be used? • How will it be managed? • What is the source of funding?
oS Q
• What specific products and components, from which vendors, are needed to build the system?
17
ITSA Framework and Methodologies
ITSA Methodologies Solution Architecture Concept
Solution Architecture Blueprint
ITSA Framework
November 26, 2009
18
ITSA Framework The fundamental architectural elements of the ITSA framework are: •Business drivers, goals, and metrics (closely associated with the business view •Principles, models, and standards (associated with each of the four views)
November 26, 2009
19
In Summary The approach for creating solution architecture is: − Based on stakeholder participation − Organised as a set of four fundamental views − Motivated by key business drivers, goals, and metrics − Expressed as a set of principles, models, and standards − Linked to actions to ensure timely progress − Supported by an extensible framework of methods, tools, and techniques November 26, 2009
Business view Functional view Technical view Implementation view
20
Contrasting Solution Architecture and Project management Solution Architecture • Defines engagement scope • Articulates the essential elements of the solution and work to be done • Defines resources needed to complete the work • Defines acceptance criteria for solution iterations and phases • … o d to t ha W
November 26, 2009
Project Management • Keeps engagement within scope • Ensures the work breakdown structure covers all the essential elements • Ensures staffing, funding, and resources are available to support the work • Defines milestones, and schedule and ensures acceptance criteria are met • … ne o d t i et g to w Ho 21
Contrasting Solution Architecture and Traditional Engineering Solution Architecture • Finds satisfactory system concepts for ill-defined problems • More art than science, heuristic in nature
n o d ds e s cu t nee o F en cli
November 26, 2009
Traditional Engineering • Finds optimal solutions to wellunderstood problems • More science than art, algorithmic in nature on d se ry u e c Fo eliv d
22
Solution Architecture Concept •A
rapid review of the key elements of a proposed solution, examining each of the four views − Focus on business drivers/goals, principles, models, and standards − Determine feasibility of an effective solution based on obstacles and constraints − Purpose: define solution’s conceptual architecture to facilitate well-informed, rapid decisions and get shared stakeholder understanding of, and commitment to, the proposed solution
November 26, 2009
23
Solution Architecture Blueprint
•A
detailed architectural description of a project, initiative, or enterprise architecture.
• Works
with you to:
− Establish an agreed-to, sufficient solution concept − Define, design, and document all essential features of the solution − Analyse the feasibility of the solution − Plan the implementation of the solution
November 26, 2009
24
IT Strategy and Architecture Framework Business drivers Goals
November 26, 2009
Business view
Functional view
Technical view
business principles
functional principles
technical principles
Implementation view implementation principles
rationales
rationales
rationales
rationales
implications
implications
implications
implications
obstacles
obstacles
obstacles
obstacles
Actions
Actions
Actions
Actions 25
More Information Alan McSweeney [email protected]
November 26, 2009
26
Related Documents
Approach To It Strategy And Architecture
June 2020 5
Wa Approach To It P1-40
May 2020 7
It Strategy For Business
June 2020 7
Design Strategy Report_finish It!
May 2020 7
It Infrastructure Strategy And Charter Toc
May 2020 3
More Documents from "nurul"
Business Cases And Benefits Management
June 2020 8
