The document discusses enterprise architecture (EA), including its linkages to strategic planning processes, budgets, and business strategies. It explains why defining an EA is important to ensure integration of critical data, applications, policies and more. The document provides guidance on how to define an EA, starting with customer channels and business processes, then technical elements. Maintaining standards, industry directions and architectural reviews of projects are also recommended. An example EA diagram is referenced for further illustration.

1. Business 2.0 Business and IT fusion Lecture 5: ArchitectureDr Raymond Young (MBA, GAICD) Raymond.young@canberra.edu.au

2. IT Strategic planning process linkagesRisks,Benefits,Effort, Disruption,Consequences of not doing it?Cost of project ?Infra Project 2Apps Project 1Apps Project 2Apps Project 3Web Project 1Infra Project 1Web Project 2Budget CyclesBusiness Planning CyclesResults – KPI’s and MetricsIT Change/Configuration ManagementIT Portfolio ManagementIT Migration PlanningWeb / Application StrategyIT InfrastructureEnterprise ArchitectureBusiness StrategiesSource: CIO Wisdom (2004) p230

3. The link between EA and strategyhttp://knol.google.com/k/the-notion-of-enterprise-architecture-ea#

4. An example using a city

5. What creates the need for EA?Vendors target marketing, sales, customer support, HR, etc ... frequently without involvement of IT.Unfortunately, the business users do not typically understand the potential architecture, implementation and support issues, and do not ask all the pertinent questions...Investing time up front defining the architecture avoids frustration and expense later in the process as the organisation grows (c.f. Smith (2006) p68)Stability, costs (maintenance, staff), flexibility to expand/modify, fit for purpose

6. Why define your Enterprise ArchitectureEnsure integration of:Critical dataKey applicationsEnforcement of corporate policiesSecurityControlsData privacyCommon service levelsUnified user interface (to facilitate intuitive use)Implications for:Operations & internal processesResourcingBudgeting ROI

7. How to define your EACIO Wisdom (2004) pp157-158Start with customer channels (not Functions): how products/services are delivered to customersBusiness Processes / Rules & FunctionsTechnical elementsNetwork infrastructure & NavigationCommon views of informationApplicationsDatabases

8. Relationships within an EACIO Wisdom (2004) pp157DS3, T1, VPN

9. Firewalls & DMZs

10. Routers, switches

11. Network cables, NIC, wireless

12. Browsers,Other HintsCIO Wisdom (2004) pp161KISS, link to business cultureStay in touch with industry direction and incorporate into plansProjects – have architectural reviews early in lifecycle, and update with new informationFollow StandardsZachman Framework (1980)Set goals 6-18 months aheadMigration plan for non-compliant systemsKeep decisions within each layer (otherwise cannot easily upgrade over time)