2006 Proceedings of the First International Conference on Software and Data Technologies   unpublished
Whether application integration is internal to the enterprise or takes the form of external Business-to-Business (B2B) automation, the main integration challenge is similar -how to ensure that the integration solution has the quality of adaptiveness (i.e. it is understandable, maintainable, and scalable)? This question is hard enough for stand-alone application developments, let alone integration developments in which the developers may have little control over participating applications. This
more » ... aper identifies main strategic (architectural), tactical (engineering), and operational (managerial) imperatives for building adaptiveness into solutions resulting from integration projects. IS-6 more aligned with (better suited for) loosely coupled integration. This is because data can be easily put aside for later use. Conversely, process integration is more aligned with tightly couple integration. Data replication, portal sharing, and messaging are the three integration solutions listed in Table 2 but missing in Table 1 . Data replication is classified as synchronous integration because replication servers of databases can be programmed to perform replications continuously and replicate data as the primary data is changing. Probably slightly controversially, portal sharing is classified in Table 2 as synchronous data integration. Portals are web sites or applications that provide access to a number of sources of information and facilities (portlets). They aggregate information from multiple sources into a single display. The display of information is synchronous but no any sophisticated process-level communication between portlets is normally assumed -hence, data integration. Messaging is the primary technology for asynchronous process integration (Hohpe and Woolf, 2003). Based on the Publish/Subscribe model, messaging frameworks guarantee reliable delivery of messages in program-to-program communication while recognizing that synchronous communication with remote applications is difficult to achieve (yet asynchronous communication is frequently acceptable). ASSURING ADAPTIVE INTEGRATION Building adaptiveness into enterprise and e-business systems engages all three traditional levels of management -strategic, tactical and operational. From the system's development perspective, the strategic level refers to the architectural solutions, the tactical level to the engineering decisions, and the operational level to the project controlling tasks. These three levels of management are used in the conventional top-down fashion when software is developed. We can say that system architecture defines adaptiveness, engineering activities deliver adaptiveness, and controlling tasks verify the existence of adaptiveness in an implemented system.
doi:10.5220/0001316401510158 fatcat:jm27ggpvlzatzh5t3envzikpbu