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.

A Integração de Aplicativos Empresariais (EAI, Enterprise Application Integration) entre empresas de uma mesma cadeia produtiva é uma inovação organizacional que proporciona grandes ganhos em competitividade, o que chega a ser vital no atual ambiente de negócios. Essa integração necessita de recursos nem sempre disponíveis nesses sistemas de gestão. Este estudo fez um levantamento dos Sistemas Integrados de Gestão Empresarial (ERP, Enterprise Resource Planning) mais utilizados no Brasil, a respectiva participação no mercado brasileiro e identificou para cada um deles quais seus recursos existentes para integração com outros ERP de outras organizações da cadeia. Tem-se como resultado um panorama no qual se pode apoiar para tomada de decisão ou usá-lo como ponto de partida para pesquisa do nível de utilização do recurso de integração de sistemas entre empresas no Brasil e das barreiras à implementação da mesma. Trata-se de uma pesquisa exploratória que pela análise dos documentos disponibilizados pelos desenvolvedores dos softwares fez a identificação dos recursos de integração dos cinco sistemas ERP mais utilizados no Brasil. / Enterprise Application Integration (EAI) among companies of the same production chain is an organization innovation that provides meaningful gains in competitiveness, which may be critical in current business environment. This integration needs resources not always available in this management systems. This paper investigated Brazil most used ERP, their market share, and identified each ones existing resources to integrate with other ERP in other organizations in the chain. As a result, there is a full view on which to rely for decision making or to be taken as a start for an research on the system integration resource utilization level among Brazil companies and implementation barriers to it. It is a exploratory research, where by means of documentation made available by the softwares developers identified the integration resources of the five ERP systems most used in Brazil.

O desenvolvimento de trabalhos em grupo tornou-se uma tarefa cada vez mais comum nos dias atuais. Com isso, houve também um crescimento na utilização e no desenvolvimento de aplicações computacionais que implementam os processos de apoio à cooperação entre as pessoas, as quais possibilitam um considerável ganho de produtividade nas tarefas realizadas pelo grupo. A integração de várias dessas aplicações pode resultar em um acréscimo de funcionalidades, aumentando as possibilidades de uso e a flexibilidade para o usuário. Com o objetivo de agregar funcionalidades e melhorar os potenciais usos dos sistemas de software, aplicações integradas possuem, em geral, mais funcionalidades e maiores possibilidades de uso do que aplicações isoladas. Assim, foi desenvolvido o WS4CSCW (Web Services for Computer Supported Cooperative Work), um Web Service que tem como objetivo facilitar a integração de ferramentas e sistemas CSCW. O WS4CSCW permite o gerenciamento de usuários, grupos, recursos, permissões e papéis de usuários e grupos, disponibilizando funcionalidades para aplicações voltadas ao trabalho em grupo, bem como para facilitar a integração entre essas aplicações, permitindo um co-funcionamento mais direto, consistente e coeso. / Nowadays, the achievement of tasks made in groups has become a habitual concern by people. In this way, a rise of using and developing computer programs that support cooperative work process has been noted. The programs aim to provide productivity improvements on work made by groups. Integrating the software could result in increasing functionalities, augmenting both its use possibilities and flexibility. Integrated softwares have, in general, more features and use's potential than isolated applications. As a result, WS4CSCW (Web Services for Computer Supported Cooperative Work) -- a Web Service to assist CSCW application's integration was developed. WS4CSCW allows management of users, groups, resources, permissions, and user and group roles, by making available functionalities to applications for group work, making easy the integration among these applications and providing a straighter, more cohesive and consistent cooperation.

This thesis reports on a research project undertaken over a four year period investigating and developing a software framework and application for integrating and managing building product information for construction engineering. The research involved extensive literature research, observation of the industry practices and interviews with construction industry practitioners and systems implementers to determine how best to represent and present product information to support the construction process. Applicable product models for information representation were reviewed and evaluated to determine present suitability. The IFC product model was found to be the most applicable. Investigations of technologies supporting the product model led to the development of a software tool, the IFC Assembly Viewer, which aided further investigations into the suitability of the product model (in its current state) for the exchange and sharing of product information. A software framework, or reusable software design and application, called PROduct Information Management System (PROMIS), was developed based on a non-standard product model but with flexibility to work with the IFC product model when sufficiently mature. The software comprises three subsystems namely: ProductWeb, ModelManager.NET and Product/Project Service (or P2Service). The key features of this system were shared project databases, parametric product specification, integration of product information sources, and application interaction and integration through interface components. PROMIS was applied to and tested with a modular construction business for the management of product information and for integration of product and project information through the design and construction (production) process.

Made available in DSpace on 2015-03-05T13:59:42Z (GMT). No. of bitstreams: 0 Previous issue date: 10 / Nenhuma / A abordagem tradicional de construção de softwares baseia-se num modelo voltado para atender um conjunto de requisitos de negócios (normalmente um modelo de objetos ou componentes), porém, precisa estar preparado para atender necessidades de negócios que podem surgir no decorrer do processo. Assim, um modelo baseado em serviços pode representar uma nova forma de tecnologia para atender estas necessidades. No cenário brasileiro e internacional, o parque de sistemas de computação legado é muito expressivo. Estes sistemas se encontram em produção utilizando tecnologias muitas vezes já ultrapassadas que permitem uma pequena taxa de reuso. Portar estes sistemas para uma tecnologia baseada em serviços, visando obter reuso em grande escala, requer uma análise criteriosa do código existente e algumas customizações para disponibilizar serviços sem comprometer seu funcionamento. Este trabalho propõe e implementa uma arquitetura denominada Aruba que permite a geração de serviços a partir de sistemas legados e o acesso a / The traditional software development is based on a model focused in answering a set of business requirements (generally an object or component model), but it needs to be prepared to deliver solutions to business needs that may occur during the process. This way, a service based model may represent a new technology approach to meet these needs. At the Brazilian and international scenario there are many legacy systems. These systems are being currently in use and often are built on old technologies that do not allow much reuse. Porting these systems to a service based technology, aiming large scale reuse, needs analysis of the existing code and some customizations to make services available without compromising its functions. This work explains an architecture called Aruba that allows service generation from legacy systems with no need of legacy code change. This solution uses the Web Services technology, which allows service description and use through WSDL and SOAP (all XML based), and uses a database as re

A Integração de Aplicativos Empresariais (EAI, Enterprise Application Integration) entre empresas de uma mesma cadeia produtiva é uma inovação organizacional que proporciona grandes ganhos em competitividade, o que chega a ser vital no atual ambiente de negócios. Essa integração necessita de recursos nem sempre disponíveis nesses sistemas de gestão. Este estudo fez um levantamento dos Sistemas Integrados de Gestão Empresarial (ERP, Enterprise Resource Planning) mais utilizados no Brasil, a respectiva participação no mercado brasileiro e identificou para cada um deles quais seus recursos existentes para integração com outros ERP de outras organizações da cadeia. Tem-se como resultado um panorama no qual se pode apoiar para tomada de decisão ou usá-lo como ponto de partida para pesquisa do nível de utilização do recurso de integração de sistemas entre empresas no Brasil e das barreiras à implementação da mesma. Trata-se de uma pesquisa exploratória que pela análise dos documentos disponibilizados pelos desenvolvedores dos softwares fez a identificação dos recursos de integração dos cinco sistemas ERP mais utilizados no Brasil. / Enterprise Application Integration (EAI) among companies of the same production chain is an organization innovation that provides meaningful gains in competitiveness, which may be critical in current business environment. This integration needs resources not always available in this management systems. This paper investigated Brazil most used ERP, their market share, and identified each ones existing resources to integrate with other ERP in other organizations in the chain. As a result, there is a full view on which to rely for decision making or to be taken as a start for an research on the system integration resource utilization level among Brazil companies and implementation barriers to it. It is a exploratory research, where by means of documentation made available by the softwares developers identified the integration resources of the five ERP systems most used in Brazil.

A semantic model oriented transformation mechanism is developed for the centralization of intra-enterprise data integration. Such a mechanism is especially crucial in the banking domain which is selected in this study. A new domain ontology is constructed to provide basis for annotations. A bottom-up approach is preferred for semantic annotations to utilize existing web service definitions. Transformations between syntactic web service XML responses and semantic model concepts are defined in transformation files. Transformation files are stored and executed in a separate central transformation repository to enhance abstraction and reusability. An RDF-Store is implemented to store transformed RDF data. Inference power of semantic model is exposed by executing semantic queries in the RDF-Store.

A framework for monitoring the dependencies between users, applications, and other system components, combined with the actual access times and frequencies, was proposed. Operating system commands were used to extract event information from the end-user workstations about the dependencies between system, application and infrastructure components. Access times of system components were recorded, and data mining tools were leveraged to detect usage patterns. This information was integrated and used to predict whether or not the failure of a component would cause an operational impact during certain time periods. The framework was designed to minimize installation and management overhead, to consume minimal system resources (e.g. network bandwidth), and to be deployable on a variety of enterprise systems, including those with low-bandwidth and partial-connectivity characteristics. The framework was implemented in a test environment to demonstrate the feasibility of this approach. The system was tested on small-scale (6 computers in the GT CERCS Laboratory over 35 days) and large-scale (76 CPR nodes across the entire GT campus over 4 months) data sets. The average size of the impact topology was shown to be approximately 4% of the complete topology, and this size reduction was related to providing system administrators the capability to better identify those users and resources most likely to be affected by a designated set of component failures during a designated time period.

<p>Denna rapport behandlar ett tämligen outforskat delområde inom elektroniskt handel, nämligen integration av affärssystem och e-handelssystem. Huvudfrågan i denna rapport går ut på att undersöka hur företag har integrerat sitt affärssystem med sitt e-handelssystem. För att besvara huvudfrågan delades den upp i tre delfrågor. Dessa sökte besvara dels på vilken nivå inom Enterprise Application Integration som företagen hade integrerat systemen, dels vilka integrationstekniker företagen använder för att integrera systemen samt dels vilka effekter integrationen medfört för företagen. För att besvara problemställningen utfördes telefonintervjuer med fyra företag. Resultatet av undersökningen var att samtliga företag hade integrerat på Enterprise Application Integrations datanivå, vilket även var den nivå de hade börjat med att integrera. De integrationstekniker som användes varierade. Det var dock inte särskilt vanligt att använda nyare integrationstekniker. Integrationen medförde genomgående positiva effekter för företagen, även om vissa problem kvarstod. Inga större nya problem uppkom dock.</p>

<p>Background: Information technology (IT) has drastically changed the traditional way to do business. In theory, coordinating information sharing among organisational partners offers notable advantages through cost savings, productivity, improved decision making, and better customer service. Supported by modern information technology, business processes can change and be developed into new more effective forms, both internally and externally. However, as IT facilitates new business opportunities, it requires a steady flow of information and information exchange, both within intra- and inter-organisational contexts where a consensus on terms and definitions 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 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 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 content, and testing. The result also implied the importance to distinguish between an operational and strategic level when working with Application Integration.</p>