Академический Документы
Профессиональный Документы
Культура Документы
IT Strategy and
Architecture
Alan McSweeney
The Adaptive Enterprise
Business
Information Technology
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.
+
• Use standard technologies and interfaces Applied
Standardisation • Adopt common architectures consistently
• Implement standard processes across:
+ • Business
processes
• Break down monolithic structures
• Applications
Modularity • Create reusable components
• Implement logical architectures • 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?
• 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:
• Enable the business
organisation and operations to
Maximise return: adapt to changing business
• Improve business results; needs
grow revenue and earnings,
cash flow, and reduced
cost of operations
Improve performance:
Mitigate risk: • Improve business operations
• Ensure security and continuity performance end-to-end
of internal business operations, across the enterprise
while minimising exposure to • Increase customer and employee
external risk factors satisfaction
Business/IT Alignment
Building
architecture
Business
view
Functional
view
Stakeholders Technical
view
Implementation
view
Ag
ili
ty
• Key questions:
− What are the internal and external drivers?
Q
oS
− What are the business models and processes?
− Who participates in the business processes?
− What are the project goals?
Co
st
− How will the success of the solution be
measured?
Ri
sk
November 26, 2009 14
Functional View
Ag
ili
ty
Key questions:
• What will the completed solution do?
Q
oS
• How will it be used and what services will it
provide?
• What information will it provide? To whom?
Co
st
• What qualities must the solution have?
Ri
sk
November 26, 2009 15
Technical View
Ag
ili
ty
Key questions:
• How will the system be structured and constructed?
Q
oS
• What are the interfaces and other constraints?
• What applications and data are needed?
Co
• What does the infrastructure look like?
st
• What standards will apply?
• How will the system qualities be achieved?
Ri
sk
November 26, 2009 16
Implementation View
Ag
ili
ty
Key questions:
• What specific products and components, from
Q
oS
which vendors, are needed to build the system?
• How will the system be developed and deployed?
• What validation methods will be used?
Co
st
• How will it be managed?
• What is the source of funding?
Ri
sk
November 26, 2009 17
ITSA Framework and Methodologies
ITSA Methodologies
Solution Solution
Architecture Architecture
Concept Blueprint
ITSA Framework
d on
o n se ry
e d ds c u e
s
cu t nee Fo eliv
o
F en d
cli
Business
drivers Implementation
Business view Functional view Technical view
view
business functional technical implementation
Goals
principles principles principles principles
Alan McSweeney
alan@alanmcsweeney.com