Business 2.0 Business and IT fusion <br />Lecture 5:  Architecture<br />Dr Raymond Young (MBA, GAICD) <br />Raymond.young@...
IT Strategic planning process linkages<br />Risks,<br />Benefits,<br />Effort, Disruption,<br />Consequences of not doing ...
The link between EA and strategyhttp://knol.google.com/k/the-notion-of-enterprise-architecture-ea#<br />
An example using a city <br />
What creates the need for EA?<br />Vendors target marketing, sales, customer support, HR, etc ... frequently without invol...
Why define your Enterprise Architecture<br />Ensure integration of:<br />Critical data<br />Key applications<br />Enforcem...
How to define your EACIO Wisdom (2004) pp157-158<br />Start with customer channels (not Functions): how products/services ...
Relationships within an EACIO Wisdom (2004) pp157<br /><ul><li>DS3, T1, VPN
Firewalls & DMZs
Routers, switches
Network cables, NIC, wireless
Browsers,</li></li></ul><li>Other HintsCIO Wisdom (2004) pp161<br />KISS, link to business culture<br />Stay in touch with...
Upcoming SlideShare
Loading in...5
×

Bus2.0 - IT architecture

722

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
722
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Bus2.0 - IT architecture"

  1. 1. Business 2.0 Business and IT fusion <br />Lecture 5: Architecture<br />Dr Raymond Young (MBA, GAICD) <br />Raymond.young@canberra.edu.au<br />
  2. 2. IT Strategic planning process linkages<br />Risks,<br />Benefits,<br />Effort, Disruption,<br />Consequences of not doing it?<br />Cost of project ?<br />Infra Project 2<br />Apps Project 1<br />Apps Project 2<br />Apps Project 3<br />Web Project 1<br />Infra Project 1<br />Web Project 2<br />Budget Cycles<br />Business Planning Cycles<br />Results – KPI’s and Metrics<br />IT Change/Configuration Management<br />IT Portfolio Management<br />IT Migration Planning<br />Web / Application Strategy<br />IT Infrastructure<br />Enterprise Architecture<br />Business Strategies<br />Source: CIO Wisdom (2004) p230<br />
  3. 3. The link between EA and strategyhttp://knol.google.com/k/the-notion-of-enterprise-architecture-ea#<br />
  4. 4. An example using a city <br />
  5. 5. What creates the need for EA?<br />Vendors target marketing, sales, customer support, HR, etc ... frequently without involvement of IT.<br />Unfortunately, the business users do not typically understand the potential architecture, implementation and support issues, and do not ask all the pertinent questions...<br />Investing time up front defining the architecture avoids frustration and expense later in the process as the organisation grows (c.f. Smith (2006) p68)<br />Stability, costs (maintenance, staff), flexibility to expand/modify, fit for purpose<br />
  6. 6. Why define your Enterprise Architecture<br />Ensure integration of:<br />Critical data<br />Key applications<br />Enforcement of corporate policies<br />Security<br />Controls<br />Data privacy<br />Common service levels<br />Unified user interface (to facilitate intuitive use)<br />Implications for:<br />Operations & internal processes<br />Resourcing<br />Budgeting <br />ROI<br />
  7. 7. How to define your EACIO Wisdom (2004) pp157-158<br />Start with customer channels (not Functions): how products/services are delivered to customers<br />Business Processes / Rules & Functions<br />Technical elements<br />Network infrastructure & Navigation<br />Common views of information<br />Applications<br />Databases<br />
  8. 8. Relationships within an EACIO Wisdom (2004) pp157<br /><ul><li>DS3, T1, VPN
  9. 9. Firewalls & DMZs
  10. 10. Routers, switches
  11. 11. Network cables, NIC, wireless
  12. 12. Browsers,</li></li></ul><li>Other HintsCIO Wisdom (2004) pp161<br />KISS, link to business culture<br />Stay in touch with industry direction and incorporate into plans<br />Projects – have architectural reviews early in lifecycle, and update with new information<br />Follow Standards<br />Zachman Framework (1980)<br />Set goals 6-18 months ahead<br />Migration plan for non-compliant systems<br />Keep decisions within each layer (otherwise cannot easily upgrade over time)<br />
  13. 13.
  14. 14. An example of an Enterprise Architecturehttp://www.google.com.au/images?hl=en&q=example%20of%20an%20enterprise%20architecture&um=1&ie=UTF-8&source=og&sa=N&tab=wi&biw=938&bih=647<br />
  15. 15. Questions & Discussion<br />Negotiate good policies with the business<br />e.g. Non-standard & Pirate s/w, virus checker?<br />

×