Enterprise Architecture

week 1

Enterprise architecture

Documentation and description if current and desried relationships among business processes and IT systems

value of EA (4)

Align IT planning with business goals , manage IS risk , optimise use of IS recourses , provides flexibility , framkework for decision making

EA domains (4)

Business Architecture , Data Architecture , Applications Architecture , Technology Architecture

Business Architecture

describes business functions

Data Architecture

Defines how data is stored

Application architecture

structure interaction of software apps within a business

technology architecture

defines hardware, software,network and security

Zachman Framework

two dimensional matrix defining architecture perspectives and aspects

The Open Group Architecture Framework

provides an architecture development method from business goals

Federal Enterprise (FEA)

Consists of interrelated reference models for cross-agency analysis and idenitfy duplicative investments

EA governance

Harmonise architectural requirements into policies and standards

Components of effective EA governence

Architecture Review Process , standards management process , roadmap management process,

Business Executives EA document

explains the planning decesions

IT executives EA document

details implications for IT strategy

Business Unit Managers EA document

Describes impact on business processes

IT project teams EA document

specifies implications for IT projects

Third party EA documents

clarifes implications for contract structures

Intergration domain

interfaces, connections, protocols, platforms

Business-Enabling Domains

define core IT system functionality

Business-Supporting Domains

non-functional requiremnts.

Types of EA artifacts (3)

Decision , facts and lifecycle