alternate text alternate text alternate text alternate text


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

Enterprise Architecture Standards Overview

IFEAD / TOGAF Open Standards

STREAM (Speedy, Traceable, Result driven, Enterprise, Architecture, Management) a Successful and Pragmatic 'Managed Diversity' Enterprise Architecture Approach

So how do you create a pragmatic managed diversity Enterprise Architecture program driven by the business?

Describing and selling an EA program to any organization is a challenge. Translating the “EA language” into your organization’s jargon will add credibility to your program. First, your organization’s knowledge workers will understand the program’s impact and value to their jobs. If they just shake their heads, but don’t understand the message, your credibility as a Lead Enterprise Architect can be lost immediately.

This instantly labels the Lead Enterprise Architect as the book smart academic that can’t apply EA into real world scenarios.

So you need another approach like the successful STREAM (Speedy, Traceable, Result-driven, Enterprise, Architecture, Management) approach developed by the Institute For Enterprise Architecture Developments in cooperation with Logica Business Consulting that has proven its value in real world scenarios.

The STREAM Approach

This STREAM approach is focused on balancing the need for a set of standards with the need for a diversity of solutions to increase innovation, business growth and competitive advantage and the need to deliver concrete added value in an agile way.
The characteristics of the STREAM approach are:
The Results must be Traceable … in order to add value: Start at the business side and make all choices and decisions traceable to the sources.
The Process must be Pragmatic ... in order to add value: Focus only on those elements that directly contribute to the goals & objectives. Make a difference between EA thinking and EA doing.
The trajectory must be Rapid ... in order to add value: Most STREAM EA transformation / rationalisation trajectories are delivering their results within a 4 to 5 months timeframe.
The Process must be Productive ... in order to add value: STREAM EA transformation / rationalisation trajectories are delivering predefined type of results, related to the goals & objectives.
The Results must be Relevant ... in order to add value: STREAM EA transformation / rationalisation / legacy trajectories are always starting at the business site and are delivering significant added value due to the focus to contribute to organisations strategic objectives & direction.

The STREAM phases are based on the characteristics of a managed diversity EA approach focused on balancing the need for a set of standards with the need for a diversity of solutions to increase innovation, business growth and competitive advantage in an agile way.

More Info:

Are you interested in the STREAM approach, then download the STREAM Paper or download the STREAM Presentation.


Enterprise Architecture Good Practice Guide First International Open Standard in EA

January 2009

The purpose of this First International adapted is to provide guidance to organization's in initiating, developing, using, and maintaining their enterprise architecture (EA) practice. This Open Standard guide offers a set of Enterprise Architecture Good Practices that have proven their benefits to organizations and that addresses an end-to-end process to initiate, implement, and sustain an EA program, and describes the necessary roles and associated responsibilities for a successful EA program.

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, organization 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.

While EA frameworks and models provide valuable guidance on the content of enterprise architectures, there is literally no guidance how to successfully manage the process of creating, changing, and using Enterprise Architecture.

This guidance is crucially important. Without it, it is highly unlikely that an organization can successfully produce a complete and enforceable EA for optimizing its business value and mission performance of its systems. For example, effective development of a complete EA needs a corporate commitment with senior management sponsorship. Enterprise Architecture development should be managed as a formal program by an Enterprise Architecture Department that is held accountable for success.

Since that EA facilitates change based upon the changing business environment of the organization, the enterprise architect is the organization’s primary change agent.

Effective implementation requires establishment of business and system compliance with the enterprise architecture, as well as continuous assessment and enforcement of compliance. Waiver of these requirements may occur only after careful, thorough, and documented business case analysis. Without these commitments, responsibilities, and tools, the risk is great that business changes or new systems will not meet organizations business needs, will be incompatible, will perform poorly, and will cost more to develop, integrate, and maintain than is warranted.

Using the methods, tools and approaches decribed in this Open Standard Guide are completly in line with initiatives of the Open Group and their TOGAF Framework and ArchiMate modelling language. Both the use of TOGAF and ArchiMate are part of the content of this book plus much more.......!

For ordering the book directly at the Publisher, go to:

CEN / ISO Standards

Enterprise Architecture, Engineering & Integration Standards

Below you find - in structured lists - the titles of selected documents relevant to the subject of Enterprise Architecture, Engineering and Integration. Each title is connected to a short versions of the document, from where you can further navigate to the complete document or the document source.


  • preEN/ISO 19439 :  Enterprise Integration - Framework for Enterprise Modelling,  ISO TC 184/SC5/WG1 - CEN TC 310/WG1, 2003
  • preEN/ISO 19440:   Enterprise Integration - Constructs for Enterprise Modelling,  ISO TC 184/SC5/WG1 - CEN TC 310/WG1, 2003
  • ISA 95.00.01: Enterprise-Control System Integration , IEC/ISO JWG15, 2002
  • ENV 13550 : Advanced Manufacturing Technology - Systems Architecture - Enterprise Model Execution and Integration Services, , CEN/TC310, 1999
  • IS 15704: Requirements for Enterprise Reference Architecture and Methodologies, ISO TC 184/SC5/WG1, 1998
  • IS 14258 : Industrial Automation Systems - Concepts and Rules for Enterprise Models, ISO TC 184/SC5/WG1, 1998
  • ENV 12204 : Advanced Manufacturing Technology - Systems Architecture - Constructs for Enterprise Modelling,  CEN TC 310/WG1, 1996
  • ENV 40003 : Computer Integrated Manufacturing - Systems Architecture - Framework for Enterprise Modelling,  CEN/CENELEC, 1991
Joint IEC/ISO Working Group CEN / ISO Reports

IEEE 1471 has been adopted by ISO as ISO/IEC 42010:2007

June 2007

IEEE 1471 has been adopted by ISO as ISO/IEC 42010:2007, Systems and software engineering -- Recommended practice for architectural description of software-intensive systems.

IEEE and ISO have begun joint revision of the standard which will become Systems and software engineering -- Architectural description. The revision will be undertaken by ISO/IEC JTC 1/SC 7 Working Group 42*
* "42" because it is said that, "Architecture is the answer to life, the universe, and everything." :-)

The joint revision has several goals:
  • to widen the scope of application from software-intensive systems to general systems architecture (including enterprise architecture);
  • to harmonize with the ISO systems engineering (ISO 15288) and software engineering (ISO 12207) life cycle processes; and
  • to align terms and concepts with other ISO architecture efforts, including RM-ODP (ISO 10746) and GERAM (ISO 15704).

Interested parties may participate in the revision either through their ISO member bodies, or through IEEE.

For more information, see IEEE 1471 | ISO 42010 web site:

preEN/ISO 19439: 2003

Enterprise Integration – Framework for Enterprise Modeling

The standards have been prepared jointly by CEN TC310 WG1 and ISO TC 184 SC5 WG1. During its preparation, contributions have been received from members of the IFAC/IFIP Task Force on Enterprise Integration.

This framework defines the generic concepts that are required to enable the creation of enterprise models for industrial businesses (industrial enterprises) either one.

This modeling framework fulfils the requirements stated in ISO IS 15704, which have been derived from the framework of the Generalised Enterprise Reference Architecture (GERAM) proposed by the IFAC/IFIP Task Force. The standard defines a three-dimensional structure with seven life cycle phases, three levels of genericity and a minimum set of four model views

The dimensions are: model phase, model view, genericity

  • Enterprise models have a life cycle that is related to the life cycle of the entity being modeled. The enterprise model phases are: Domain Identification, Concept Definition, Requirements Definition, Design Specification, Implementation Description, Domain Operation, Decommission Definition.
  • The enterprise model view dimension enables the enterprise modeler and enterprise model user to filter their observations of the real world by particular views. The predefined views are: Function View, Information View, Resource View, Organization View/Decision View.
  • The Genericity dimension provides for the progression from general concepts to particular models . The standard defines three levels of genericity: Generic Level, Partial Level, Particular Level.

Normative references are:

ISO 14258:1998, Concepts and Rules for Enterprise Models.
ISO 15704:2000, Requirements for Enterprise Reference Architecture and Methodologies

ISO Reference Model for Open Distributed Processing

[ISO RM-ODP] (pdf 97KB)

The Reference Model of Open Distributed Processing (pdf 30Kb), ITU-T Rec. X.901 | ISO/IEC 10746-1 to ITU-T Rec. X.904 | ISO/IEC 10746-4, commonly referred to as RM-ODP, provides a framework to support the development of standards that will support distributed processing in heterogeneous environments. It is based, as far as possible, on the use of formal description techniques for specification of the architecture.

RM-ODP uses an object modelling approach to describe distributed systems. Two structuring approaches are used to simplify the problems of design in large complex systems: five 'viewpoints' provide different ways of describing the system; and eight 'transparencies' identify specific problems unique to distributed systems which distributed system standards may wish to address. Each viewpoint is associated with a language which can be used to describe systems from that viewpoint.

The five viewpoints described by RM-ODP are:

1. The enterprise viewpoint, which examines the system and its environment in the context of the business requirements on the system, its purpose, scope and policies. It deals with aspects of the enterprise such as its organizational structure, which affect the system.

2. The information viewpoint, which focuses on the information in the system. How the information is structured, how it changes, information flows, and the logical divisions between independent functions within the system are all dealt with in the information viewpoint.

3. The computational viewpoint, which focuses on functional decomposition of the system into objects which interact at interfaces.

4. The engineering viewpoint, which focuses on how distributed interaction between system objects is supported.

5. The technology viewpoint, which concentrates on the individual hardware and software components which make up the system.

ISO/IEC 14252 (IEEE Std 1003.0)

Overview ISO/IEC Technical Report (TR) 14252:1996, Guide to the POSIX Open System Environment, is a direct line ancestor of TOGAF.

Describes POSIX Open System Environment (POSIX OSE). It is intended to be used by anyone interested in using standards to construct an information processing system, including consumers, system integrators, application developers, system providers, and procurement agencies.

IEEE Standards

IEEE 1471-2000 Standard for Architectural Description

IEEE Std 1471-2000 is IEEE's Recommended Practice for Architectural Description of Software-Intensive Systems description (AD) to conform to the Standard.

Download Presentation IEEE 1471(pdf 1766Kb)

Download Document IEEE 1471 Beyond (pdf 134Kb)

IEEE Std 1471-2000 and the impact on The Open Group Architecture Framework (TOGAF)

Download Document IEEE 1471-Togaf impact (pdf 55Kb)

Website SESC

NIST / Open Group / Other Standards

Enterprise Architecture and Standards

Enterprise Architecture and Standards are developed under the sponsorship of the USA Commonwealth of Kentucky Information Resources Management Commission. Enterprise Architecture Standards pages are maintained by GOT's Office of Policy and Customer Relations, Division of Planning and Architecture.

USA-National Institute of Standards and Technology

USA-NIST plays a variety of roles in support of voluntary standardization efforts that respond to market and industry needs. We provide technical expertise and facilitate private sector agreement. In addition, NIST supports trade agreements by helping to build the underlying conformity-assessment infrastructure necessary to harmonize standards and regulatory requirements across borders. We also coordinate federal agencies' use of voluntary standards.

  • Measurement standards—provide measurement traceability, at necessary levels of accuracy, to national standards
  • Documentary standards—specify characteristics of products, processes, services, or systems.See standards information, (which includes Export Alert! an e-mail notification service), standards coordination and participation in standards activities, and training
  • Conformity assessment/accreditation—procedures for demonstrating compliance with standards and regulations, including NIST guides to EU directives
  • Information technology standards

Architecture Description Markup Language (ADML)

The Architecture Description Markup Language (ADML) is an XML-based representation language for architecture. It was originally developed by the Micro-electronics and Computer technology Consortium (MCC) as part of MCC's Software and Systems Engineering Productivity (SSEP) project.

The Business Process Modeling Language (BPML) is a meta-language for the modeling of business processes, just as XML is a meta-language for the modeling of business data. BPML provides an abstracted execution model for collaborative & transactional business processes based on the concept of a transactional finite-state machine. More on BPML...

Download the BPML 1.0 Specification (335Kb)

The Business Process Modeling Notation (BPMN) specification provides a graphical notation for expressing business processes in a Business Process Diagram (BPD). The BPMN specification also provides a binding between the notation's graphical elements and the constructs of block-structured process execution languages, including BPML and BPEL4WS. The first draft of BPMN was made available to the public on November 13, 2002.

Download the BPMN 1.0 Draft Specification (1260Kb)

The Business Process Query Language (BPQL) defines a standard interface to forthcoming Business Process Management Systems (BPMS). It allows system administrators to manage the BPMS and business analysts to query the instances of business processes it executes. The Business Process Query Language (BPQL) is a management interface to a business process management infrastructure that includes a process execution facility (Process Server) and a process deployment facility (Process Repository).

The BPQL interface to a Process Server enables business analysts to query the state and control the execution of process instances managed by the Process Server. This interface is based on the Simple Object Access Protocol (SOAP).

The BPQL interface to a Process Repository enables business analysts to manage the deployment of process models managed by the Process Repository. This interface is based on the Distributed Authoring and Versioning Protocol (WebDAV).

Process models managed by the Process Repository through the BPQL interface can be exposed as UDDI services for process registration, advertising, and discovery purposes.

IDEF0, 1x & 3 GAO Standards

Modeling Methods


IDEF0, published 1993 by the National Institute of Standards and Technology (NIST), is the
USA General Accounting Office (GAO) standard for graphically depicting processes and functions.

The primary strength of IDEF0 is that the method has proven effective in detailing activities for
function modeling, the original structured analysis communication goal for IDEF0. IDEF0 will
be used to model the As Is Trust Business processes. Activities for the processes will be
described by their inputs, outputs, controls, and mechanisms (ICOMs). Additionally, the
description of the activities of a system can be refined into the descriptive detail required for the
decision-making task at hand.

Download Document IDEF0 (237Kb)


IDEF1X is a method for designing relational databases with a syntax designed to support the semantic constructs necessary in developing a conceptual schema. A conceptual schema is a single integrated definition of the enterprise data that is unbiased toward any single application and independent of its access and physical storage. Because it is a design method, IDEF1X is not particularly suited to serve as an AS-IS analysis tool.

Download Document IDEF1x (426Kb)

Also published by the NIST, IDEF3 captures precedence and causality relations between situations
and events 2 . While IDEF3 can be used to capture detailed characteristics of information systems that
support business processes, IDEF3 will be used by the As Is Trust Business project to capture the
precedence and causality relations between processes.

Download Document IDEF3 (1885Kb)

Information Technology Enterprise Standards

The premise of adopting standards is to enable innovation of technology within an environment that is well understood and defined. The enterprise standards support the technology vision and principles of the Strategic Information Technology Plan and the direction in the Commonwealth Information Technology Enterprise Architecture. Most importantly, the standards promote migration to enterprise solutions with reduced complexity and support. The establishment and governance of enterprise standards requires a constant balancing between too much control and not enough control. Standards are both beneficial and detrimental, depending on the perspective of the user. The standards must provide the right amount of flexibility so that the state's business is not constrained.

Information Technology Enterprise Standards (pdf 367Kb)

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