Hyperlink: Programming: Software: Integration
Meta-Reference on Information Technology

Integration - Enterprise Architecture

Frameworks for Information Systems Enterprise Architecture

• Architecture Framework Forum
  The Architecture Framework Forum is an information resource dedicated to the leading frameworks for specifying enterprise architectures, to include: DoDAF (Department of Defense Architecture Framework - USA), MODAF (Ministry of Defence Architecture Framework - UK), UPDM (Unified Profile for DoDAF and MODAF), TOGAF (The Open Group Architecture Framework), Zachman Framework.
• Enterprise architecture
  From Wikipedia, the free encyclopedia.
  Enterprise Architecture is the description of the current and/or future structure and behavior of an organization's processes, information systems, personnel and organizational sub-units, aligned with the organization's core goals and strategic direction. Although often associated strictly with information technology, it relates more broadly to the practice of business optimization in that it addresses business architecture, performance management, organizational structure and process architecture as well.
  See also Systems architecture.
• IEEE 1471
  From Wikipedia, the free encyclopedia.
  IEEE 1471 is the short name for a standard formally known as ANSI/IEEE 1471-2000, Recommended Practice for Architectural Description of Software-Intensive Systems. This standard was published in 2007 by ISO/IEC JTC1/SC7 as ISO/IEC 42010:2007.

The Open Group Architecture Framework (TOGAF)

• The Open Group Architecture Framework (TOGAF)
  From Wikipedia, the free encyclopedia.
  TOGAF is a framework for Enterprise Architecture which provides a comprehensive approach to the design, planning, implementation, and governance of an enterprise information architecture. The architecture is typically modeled at four levels or domains: Business, Application, Information/Data, Technology. A set of foundation architectures are provided to enable the architecture team to envision the current and future state of the architecture.
• Introducing The Open Group Architecture Framework (TOGAF)
  Part 1: Understand TOGAF and IT architecture in today's world.
  Connecting business needs with the technology infrastructure. By Nicholas Chase, 14 Feb 2006, IBM developerWorks.
  Part 2: Explore an industry standard for defining an enterprise architecture, por Nicholas Chase, 28 Mar 2006.
  Part 3: Create an enterprise architecture with TOGAF, por Jeff Egan, 05 Sep 2006.
• TOGAF (tm), The Open Group Architectural Framework
  Version 8.1.1.
• TOGAF Version 8 "Enterprise Edition"
  By The Open Group.
  Welcome to TOGAF - The Open Group Architecture Framework.

Zachman Framework

• Zachman framework
  From Wikipedia, the free encyclopedia.
  The Zachman Framework is a framework for enterprise architecture which provides a formal and highly structured way of defining an enterprise. It uses a two dimensional classification model based around the 6 basic communication interrogatives (What, How, Where, Who, When, and Why) intersecting 6 distinct model types which relate to stakeholder groups (Visionary, Owner, Designer, Builder, Implementer and Worker) to give an holistic view of the enterprise which is being modeled.
• A framework for information systems architecture (PDF)
  By J. A. Zachman, IBM Systems Journal, vol. 26, no. 3, 1987. Article summary.
  Extending and formalizing framework for information systems architecture, by J.F. Sowa and J. A. Zachman, IBM Systems Journal, vol. 31, no. 3, 1992.
• Zachman Institute for Framework Advancement (ZIFA)
  ZIFA is a network of information professionals who understand the critical role of Enterprise Architecture in the ability of the enterprise to successfully participate in the global economy of the 21st century. To this end, the mission of ZIFA is to promote the exchange of knowledge and experience in the use, implementation, and advancement of the Zachman Framework for Enterprise Architecture.
  Framework Overview (PDF version of the Zachman Framework), Framework in 3D.
  Zachman International.
• Zachman Framework Applied to Administrative Computing Services
• The Zachman Framework: An Introduction
  By David C. Hay, June 1, 1997, The Data Administartion Newsletter (TDAN).
  What's Wrong With The Zachman Framework?, by Graeme Simsion, 01 Jan 2005.
• The Zachman Framework
  By David C. Hay, 2000, Essential Strategies, Inc.
• A Tutorial on the Zachman Enterprise Architecture Framework (PowerPoint)
  By USA.Gov Department of Veterans Affairs (VA), Office of Information and Technology, 2007-11-21.
  The Zachman Framework.
• UML, RUP, and the Zachman Framework: Better together
  By Vitalie Temnenco, Architect, Uniserve Communications Corporation, 15 Nov 2006, IBM developerWorks.

DoDAF, MODAF, UPDM

• UPDM
  From Wikipedia, the free encyclopedia.
  The UML Profile for DoDAF/MODAF (UPDM) provides an industry standard UML representation for DoDAF and MODAF compliant enterprise architectures, through the OMG standardization process based on a model-driven architecture (MDA) approach to specification.
• UML Profile for DODAF/MODAF (UPDM)
  Catalog of UML Profile Specifications, Unified Modeling Language (UML), Object Management Group (OMG).
  UML Profile for the Department of Defense Architecture Framework (DoDAF) and the Ministry of Defence Architecture Framework (MODAF) (PDF), OMG Document c4i/2007-02-01.
• UML Profile for the DoD and MoD Architecture Frameworks (UPDM) (PDF)
  By Ron Williamson, Ph.D. Raytheon, 2007-01-31. Enterprise Architecture Modeling and Tools, OpenGroup Architecture Practitioners Conference, San Diego, CA35.
• Department of Defense Architecture Framework (DoDAF)
  From Wikipedia, the free encyclopedia.
  The Department of Defense Architecture Framework (DoDAF) defines a standard way to organize an enterprise architecture (EA) or systems architecture into complementary and consistent views. All major U.S. Government Department of Defense (DoD) weapons and information technology system procurements are required to develop and document an EA using the views prescribed in the DoDAF. While it is clearly aimed at military systems, DoDAF has broad applicability across the private, public and voluntary sectors around the world. It is especially suited to large systems with complex integration and interoperability challenges, and is apparently unique in its use of "operational views" detailing the external customer's operating domain in which the developing system will operate (reference: Zachman framework).
• U.S. Department of Defense (DoD) CIO - Enterprise Architecture
  DoD Architecture Framework, Version 1.5, 23 April 2007 (PDF): Volume I: Definitions and Guidelines.
  Volume II: Product Descriptions.
  Volume III: Architecture Data Description.
  Alternative links, from jitc.fhu.disa.mil: Volume I, Volume II.
  DoD Architecture Framework.
• UK Ministry of Defence Architectural Framework (MODAF)
  From Wikipedia, the free encyclopedia.
  The UK Ministry of Defence Architectural Framework (MODAF) defines a standardised way of conducting Enterprise Architecture and provides a means to model, understand, analyze and specify Capabilities, Systems, Systems of Systems, and Business Processes. The purpose of MODAF is to provide a rigorous systems of systems definition when procuring and integrating defence systems. As of 10th April 2007, MODAF version 1.1 was released.
• MoD Architecture Framework (MODAF), UK
  MODAF is the UK Ministry of Defence (MoD) chosen implementation of an Enterprise Architecture Framework.
  The MODAF Meta-Model (M3) specifies a profile of UML 2.1 for MODAF.

Service Oriented Architecture (SOA) & Enterprise Application Integration (EAI)

• Service-oriented architecture (SOA)
  From Wikipedia, the free encyclopedia.
• Open SOA Collaboration
  The Open Service Oriented Architecture Collaboration represents an informal group of industry leaders that share a common interest: defining a language-neutral programming model that meets the needs of enterprise developers who are developing software that exploits Service Oriented Architecture characteristics and benefits. The Collaboration is not a Standards Body. Their resulting specifications are made available to the community on a Royalty Free basis for the creation of compatible implementations. When mature, the intent is to hand these specifications over to a suitable Standards Body for future shepherding.
  The Industry Partners are currently working on two main projects:
  • Service Component Architecture (SCA) - SCA Version 1.0 specifications, published by Open SOA in March 2007.
  • Service Data Objects (SDO) for Java, C++, COBOL, C.
  • OASIS Open Composite Services Architecture (CSA) Member Section is working on formal standardization of SCA and SDO.
• The Service Oriented Architecture (SOA) Blog
  By Eric Roch, ITtoolbox Blogs.
• Service Oriented Architecture
  MSDN Special Coverage.
• SOA Best Practices: A Conversation With Sun Microsystems Distinguished Engineer Mark Hapner
  By Janice J. Heiss. January 2006, Sun Developer Network (SDN).
• Tutorial on Service Oriented Architecture
  (Semantic) Web Services, Business Process Modeling, Software Engineering. By Dr. Yuhong Yan, Dr. Harold Boley, Dr. Bruce Spencer. Institute for Information Technology (IIT) of the National Research Council's (NRC). University of New Brunswick.
• Enterprise application integration (EAI)
  From Wikipedia, the free encyclopedia.
• SOA Enterprise Patterns
  Services, Orchestration, and Beyond. By Dragos Manolescu, Boris Lublinsky.
  micro-workflow.com, by Dr. Dragos Manolescu.
• Thomas Erl, SOA Systems - SOA & Web Services
  
  • What Is SOA? - An Introduction to Service-Oriented Computing
  • SOA Principles - An Introduction to the Service-Oriented Paradigm
  • SOA Glossary - Definitions for Service-Oriented Computing Terms
  • WS-Standards with Thomas Erl
  • SOA Specifications: Second-Generation (WS-*) Web Services, First-Generation Web Services, Core XML Platform
  • Thomas Erl's XML Enterprise
  • The SOA Magazine
  • SOA Books - The Prentice Hall Service-Oriented Computing Series from Thomas Erl
• IBM developerWorks - SOA and Web services
  Learning resources: New to SOA and Web services.
• Web Services and Service-Oriented Architectures
  On-line articles on SOA, Related books, Related reports.
• Service-Oriented Architecture (SOA) and Web Services: The Road to Enterprise Application Integration (EAI)
  Article by Qusay H. Mahmoud, April 2005. Sun Developer Network (SDN).
  Service-Oriented Architecture and Web Services: Concepts, Technologies, and Tools, by Ed Ort, April 2005.
  Implementing Service-Oriented Architectures (SOA) with the Java EE 5 SDK, by Gopalan Suresh Raj, Binod P.G., Keith Babo, and Rick Palkovic; May 2006. SOA3: Full Article PDF.
• SOA and Web Services
  SOA and Web Services Tutorials in this site helps you learn more about service-oriented architecture (SOA) and web services. By RoseIndia.
• Migration of Legacy Assets to SOA Environments (PDF)
  Grace Lewis, Ed Morris, Soumya Simanta, Dennis Smith, Lutz Wrage. Software Engineering Institute, Carnegie Mellon University.
• Introduction to Web services architecture
  Paper by K. Gottschalk, S. Graham, H. Kreger, and J. Snell. IBM Systems Journal, November 2001.
• An Introduction to the Web Services Architecture and Its Specifications
  By Luis Felipe Cabrera, Christopher Kurt, Don Box. MSDN Web Services Technical Articles, Version 2.0, Microsoft, October 2004.
• See also: Web Services (WS), WSDL, SOAP, UDDI

Enterprise Service Bus (ESB)

• Enterprise service bus
  From Wikipedia, the free encyclopedia.
• Open-Source ESBs - Presentations
  By Tijs Rademakers, Jos Dirksen, and others.
  Open Source ESBs, by Tijs Rademakers and Jos Dirksen, 10-14 December 2007, JavaPolis '07, Belgium; Presentation slides (PDF) from JavaPolis, from authors site.
  Enterprise Integration Patterns in Action (PDF), by Jos Dirksen, J-Spring 2007, Netherlands; Presentation slides from author site.
• Best of open source in platforms and middleware (page 2)
  2007 InfoWorld Bossie Awards picks among operating systems, app servers, Web servers, databases, service buses, and virtualization platforms. By Andrew Binstock, James R. Borck, Paul Venezia, 2007-09-10, InfoWorld.
  Bossie 2007 winners - Enterprise service bus: Mule ESB.
• Apache ServiceMix (open source)
  Apache ServiceMix is an Open Source ESB (Enterprise Service Bus) that combines the functionality of a Service Oriented Architecture (SOA) and an Event Driven Architecture (EDA) to create an agile, enterprise ESB. Apache ServiceMix is an open source distributed ESB built from the ground up on the Java Business Integration (JBI) specification JSR 208, released under the Apache license.
  IONA FUSE: open source solutions for SOA, ESB and enterprise messaging based on Apache projects (ServiceMix, ActiveMQ, CXF, Camel), fully tested, certified and supported by IONA.
• Mule Open Source ESB (open source)
  Mule is an open source ESB (Enterprise Service Bus) and integration platform. It is a scalable, highly distributable object broker that can seamlessly handle interactions with services and applications using disparate transport and messaging technologies.
• Service Oriented Java Business Integration
  Integration services are at the heart of any Service Oriented Architecture. Java integration efforts are focused at standardizing the core architectural elements of an integration architecture. By Sun Developer Network (SDN).
• JSR 208: Java Business Integration (JBI)
  JBI extends Java EE and Java SE with business integration SPIs.
• Java Business Integration
  From Wikipedia, the free encyclopedia.
• Open ESB (open source)
  Project Open ESB implements an Enterprise Service Bus (ESB) runtime using Java Business Integration (JBI) as the foundation. This allows easy integration of web services to create loosely coupled enterprise class composite applications.
• JBoss ESB (open source)
  JBoss ESB comes from Rosetta ESB, acquired by JBoss on 13th of June 2006, a mature ESB developed using JBoss Enterprise Middleware Suite (JEMS) technologies which has been proven in enterprise use as the backbone of the second-largest insurance provider in Canada, handling data from 3,000 employees, 40 locations and two million customers for nearly three years.
  Red Hat supports the JBI effort, but JBoss ESB does not support JBI 1.0 at this time. JBoss is working on the JBI 2.0 expert group as it may be their target.
• ObjectWeb PEtALS (open source)
  PEtALS provides a leading open source ESB to support your Service Oriented Infrastructure. PEtALS is a lightweight, highly distributed and scalable platform for both A2A and B2B integration.
• Apache Synapse (open source)
  Apache Synapse is a easy-to-use and lightweight XML and Web Services management and integration broker that can form the basis of a Service Oriented Architecture (SOA) and Enterprise Service Bus (ESB).
• Open Source EAI Written In Java
  List by Manageability Blog.
• TIBCO Enterprise Service Bus Software (commercial)
  TIBCO BusinessWorks and TIBCO ESB Solution.
• IBM WebSphere Enterprise Service Bus (commercial)
  IBM has put the ESB at the heart of its middleware strategy and offers two software ESBs and one hardware ESB appliance: WebSphere Enterprise Service Bus (WebSphere ESB): built on WebSphere Application Server for an integrated SOA platform; WebSphere Message Broker: built for universal connectivity and transformation in heterogeneous IT environments; WebSphere DataPower Integration Appliance XI50: purpose-built hardware ESB for simplified deployment and hardened security.
• Oracle Enterprise Service Bus (commercial)
  Oracle ESB is part of Oracle SOA Suite. Oracle Fusion Middleware includes key Enterprise Service Bus (ESB) infrastructure based on open standards to provide messaging, routing, and data transformation services between applications and IT systems. With these services, the ESB infrastructure simplifies implementation by linking different systems together across a common backbone. The result is a framework that is easy to deploy, and gives businesses increased flexibility, reusability and responsiveness.
• Microsoft BizTalk Server: Enterprise Service Bus (commercial)
  

Business Process Modeling (BPM)

Business Process Execution Language (BPEL) is a business process modeling language, designed to define business processes that interact with external entities, specially through Web Service operations. BPEL is an orchestration language. BPEL for Web Services (BPEL4WS) originated from combination of IBM's WSFL and Microsoft's XLANG. In April 2003, IBM, Microsoft, BEA Systems, SAP and Siebel Systems submitted BPEL4WS 1.1 to OASIS for standardization, which named it WS-BPEL 2.0 to align BPEL with other Web Service standard naming conventions starting with WS-.

There is no standard graphical notation for WS-BPEL. The Business Process Modeling Notation (BPMN) is a standardized graphical notation for drawing business processes in a workflow. Mosts BPEL constructions can be mapped to BPMN graphical representations. However, fundamental differences between BPMN and BPEL make it very difficult, and in some cases impossible, to generate human-readable BPEL code from BPMN models.

• Portal BPM [Em Português]
  Espaço dedicado à discussão de BPM, BPMS e SOA.
• BPM - Business Process Management - para Leigos [Em Português]
  Por Marco Aurélio Mendes, 29/01/2007.
• Business Process Management - BPM
  BPM Tutorial, BPM Vendor Directory. By Knowledge Hills.
• Business Modeling Forum
  Business Modeling Forum FAQ.
• ebPML.org
  ebPML is a site dedicated to the standards, technologies and products of Service Oriented Computing, Business Process Management and Model Driven Architectures. Process modeling languages (PML's): BPMN, WS - CDL, WS - BPEL, ebBP, BPEL-J, UML 2.0, BPML, XPDL, EDOC, deprecated ones.
• Business Process Execution Language (BPEL)
  From Wikipedia, the free encyclopedia.
  Process modeling. Business Process Modeling Notation (BPMN).
• Web Services Business Process Execution Language Version 2.0
  WS-BPEL 2.0, OASIS Standard, 11 April 2007.
  OASIS WSBPEL Technical Comitee (TC).
• Business Process Execution Language for Web Services 1.1
  BPEL4WS Specification and Resources. Contributors: IBM, BEA Systems, Microsoft, SAP AG, Siebel Systems. 30 Jul 2002, updated 08 Feb 2007. Business Process Execution Language for Web Services (BPEL4WS) provides a means to formally specify business processes and interaction protocols.
• BPEL and Java
  By Matjaz Juric, April 2005, TheServerSide.COM.
• Business Process Modeling Notation (BPMN) Information
  By Business Modeling & Integration Domain Task Force (DTF), joined forced of Object Management Group (OMG) and Business Process Management Initiative (BPMI).
• BPMN2BPEL: A tool for translating BPMN to BPEL
  BABEL Tools, Queensland University of Technology, Australia.
• The BRMS Blog
  All about Business Rules Management Systems, blog posts written by managers in YASU Technologies.
  YASU's QuickRules BRMS introduces Business Rules to NetBeans and JBI Community, by Subhash, on 2007-05-14.
• TIBCO Business Studio (freeware)
  IDE with graphical software tools for elements of business process management: modeling, management, simulation and implementation. Full support for BPMN 1.0 standard and XPDL. Based on Eclipse Platform. Requires JRE 1.4 or superior.