Keywords: , , , , , , , , , ,

Greg Deller


This article compares current and future interface concepts and the dramatic cost implications of interfaces. With the increased importance of exchanging information between enterprise solutions, a coordinated interface architecture should be considered. An interface architecture for the extended enterprise requires a shared communication language, one that standards greatly facilitate. While traditional interface approaches, such as point-to-point and hub and spoke, have been widely deployed in the past, they are costly to maintain and do not provide loose-coupling and fast return-on-investment. Web services and the Enterprise Service Bus (ESB) are promising interface technologies that provide access to loosely-coupled services using commercial standards and existing infrastructure to support a service oriented architecture. Numerous cost drivers, such as the interface architecture and functional, technical, and organizational characteristics significantly impact the cost of an interface. An understanding of interface technology and cost drivers will ensure system architects are better equipped to design and deploy cost-effective interface architecture.


interface, application integration, enterprise solution, interoperability, cost estimate, architecture, topology

About the author

Greg Deller is an information management consultant with Capgemini Government Solutions. Mr. Deller is currently supporting the Army Enterprise Integration Oversight Office (AEIOO), which helps ensure the transformation of key business processes through the use of enterprise applications to enhance and optimize business results and customer satisfaction. Previously, Mr. Deller was a manager with KPMG’s Information Risk Management practice and has over eight years of systems-based consulting experience. Mr. Deller is pursuing a Masters in Information Systems at George Mason University.


Altarum (2003). “Economic and Business Case Analysis Approach.” Unpublished, Oct 2003.

Belliappa, G. (2003). “Base-lining Interface Architecture for an Existing System.” Unpublished, Capgemini Ernst & Young.

Bernard, S. (2004). An Introduction to Enterprise Architecture. AuthorHouse, IL

Derby, P. (2004). “Enterprise Architect, U.S. Army, Army Architecture Integration Cell (AAIC).” Interview on 11 Aug 2004.

Buede, D. (2000). The Engineering Design of Systems. Wiley Inter-Science, New York.

Data Mirror Corporation (2001). “Benefits of Transformational Data Integration.”

Defense Information Systems Agency (2004), “DoD e8usiness.”

Department of Defense (2003). “RICE Development Process and Procedures,”:

Department of Defense Appropriations Act of 2004. Public Law 108-87, Section 8084(b)(1). Jacobsen, C. “A Framework for Continuous Improvement in Enterprise Application Integration,” Capgemini, unpublished.

Joint Financial Management Improvement Program (2004). “Forum Highlights: Keys to Successfullntegration/lnteroperabilityof Business Management Systems.” Unpublished, 27 May 2004.

Myerson, J. (2002). Enterprise Systems Integration. New York: Auerbach Publications. Newman, M. (2004). “1904 Baltimore Fire Made Standards a Hot Issue.” NIST Tech Beat. 2.htm#Centennial.

Nyere, J. (2004). “Enterprise Architect, Office of the Under Secretary of Defense for Acquisition, Technology, & Logistics.” Interview on 26 Aug 2004.

Rumsfeld, D. (2001). Town Hall Meeting. 01_t809town.html.

Society of Cost Estimating and Analysis. Software Cost Estimating, Unit IV, Module 12. Unpublished class materials.

Wikipedia (2005). Retrieved on 11 Jan 2005 from

Wolfowitz, P. (2004) Deputy Secretary of Defense Memo; Information Technology Portfolio Management, 22 March 2004.,

Wright, L. (2004). Senior Manager, Capgemini. Interview on 14 Sept 2004.

von Bernewitz, C. (2004). Director, Army Enterprise Integration Oversight Office, Interview on 18 Aug 2004.

Journal of Enterprise Architecture

Leave a Comment