Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Approach to  IT Strategy and Architecture Alan McSweeney
The Adaptive Enterprise Business and IT synchronised to capitalise on change Business Information Technology Business bene...
Learn to love what you’ve been taught to fear… <ul><li>Change is constant </li></ul><ul><li>Everyday events send ripples t...
Darwin Reference Architecture Business strategy Business processes Management Infrastructure <ul><li>Brings standardisatio...
Adaptive Enterprise Design Principles Integration Simplification Standardisation Modularity + + + <ul><li>Applied consiste...
How Do We Define Solution Architecture? <ul><li>Benefits </li></ul><ul><ul><li>Aligns business and information contexts wi...
CIO Balancing Act <ul><li>Mitigate risk: </li></ul><ul><li>Ensure security and continuity  of internal business operations...
Solution Architecture Bridges the Business and IT Gap Solution Architecture Business Problem IT Solution Business/IT Align...
Architecture Scope  Building architecture Information system architecture Discrete  (project) Examples:  e-procurement, em...
Solution Architecture is Not Just… <ul><li>A detailed implementation plan  </li></ul><ul><li>A set of product standards </...
Approach <ul><li>Approach is a mature, fully supported suite of methodologies that enable the delivery of offerings and se...
Approach to ITSA <ul><ul><li>Based on stakeholder participation </li></ul></ul><ul><ul><li>Organised as a set of four fund...
The Four ITSA Views – Building a House Analogy Business view Implementation view <ul><li>Why  do I want a new house? </li>...
Business View <ul><li>Key questions: </li></ul><ul><ul><li>What are the internal and external drivers? </li></ul></ul><ul>...
Functional View <ul><li>Key questions: </li></ul><ul><ul><li>What will the completed solution do? </li></ul></ul><ul><ul><...
Technical View <ul><li>Key questions: </li></ul><ul><ul><li>How will the system be structured and constructed? </li></ul><...
Implementation View <ul><li>Key questions: </li></ul><ul><ul><li>What specific products and components, from  which vendor...
ITSA Framework and Methodologies Solution  Architecture  Concept Solution Architecture Blueprint ITSA Methodologies ITSA F...
ITSA Framework <ul><li>Business drivers, goals, and metrics (closely associated with the business view </li></ul><ul><li>P...
In Summary <ul><li>The approach for creating solution architecture is: </li></ul><ul><ul><li>Based on stakeholder particip...
Contrasting Solution Architecture and Project management  <ul><li>Solution Architecture </li></ul><ul><ul><li>Defines enga...
Contrasting Solution Architecture and Traditional Engineering <ul><li>Traditional Engineering </li></ul><ul><ul><li>Finds ...
Solution Architecture Concept <ul><li>A rapid review of the key elements of a proposed solution, examining each of the fou...
Solution Architecture   Blueprint <ul><li>A detailed architectural description of a project, initiative, or enterprise arc...
IT Strategy and Architecture Framework Actions Actions implementation principles rationales implications obstacles Impleme...
More Information <ul><ul><ul><li>Alan McSweeney </li></ul></ul></ul><ul><ul><ul><li>[email_address]   </li></ul></ul></ul>
Upcoming SlideShare
Loading in …5
×

of

Approach To It Strategy And Architecture Slide 1 Approach To It Strategy And Architecture Slide 2 Approach To It Strategy And Architecture Slide 3 Approach To It Strategy And Architecture Slide 4 Approach To It Strategy And Architecture Slide 5 Approach To It Strategy And Architecture Slide 6 Approach To It Strategy And Architecture Slide 7 Approach To It Strategy And Architecture Slide 8 Approach To It Strategy And Architecture Slide 9 Approach To It Strategy And Architecture Slide 10 Approach To It Strategy And Architecture Slide 11 Approach To It Strategy And Architecture Slide 12 Approach To It Strategy And Architecture Slide 13 Approach To It Strategy And Architecture Slide 14 Approach To It Strategy And Architecture Slide 15 Approach To It Strategy And Architecture Slide 16 Approach To It Strategy And Architecture Slide 17 Approach To It Strategy And Architecture Slide 18 Approach To It Strategy And Architecture Slide 19 Approach To It Strategy And Architecture Slide 20 Approach To It Strategy And Architecture Slide 21 Approach To It Strategy And Architecture Slide 22 Approach To It Strategy And Architecture Slide 23 Approach To It Strategy And Architecture Slide 24 Approach To It Strategy And Architecture Slide 25 Approach To It Strategy And Architecture Slide 26
Upcoming SlideShare
IT strategy
Next
Download to read offline and view in fullscreen.

44 Likes

Share

Download to read offline

Approach To It Strategy And Architecture

Download to read offline

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Approach To It Strategy And Architecture

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

    Feb. 21, 2021
  • AaronDolan6

    Feb. 6, 2021
  • tgroenwa

    Jan. 4, 2021
  • Sergebouwens

    Nov. 16, 2020
  • kitkatneko

    Aug. 10, 2020
  • octalxia

    Jul. 22, 2020
  • jerryprimus

    Feb. 20, 2020
  • NabazMawlood1

    Jan. 24, 2020
  • nomi841

    Jan. 24, 2020
  • tomlee714

    Aug. 15, 2019
  • IoanSandru

    Apr. 14, 2019
  • samserero

    Feb. 27, 2019
  • ZubinZubi

    Feb. 10, 2019
  • ksbaxter

    Feb. 10, 2019
  • kdw91

    Oct. 15, 2018
  • RuthEastham

    Jul. 24, 2018
  • aim881

    Mar. 19, 2018
  • ChrisSlee2

    Jan. 8, 2018
  • ArmonJamesForonda

    Dec. 12, 2016
  • TomiLaurell

    Dec. 11, 2016

Views

Total views

19,971

On Slideshare

0

From embeds

0

Number of embeds

97

Actions

Downloads

1,677

Shares

0

Comments

0

Likes

44

×