Enterprise Architecture

HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT

Why Enterprise ArchitectureDefinition: EA translates business vision and strategy into change

How? By creating, communicating and improving key requirements, principles, models

to describe future state Enterprise Architects do what: compose holistic solutions that address the business challengesAlign IT with the businessSupport the business by providing the fundamental technology and process structure for an IT strategyWhat does that mean anyway?

Benefits of Enterprise Architecture

IT alignment with business goals – an IT plan that shares the vision of the future

Integration (need for rapid business change means we need business and IT integration)• We use methodologies and frameworks to integrate functions, processes, data, locations, people,

events and business plans• To achieve integration, we use enterprise portals, web services, service oriented architecture (SOA),

business process management (BPM) and try to lower the number of interfaces

Change Management

Reduced time to market and increased IT responsiveness

Better access to information across applications and improved interoperability• Identify overlapping functional scope and consolidate architectures for: shared enterprise services,

applications and information, technologies and data centres

Benefits of Enterprise Architecture…continued

Reduced time to market and increased IT responsiveness

Better access to information across applications and improved interoperability

Readily available descriptive representation of documentation of the enterprise

Reduce IT costs by consolidating, standardizing, rationalizing and integrating corporate information systems

More Spending on innovation

Enabling strategic goals via better operational excellence

Customer intimacy (business model, IT systems and operational activities designed to support customer focus strategy)

Enterprise ArchitectureEnterprise Architecture = Strategy + business + technology

Enterprise ArchitectureCurrent Architecture to future architecture

Enterprise ArchitectureExamples of EA components

Enterprise ArchitectureEvaluating current capabilities and designing future capabilities

Enterprise Architecture Phase 1: Goals and Initiatives

• Goals and initiatives, why does the enterprise exist (mission statement)• Where do we intend to be (vision statement)• Primary goals (strategic goals)• What are the current strategic initiatives • How will we measure our success

Phase 2: Products and Services• Lines of business to support the strategic initiatives and maintenance/housekeeping functions• Specific activities/products/services in each line of business• How do we measure the success of each line – how does each line contribute to the strategic goals• Do we need to re-engineer any of the business or manufacturing processes so that they can fit with the future architecture

Enterprise Architecture Phase 3: Data and Information

• Flows of data within and between activities• How can we harmonize, standardize protect this data for efficient sharing• How will the data be generated, shared and stored• How will the data become useable knowledge

Phase 4: Systems and Applications• Application systems used and what they need to generate to serve business needs• How can IT systems work together• Common operating Environment

Phase 5: Network and Infrastructure• Physical space and utility support requirements to support IT systems

Enterprise Architecture Methodologies - Zachman

A framework for organizing all architectural artifacts of an organization from the perspective of a target individual or group (ex. Of building)

Enterprise Architecture Methodologies - Zachman

Enterprise Architecture- TOGAF

Enterprise Architecture- TOGAF