Friday, November 17, 2006

Introducing ICT Enterprise Architecture



This is an open content presentation on enterprise architecture. The target users are ICT Service Manager and Executive, Administrator, and Corporate Planner.

The goal is to build a common reference, terminology, and practices on enterprise architecture to support the strategic and tactical goals of government, education and SME through information and communications technology.

It brings a "get started" guidance to usher in an integrative process approach in assessment, development, delivery and support of the enterprise wide ICT architecture envisioned to meet the strategic business and service goals of the organization.


Enterprise Architecture Definition: (from EWITA)

Enterprise Architecture is generally defined in terms of its constituent architectures, namely:

  • Business architecture

  • Application/software architecture

  • Technology/infrastructure architecture

  • Information architecture

A fairly general definition of architecture in the system space (versus civil or building architectures), is:

Architecture is the high-level definition of the structure of a system, which is comprised of parts, their interrelationships, and externally visible properties.

With this definition in mind, it is all the more obvious that Enterprise Architecture is more than the collection of the constituent architectures (Business, Application, Technology, and Information). The interrelationships among these architectures, and their joint properties, are essential to the Enterprise Architecture. That is to say, these architectures should not be approached in isolation. Together, they are intended to address important Enterprise-wide concerns, such as:

  • meeting stakeholder needs

  • aligning IT with the business

  • seamless integration and data sharing

  • security and dependability

  • data integrity, consistency

  • reducing duplication

Treating the Enterprise as a system, means taking the interactions among the constituent architectures into account. By the same token, the whole point of breaking a system into parts is so that task is less overwhelmingly complex, and specialists can focus on the parts and make progress.

Training Program

Three (3) Days Introductory Course on Enterprise Architecture

Enterprise Architecture provides a comprehensive definition and modeling view of the business processes and the supporting ICT services and infrastructure. It defines the standards to understand business process, information requirements, data elements, application suitability, and technology infrastructure.

It brings an integrative visualization and documentation of the relationship between people, process, technology and data in the organization. Enterprise Architecture is a necessity to insure ICT investments and development are aligns to the strategic goals and service ends of the organization.

Day 1:
The Context and Framework of Enterprise Architecture

Morning:
a.
Enterprise, Architecture, Government ICT Enterprise Architecture
b. People, Process, Data, Technology

Afternoon:
a. Zachman EA Framework
b. OpenGroup EA Framework
b. NASCIO EA Development Framework

Day 2
: The EA Domains

Morning:
a. Business Architecture
b. Information Architecture

Afternoon:
a. Application Architecture
b. Technology Architecture

Day 3:
Enterprise Architecture Implementation

a: Process
b. Deliverables