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

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.

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

No description available.

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

Enterprise Application Integration (EAI) handlar om att koppla samman system för att tillfredsställa behov som inte kunnat tillfredsställas av systemen var och en för sig, eller upprätta nya kommunikationskanaler inom eller mellan företag. Allteftersom system och deras underliggande teknologier blivit mer avancerade har uppgiften att integrera dem blivit mer komplicerad. Genom att göra en fallstudie i samband med ett integrationsprojekt på ett företag syftar denna uppsats till att identifiera fallgropar som kan innebära risker för sådana projekt. En målsättning är att analyser kring dessa fallgropar ska kunna användas för att hjälpa utvecklare undvika dessa i sina projekt. Under fallstudien identifierades flera fallgropar genom analys av dokumentation och reflektion. Den fallgrop som hade störst påverkan under projektet var otydliga krav. Fallgroparna analyseras utifrån hur de upptäcktes och resonemang förs kring bidragande faktorer. För de fallgropar som utgjorde faktiska utmaningar under fallstudien analyseras även hur de undveks, medan potentiella lösningar diskuteras för resterande. / Enterprise Application Integration (EAI) concerns connecting systems together to meet demands that could not be met by either system individually, or to establish new channels for communication within and between enterprises. As the systems and their underlying technologies have become more advanced, the task of integrating them has become a more complicated one. By making a case study bound to an integration project at an enterprise, this study aims to identify pitfalls that could constitute risks for such projects. The main goal is for the analysis of these pitfalls to guide developers to avoid the pitfalls in their own projects. Several pitfalls were identified by analyzing documentation and reflecting on the course of the project. The pitfall that had the greatest impact during the project was unclear requirements. The pitfalls are analyzed with emphasis on circumstances under which they were discovered and contributing factors are reasoned about. For the pitfalls that were actual challenges for the case study, analysis also covers how they were avoided, while potential solutions are discussed for the remainder.

Community-based open source (community source) has emerged as a new approach of developing enterprise software systems that requires participation and investments from partner institutions. This new approach provides the opportunity for institutions to pool resources together to achieve objectives that are hard to reach individually. In my dissertation, community-based development of enterprise applications is examined in a real world project called Kuali through the following three perspectives: technology perspective, economic perspective and management perspective. Under the technology perspective, the main research question is "how do service-oriented architectures enable technology flexibility in community source?" The Kuali case provides the initial context for understanding the basic concepts and insights surrounding the technological issues in community source. Under the economic perspective, the main research question is "why are institutions interested in investing in community source?" The case study and analytical modeling are used to better understand the decision-making process in community source. Under the management perspective, two main research questions are studied. The first research question is "what are the factors affecting the project success in community source development?" The case study, the surveys and the interviews are conducted to test the community source project success model. The second research question is "what are the motivations for outsourcing software development in community source?" Based on the results of our interview analysis, we propose a research framework for community source outsourcing. In the long term, I would like to develop a generic framework for describing the process of acquiring application software via either commercial, open source, or home grown approach. My research will concentrate on comparing these three application development approaches with a special focus on community source. The main contribution of my dissertation is to provide guideline for strategic planning and decision making in an institution. The finding in this dissertation research will provide significant insights on the selection of various software development approaches that are useful for both researchers and practitioners.