alternate text alternate text alternate text alternate text

IFEAD

People -- Process -- Business -- Technology
IFEAD is an independent research and information exchange organization working on the future state of Enterprise Architecture.

Enterprise Architecture Best Practices & White Papers

-

The USA National Association of State Chief Information Officers (NASCIO), which represents the chief information officers (CIOs) of the states, is pleased to announce the release of its research brief, Service Oriented Architecture: an Enabler of the Agile Enterprise. The brief identifies what state CIOs need to know now regarding Service Oriented Architecture (SOA), including its business value, the vision for SOA, SOA governance, SOA as a program and SOA security.

This research brief, an important resource for CIOs and state chief architects, also provides an excellent overview of SOA for non-technical government professionals at all levels of government. SOA promises to be a significant innovation for state government that will provide the ability to pick and choose business and technology services, and will allow the trade out of services based on organizational re-design, new strategic intent, legislative requirements, or business process modifications.

“SOA promises to bring significant business value out of existing IT assets through increased operational efficiencies, optimized business processes, and the ability to adapt and change quickly,” said Utah CIO Stephen Fletcher. "Providing flexible access to information across platforms and languages can be complex and resource intensive. Service Oriented Architecture simplifies this through standard protocols which treat all platforms equally. This allows us to offer data services to a wide variety of business partners with requests that can originate from anywhere."

Service Oriented Architecture: an Enabler of the Agile Enterprise is avaliable for download


Enterprise Architecture Consulting Services (EACS) is a proven source for research & best practices based EA measurement tools, EA development & implementation programs and strategic advisory services. Enterprise Architecture Consulting Services is working close together with the research people from the Institute For Enterprise Architecture Developments (IFEAD).

In just five years, IFEAD has developed a world wide position in the EA research & development arena with its EA frameworks, methods, opinions and approaches, etc.

EACS has leveraged this understanding of EA organizational and technological behavior to develop their surveys and consulting services to apply to a wide variety of organizations with one single purpose in mind: Enterprise Architecture is a complete expression of the enterprise; a master plan which “acts as a collaboration force” between aspects of business planning such as goals, visions, strategies and governance principles; aspects of business operations such as business terms, organisation structures, processes and data; aspects of automation such as information systems and databases; and the enabling technological infrastructure of the business such as computers, operating systems and networks.

Enterprise Architecture Consulting Services professionals deliver EA advisory services via the web, at client sites and at EA leadership conferences around the world.

EACS; EA Consulting Services:

Fore more info about EACS visit the website at http://www.ea-consulting.com


OMB releases EA Assessment

The Office of Management and Budget has the second version of its Enterprise Architecture Assessment Framework. Agencies have until Feb. 28 to submit their EA materials under this guideline, according to a memo issued by Richard Burk, director of the Federal Enterprise Architecture Program Management Office.

Last year, OMB announced it would evaluate how well agencies complete and utilize their EAs to save money, improve services and meet their missions overall. OMB will use this assessment to evaluate agency EAs as part of the second quarter 2006. President’s Management Agenda Scorecard.

Version 2.0 of the assessment framework supersedes Version 1.5, published last year. While Version 1.5 focused on gauging how well agencies completed their baseline EAs, Version 2 looks at how well an agency actually uses its EA, and what results the agency gets from the EA.

Download OMB EA Assessment Framework Version 2.0 here.


Is proud to Announce the Report 'Trends in Enterprise Architecture' 2005

How are Organizations Progressing?

Results of the Third Measurement


This report presents the results of the third electronic survey, executed by the Institute For Enterprise Architecture Developments (IFEAD)©, 2005, on the progress of Enterprise Architecture (EA) usage & implementations in several organizations all over the world.

This third survey is part of a yearly recurrent survey to measure the progress and developments in Enterprise Architecture. The survey is based on a 25 questions survey, addressing geographical aspects, branch aspects, EA implementations aspects as well about tools and methodologies used in Enterprise Architecture programs and the role of architects in organizations.

Where possible an overview will be given of the results of 2005, 2004 and 2003 and an analysis and explanation of exceptions. All geographic areas are represented in the survey as well as different sizes of organizations. All the source information is copyrighted and based on the EA Survey's 2005, 2004 and 2003 executed by the Institute For Enterprise Architecture Developments (IFEAD) 2005.

This report 'Trends in Enterprise Architecture 2005' can be downloaded from this site (2.27Mb pdf).

© Copyright, Institute For Enterprise Architecture Developments (IFEAD), 2005 – All Rights Reserved. No part of this report may be reproduced or transmitted in any form or by any means, electronic, mechanical, including photocopying, recording, or by any information storage and retrieval system, without the express written permission of the copyright holder.


A Review with dramatic results of the
US FBI’s Trilogy IT
Modernization Program

A report recently released by the Computer Science and Telecommunications Board (CSTB), which is empowered by the National Research Council, points out planning flaws in the FBI's Trilogy program. It is a rare and deep look into a failed promise to quickly modernize. The report concludes that, after many improvements, the program is not yet on track to success.

'The number one problem is the FBI's enterprise architecture. They didn't have one,' said Mr. Orr a member of the CSTB , who noted problems with the project's data architecture as well. Naturally, this is expanded upon in the full report.

The report notes that management of enterprise architecture design cannot be farmed out of an organization, nor can it be entrusted solely to a CIO within an organization. True management buy-in is also needed. The senior leadership of the FBI needed to be directly involved in creating this strategic view and supporting its implementation.

Download here the full report 2079Kb PD


Enterprise Architecture Reference Models:
A Shared Vision for Service-Oriented Architectures

By Tim Bass, Silk Road; bass@silkroad.com and Roy Mabry, DoD OCIO ASD/NII; roy.mabry@osd.mil

The business- and mission-driven objectives of service-oriented architectures depend on the dynamic interaction of collaborative integrated operations in a federated operational environment. The theme of this paper is that integrated operations can and should be considered service-oriented nodes in a dynamic information environment. In the Department of Defense, this dynamic information environment has often been referred to as “the global information grid” or simply “the grid.” We describe enterprise architecture reference models as a dynamic abstract reference environment for net-centric collaboration between the service-oriented “nodes on the grid.” The complex, dynamic interaction of service-oriented nodes in the net-centric environment creates an opportunity to view enterprise architecture as a taxonomy of well-defined systems architectures governed by a set of enterprise architecture reference models.

Download this paper here (PDF 553 Kb)


US-Government Agency EA documents collection


GCN's EA Resource Center tracks development of federal agency systems blueprints using the Federal Enterprise Architecture as a template.
Links to each agency's key enterprise architecture documents and models now available.


Microsofts Architecture View

This document is intended for business, software, and infrastructure architects who want to understand Microsoft's approach to enterprise, application, and technology architectures. It covers architectural terminology, patterns, concepts, and definitions as a series of views or levels of architecture.


ENTERPRISE ARCHITECTURE For Distributed Data Integration

Web-Seminar of Forrester and Avaki about Enterprise Architecture For Dustributed Data Integration.


Industry Advisory Councel 'ENTERPRISE ARCHITECTURE WHITE PAPERS'

White papers developed for the Federal Enterprise Architecture Program Management Office (FEA-PMO) by the Industry Advisory Council (IAC) Enterprise Architecture SIG.

Advancing Enterprise Architecture Maturity (PDF)

Business Line Architecture & Integration (PDF)

Interoperability Strategy - Concepts, Challenges, and Recommendations (PDF)

Succeeding with Component-Based Architecture in e-Government (PDF)


How Differentiate Enterprise Architects from Engineers & Designers

Architecture in the world of Enterprise Architects is addressing 3 major areas in a holistic way: The area of construction, the area of function and the area of style. Style is reflecting the culture, values, norms and principles of an organization. Most of the time, the term architecture is dealing with construction and function, without any attention of the style aspect, while the style aspect reflects the cultural behavior, values, norms and principles of that organization in such a way that it reflects the corporate values of that organization. So my statement is that Architecture differentiate from Engineering and Design by the fact of explicitly incorporating and reflecting the style characteristics in the results of the work of an Architect. So don't call every designer or engineer, architect, because it are different roles with different capabilities.


US-GAO defines Enterprise Architecture benchmarks

Responding to agency requests, the General Accounting Office has updated its guide on enterprise architectures with expanded metrics to measure how well an agency succeeds in implementation.

The update, "Information Technology: A Framework for Assessing and Improving Enterprise Architecture Management," (426Kb pdf) provides benchmarking tools for agencies to plan and measure their efforts in developing enterprise architectures. It also provides guidelines for the Office of Management and Budget to evaluate agency efforts.

The report was updated using feedback from the release of the first version, published February 2002 and entitled, “Information Technology: Enterprise Architecture Use Across the Federal Government Can Be Improved.”

This update expands the performance measurements identified in the first report. It defines attributes critical for success and offers a matrix to gauge how mature an agency’s architecture is.

The report defines an enterprise as any activity that an agency executes. The architecture characterizes how that activity is structured.


'InfoCitizen'

European Enterprise Architecture Project

2001-2003 InfoCitizen project aims at:
• establishing a common Enterprise Architecture among the participating EU countries tested in representative public administration segments, and
• deploying a distributed, Internet-based information system that supports the above for all actors involved (citizens, administrations, private sector), building on emerging technologies (e.g. mobile agents, middleware, xml) and solving incompatibilities and complexities that exist today.

To achieve this, InfoCitizen employs concepts from the fields of public administration, enterprise architectures and systems integration, generic process and data modelling and metadata standards (e.g. xml) in order to classify and organize information regarding a citizen/business oriented process in all participating countries.

The addressed domain for the InfoCitizen project is the achievement of a highly interoperable organisational model for the European Public Administrations and the development of the corresponding IT infrastructure, facilitating services at two levels:

  • the inter-Administration level; concerning communications and interactions between Public Administrations (A2A, i.e. Administration to Administration)
  • the Administration to Citizen level; concerning communications and interactions between Public Administrations and citizens (A2C, i.e. Administration to Citizen).

Info Citizen Project Presentation (1027Kb)

Project Document

This deliverable is separated into two parts: At the first part a user scenario has been identified (Marco's case) and requirements analysis of all four user-partners (Schmelz-Germany, Thessaloniki-Greece, Colleferro-Italy, Tres Cantos-Spain) together with detailed descriptions of the business processes performed by each one during the scenario execution are documented using the UML notation. At the second part we lay out the scoping of the project and propose requirements for building the InfoCitizen architecture. Prerequisites for developing a pan-European approach have been also included in this part. At the second part we lay out the scoping of the project and propose requirements for building the InfoCitizen architecture. Prerequisites for developing a pan-European approach have been also included in this part. (1166Kb)


Downloads

State of the Art Analysis

This report presents the State-of-the-Art of methodologies, frameworks and technologies that InfoCitizen may imply in order to achieve the goal of Integration and Interoperability among European Public Administration organizations. It is structured in three main parts presenting (a) conceptual (design) ideas, (b) technical (implementation) ideas and (c) cases of relevant projects/initiatives from the European Union and the USA. (1097Kb)


Business Processes

In this report the user partners of the INFOCITIZEN consortium identified and agreed upon the business areas for which they are to a large degree responsible and which are of major significance to them. These areas pertain to: Registration, Work Permission, Social Services, Booking of Services. The general description documents the respective public administration unit that each user partner corresponds to, namely a municipality in three countries and a prefecture in a fourth. This documentation leads to a high-level understanding and ability to compare (i.e. commonalities, differences) amongst the corresponding administrative units for the participating countries. The selected process areas were then described by their respective processes. Each such process was both documented textually and analyzed by building ARIS business process models. (2083Kb)

Report on InfoCitizen Enterprise Architecture prototpye (NEW)

The InfoCitizen European Architecture is the conceptual basis for the InfoCitizen system and its components. It contains the necessary models and descriptions that have been developed in order to fulfil the requirements analysed in WP1 and that meet the goal of developing an interoperable system integrating business processes in European Public Administrations. The InfoCitizen European Architecture is divided into three parts:

o The conceptual part, defining the business processes, information objects and the basic interoperability mechanisms (InfoCitizen Conceptual Architecture).

o The technical description, defining the structure of the InfoCitizen Platform, its various components that compose the platform as well as the interrelationships amongst them (InfoCitizen Technical Architecture).

o The system description, detailing the software-technical consequences and limitations exposed by the overall architecture. (2406Kb)


Enterprise Architecture Score Card

Today the area of (enterprise) architecture in the virtual digital world will become more and more full-grown. So the focus is changing to the quality of the work of enterprise architects. How can we review the results of the work of (enterprise) architects and how can we review their process. Can we define quality criteria to validate the products and results from other architects?

 


'The Uncontrolled Distribution of Components'

The rise of distributed information systems generates new challenges in system development. During the design phase one needs to answer the question “how do I partition my information system, where do I place the components and how do these components depend on each other ”. In order to solve this distribution problem, one needs to survey the entire information system, including its environment, and consider the additional design criteria from a distribution perspective.

-
Extended Enterprise Architecture Framework / E2AF & Extended Enterprise Architecture Maturity Model / E2AM are Service Marks (SM) registered by IFEAD