constraints

constraints - Architectural Integration Styles for...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Architectural Integration Styles for Large-scale Enterprise Software Systems Jonas Anderson, Pontus Johnson Dept. of Industrial Information and Control Systems, KTH, Royal Institute of Technology Osquldas vag 12, SE - 100 44 Stockholm, SWEDEN Gonasa, pontusj} @ics. kth.se Abstract A predominant problem in the management of large- scale enterprise software systems is application integration. Despite the considerable efforts spent on the development of new standards and technologies for software interoperation, the integration of systems that originally were not designed io interact with each other is a major undertaking, requiring in-depth knowledge existing systems, incorporation of integration products, and development and/or parameterization of various kinds of adapters and gateways. This article presents the concept of architectural integration styles, i.e. architectural styles describing software structures of integration solutions for enterprise systems. The article further proposes an approach for selection styles based on the characteristics of the existing software applications and the desired quality attributes of the integrated system. A number of architectural integration styles for enterprise systems are presented in the article, and a case study the style selection process applied to a mid-sized Swedish electricity retailer is described. 1. Introduction Integration of software systems has during the last decades become one of the most important, as well as resource consuming, activities in enterprise software system management. Enterprise software systems are typically composed of a mix of legacy, custom, and commercial-of-the-shelf software, and characterized by large-grained, heterogeneous and unmodifiable components, and heterogeneous connectors. As a result of the increasing focus on system integration, there is a growing market for software integration products and standards. The once fairly clear market division has recently been blurred by component technologies and standards like CORBA [20], COM [9], and Enterprise JavaBeans [ 171 incorporating more and more services. Typical integration solutions are exemplified by remote method invocation, message 0-7695-1345-X’01/$10.00 0 2001 IEEE queuing systems, transaction management message brokers, adapters, and database connectivity solutions [7] [16] [21] [22]. This article considers architectural styles [14] as a means for design of integration solutions for enterprise software systems. The article argues that architectural styles on the level of enterprise software systems can be used as generalizations of common integration solutions, much in the same way that styles and pattems are used in traditional software architecture and design. In other words, architectural integrations styles may be seen as generalizations of historically successful solutions to common problems. The perhaps most interesting part about architectural styles is that they are believed to impact software quality attributes. Certain styles are more
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 06/16/2009 for the course CSCI 578 taught by Professor Nenadmedidovic during the Spring '08 term at USC.

Page1 / 13

constraints - Architectural Integration Styles for...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online