Because of the development of the information technology, the enterprises of telecommunication introduce many applications system which have different independent function or some software developed by enterprises itself. After enterprises introduce these systems, they find information systems ongoing to expand have influenced the performance of systems and the operation time of users. Even influence the customer service satisfaction. Thus the enterprise continually to integrate system functions. At the same time, they find these independent systems have many problems, such as valuable data have been input several times to different system, data and object standard different between different systems. The technology of enterprise application integration¡]EAI¡^ provides enterprise a better solution to solve these problems. The purpose of this study is to address the issue of telecommunication system integration and using the EAI¡¦s methodology to analysis system. The analytics contains 3 modules, i.e. ¡§data¡¨, ¡§activity¡¨ and ¡§process¡¨ that handle functions of data transforming, message dispatching and process modeling among the heterogeneous systems. This study will use three modules of EAI to analyze the operation information system and study the main evaluation factors of EAI. This study could be submitted to the telecommunication industry for presetting construction when they consider to implementing the ¡§Enterprise Application Integration¡¨ system.

Atualmente a Integração de Aplicações Empresariais (EAI) desempenha um papel fundamental no cenário de integração de sistemas corporativos. Isso pode ser feito de diferentes formas, como por exemplo, por meio do compartilhamento de acesso às bases de dados ou trabalhando-se com Web Services, em que um serviço é disponibilizado por um sistema e pode ser chamado por outro sistema a ser integrado. Essas duas soluções estão sendo empregadas com sucesso, mas ambas apresentam vantagens e desvantagens que devem ser analisadas. Assim, este trabalho tem como objetivo primeiramente efetuar uma comparação entre essas duas abordagens de integração (tomando como base a norma ISO-IEC 9126-1) por meio de uma revisão bibliográfica complementada por uma revisão sistemática e relatos da experiência profissional da autora deste trabalho e da sua orientadora. Com o intuito de validar esta comparação, foi feito um estudo experimental, cujo objetivo do experimento foi avaliar a melhor abordagem para se realizar uma integração de aplicações empresariais: EAI-Dados e EAI-WS no que diz respeito ao esforço necessário para a implantação de cada uma. Assim, a avaliação foi realizada para responder à seguinte questão: Em termos de tempo de desenvolvimento e código produzido, é mais fácil realizar EAI-WS ou EAI-Dados? Finalmente, foram propostos cinco padrões para EAI, com o objetivo de auxiliar desenvolvedores com problemas similares de integração de aplicações. Esses padrões podem ser reusados em diversos contextos de integração, obedecendo às regras de negócios específicas a serem consideradas no momento da integração, e agilizando a modelagem da solução por meio da instanciação do padrão mais adequado a cada situação / Nowadays, Enterprise Applications Integration (EAI) performs a fundamental function in the scenery of enterprise systems integration. This can be done in different forms, for example by sharing the database access or working with Web Services, in which a service is provided by the system and can be called by other systems to be integrated. Those two solutions are being applied successfully, even though both present advantages and disadvantages that must be analyzed. Thus, the goal of this work is first to compare those two integration approaches, (Based on the standard ISO-IEC 9126-1) through a bibliographical review complemented by a systematic review and professional reports from the author of this work and her supervisor. In order to confirm this comparison, an experimental study was done, which resulted in quantitative answers about the best approach to perform systems integration: EAI-Data and EAI-WS which refer to effort required to deploy each. Thus, the assessment was conducted to answer the following question: In terms of development time and code produced, is easier to perform EAI-WS or EAI-Data? Finally, five patterns were proposed to EAI, which aim to support developers with similar problems of applications integration. These patterns can be reused in many integration contexts, following the rules of specific business to be considered in the moment of integration, and accelerating the modeling of the solution through the instantiation of the most adequate pattern to each situation

<p>Background: Information technology (IT) has drastically changed the traditional way to do business. In theory,</p><p>coordinating information sharing among organisational partners offers notable advantages through cost savings,</p><p>productivity, improved decision making, and better customer service. Supported by modern information technology,</p><p>business processes can change and be developed into new more effective forms, both internally and externally.</p><p>However, as IT facilitates new business opportunities, it requires a steady flow of information and information</p><p>exchange, both within intra- and inter-organisational contexts where a consensus on terms and definitions</p><p>coordinating the uniform communication is vital.</p><p>Purpose: With the focal point on inter-organisational information exchange, the purpose of the thesis is to define</p><p>a set of guidelines for AI that can be used and adjusted according to the needs of a specific situation or context.</p><p>Method: The thesis was carried out with a Multi Grounded Theory approach. Interviews were conducted at a local</p><p>IT-company and with an associate professor of Informatics at Jönköping International Business School.</p><p>Results: Five categories were discovered which impact AI: integration governance, project management, context, integration</p><p>content, and testing. The result also implied the importance to distinguish between an operational and strategic level</p><p>when working with Application Integration.</p>

Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2006. / A thesis submitted in total fulfillment of the requirments of for the degree of Doctor of Philosophy, Faculty of Information and Communication Technologies, Swinburne University of Technology, 2006. Typescript. Bibliography p. 194-201.

Thesis (Ph. D.)--Computing, Georgia Institute of Technology, 2007. / Calton Pu, Committee Chair ; Ling Liu, Committee Member ; Karsten Schwan, Committee Member ; Olin Shivers, Committee Member ; Donald F. Ferguson, Committee Member.

This thesis was requested by Solution Xperts in Linköping and is an evaluation of the software BizTalk360, which is a add-on to the very well known application integration software BizTalk Server. One problem that many face with BizTalk Server is how to handle the post-implementation operations of their implementation. Referring to such factors as monitoring and security for instance. The built-in tools are very limited and lack a variety of functions that are very desirable. BizTalk360 tries to solve this. In order to evaluate the value that BizTalk360 brings to its users, two factors were taken into account. How important are the functions provided for the company? And how difficult would these be to implement independently?. After testing the BizTalk360 core functions and features and also implementing a representative function of BizTalk360, everything learnt were presented to group of experienced BizTalk Sever developers in order to receive estimates regarding their individual importance and theoretical implementation time. The importance of the functions proved quite minor. The platform offers a lot of smart solutions to various problems but these wont see enough use to justify the cost. The difficulty of implementing a similar platform were also estimated to be quite low, only time consuming. Estimated to take (through average) 653 man hours.

M.Com. (Business Management) / Data and the use thereof, is considered to be a source of competitive advantage for organisations. In order to achieve this it needs to be managed appropriately, and existing literature considers enterprise information management (EIM) to be the foundation for organisations to manage information successfully. (For the purposes of this dissertation, data and information will be treated as analogous concepts.) Key contributing factors to the success of EIM have been identified as ensuring data governance is in place, and that there is a focus on data quality. Within EIM, a key set of data that must be managed effectively is customer data. In many organisations – including the financial services organisation that is the focus of this study – customer data is held in disparate systems across the organisation. Creating a single view of how customers interact with an organisation is deemed of crucial importance for future organisational growth, and the initiatives that organisations undertake to create this view is referred to in the literature as customer data integration (CDI). In order for CDI to be successful, master data management (MDM) needs to be addressed; this will ensure that core data is managed consistently across the disparate systems. This study sought to determine how the concepts of EIM, CDI and MDM were being applied in the organisation under review, and how closely this application matched the recommendations of the literature. In addition, the study sought to uncover additional factors that had an impact on customer data integration, and information management in general, in the organisation. What was found is that in the organisation in question, how information management is being addressed is consistent with the literature in some areas – primarily the importance of a single view of customer and the supporting roles of information governance and data quality – but divergent in others, the key area being that there is no EIM strategy in the organisation that drives a consolidated approach to information management. Organisational culture was also highlighted by the literature as being a critical influencer on how information is managed, and this was supported by the findings. Additional factors that were found to have a significant influence on data management – which were not highlighted by the literature – included the importance of processes, and especially for CDI the critical role played by legislation, in particular the Financial Intelligence Centre Act (FICA). An additional crucial factor, again not highlighted by the literature, is the difficulty organisations have in placing an actual financial value on the use of information. Although intrinsically it is understood that information is valuable, the difficulty in ascribing an explicit value to it is a key inhibitor (in conjunction with organisational culture), to the organisation initiating data management projects at a strategic level, and instead having to address data management as a component of projects driven by individual business units.

Atualmente a Integração de Aplicações Empresariais (EAI) desempenha um papel fundamental no cenário de integração de sistemas corporativos. Isso pode ser feito de diferentes formas, como por exemplo, por meio do compartilhamento de acesso às bases de dados ou trabalhando-se com Web Services, em que um serviço é disponibilizado por um sistema e pode ser chamado por outro sistema a ser integrado. Essas duas soluções estão sendo empregadas com sucesso, mas ambas apresentam vantagens e desvantagens que devem ser analisadas. Assim, este trabalho tem como objetivo primeiramente efetuar uma comparação entre essas duas abordagens de integração (tomando como base a norma ISO-IEC 9126-1) por meio de uma revisão bibliográfica complementada por uma revisão sistemática e relatos da experiência profissional da autora deste trabalho e da sua orientadora. Com o intuito de validar esta comparação, foi feito um estudo experimental, cujo objetivo do experimento foi avaliar a melhor abordagem para se realizar uma integração de aplicações empresariais: EAI-Dados e EAI-WS no que diz respeito ao esforço necessário para a implantação de cada uma. Assim, a avaliação foi realizada para responder à seguinte questão: Em termos de tempo de desenvolvimento e código produzido, é mais fácil realizar EAI-WS ou EAI-Dados? Finalmente, foram propostos cinco padrões para EAI, com o objetivo de auxiliar desenvolvedores com problemas similares de integração de aplicações. Esses padrões podem ser reusados em diversos contextos de integração, obedecendo às regras de negócios específicas a serem consideradas no momento da integração, e agilizando a modelagem da solução por meio da instanciação do padrão mais adequado a cada situação / Nowadays, Enterprise Applications Integration (EAI) performs a fundamental function in the scenery of enterprise systems integration. This can be done in different forms, for example by sharing the database access or working with Web Services, in which a service is provided by the system and can be called by other systems to be integrated. Those two solutions are being applied successfully, even though both present advantages and disadvantages that must be analyzed. Thus, the goal of this work is first to compare those two integration approaches, (Based on the standard ISO-IEC 9126-1) through a bibliographical review complemented by a systematic review and professional reports from the author of this work and her supervisor. In order to confirm this comparison, an experimental study was done, which resulted in quantitative answers about the best approach to perform systems integration: EAI-Data and EAI-WS which refer to effort required to deploy each. Thus, the assessment was conducted to answer the following question: In terms of development time and code produced, is easier to perform EAI-WS or EAI-Data? Finally, five patterns were proposed to EAI, which aim to support developers with similar problems of applications integration. These patterns can be reused in many integration contexts, following the rules of specific business to be considered in the moment of integration, and accelerating the modeling of the solution through the instantiation of the most adequate pattern to each situation

Mjukvarutestningsgruppen på Scania använder en manuell och tidskrävande process för att återställa testfordon efter sina utförda arbeten. I den återställningsprocessen ingår ett antal olika applikationer för att kunna säkerställa att fordonet är i samma skick som det var innan testerna. För att förbättra arbetsflödet med minskad arbetsbelastning och att försäkra en säkrare process var de intresserade av att utveckla ett återställningsverktyg som kan göra detta uppdrag. Önskemålet var att skapa detta genom att återanvända så mycket av de redan tillgängliga komponenterna som möjligt. Då det fanns flera komponenter som uppfyllde funktionskraven för de flesta funktionaliteten krävdes det en undersökning för att avgöra vilka ska användas. Denna gjordes med hjälp av integrationsmodellen Enterprise Application Integration, där målet är att utveckla en slutprodukt av applikationerna som används inom en organisation för att förenkla bland annat underhåll, datahantering och utbildning av medarbetarna. En prototyp har tagits fram som implementerar tre existerande moduler på olika nivåer och som enligt målet med EAI själv är en enkel mjukvara som möjliggör att komponenterna tillsammans utför arbetet. / The software testing team at Scania use a manual and time consuming process to restore a test vehicle after working with it. Several different applications are used in this process to ensure the vehicle is in the same state as it was before their testing. To improve the workflow with a reduced workload and a more robust process, the test team was interested in the development of a restoration application. It was desired to develop the restoration application by reusing the components to the greatest possible extend. Since there were many components that fulfilled the needs of most functions, a pre-study of all the applications was done to decide which components can be re-used. This was study was based on the integration model, Enterprise Application Integration, which aims to create a single product combining the applications used in an organization to simplify processes such as maintenance, data management and employee training. A prototype was developed which implements three existing modules on different levels and, in line with the goals of EAI, is itself a simple application that enables the components to work in unision

Approved for public release, distribution is unlimited / A thorough examination of the Secure Application Integration Methodology (SAIM) for applicability in the Department of the Navy (DON) would provide useful information about a beneficial methodology. SAIM is analyzed, by accessing its step by step directions, for suitability in the integration of the Enterprise Resource Planning (ERP) projects implemented by the SYSTEMS COMMANDS (SYSCOMS). The Navy Enterprise Convergence Team (NECT) that leads the ERP integration effort could benefit from a sound Enterprise Application Integration methodology. Results do not support SAIM as the sole guiding EAI methodology however it could have some value to the NECT. SAIM has three primary benefits which NECT could employ: 1) It provides a complete walkthrough of the EAI process, 2) It emphasizes the importance of an Enterprise Architecture, and 3) It provides useful management checklists along with other important considerations. SAIM also has some significant shortcomings: 1) It does not support all the DON Chief Information Officer requirements, 2) It does not provide Change Management Guidance, 3) It does not take into account the uniqueness of the Navy's environment, and finally 4) SAIM relies on an Enterprise Architecture as its foundation which the Navy does not currently have. / Lieutenant Commander, United States Navy