With the proliferation of Internet, ERP systems like all the domains of Information Technology have known an important evolution. This final thesis project is a study about the evolution of ERP systems, more precisely about their migration to the Web giving birth to a new generation of systems: the Web-Based or Web-enabled ERP systems. This migration to the Web is justified by the difficulty of making possible the communication between partner’s legacy systems and the organizations’ ERP systems. A historical evolution of these systems is presented in order to understand the reasons that lead vendors to adopt the Web Service Technology. Based on different studies, the main technologies such as Web services, Service-Oriented Architecture and Web Application server are also presented. From an interpretative research approach mySAP ERP has been chosen as a case study. This Master’s thesis has been led into AIRBUS France Company within the framework of the SAP Customer Competence Center (SAPCCC) Web site project. The project is aimed at re-building the SAPCCC Web site. The new characteristic of the Web site is to make it accessible by all AIRBUS partners working with SAP applications. To make the Web site accessible by the partners from their own applications located on their own platforms the development has been done thanks to mySAP ERP which is an ERP using the Web service technology. Finally, this thesis presents a comparative study between traditional ERP systems and the new generation of Web-based ERP systems.

In this thesis we will identify which are the desired features and functionalities for implementing a system capable of acting as an information bridge for content available in the “wired” Internet to be delivered to mobile devices. We will also explore how to design and build such a system based on the specifications within parts of the MUSIS project. The MUSIS’ system development is used as a base of the work described in this thesis and the experiences from those efforts are used in order to design a system with more focus on data portability and media migration. During the development of the MUSIS platform, problems related to system upgrading, i.e. adding new ad-hoc functionalities were discovered. Due to the fact that a user-centred design approach was taken, this was essential in the project. To solve some of these issues, we propose a new component-based system with a high level of scalability and re-usability. We name this system Collect, Convert and Send, CCS. The system shall be seen as a base that can be used as a core system for different projects where interoperability of content between different platforms, devices or systems is important. The implementation of the system is based on the use cases and those theoretical aspects and ideas related to component software, interoperability, media migration and metadata in a Web service context. The results of our efforts give some indications that the use of component software gives a foundation for a service-oriented architecture.

This thesis emphasizes on investigating the relationship between the quality attributes and service oriented architecture (SOA). Due to quality attributes requirements drive the design of software architecture, it is necessary to maintain the positive quality of SOA and improve the negative quality of SOA. This thesis gives an introduction to SOA, Enterprise Service Bus (ESB) and MULE. Then, it covers information on quality of systems and tactics for achieving each quality attribute. Finally, we discuss the quality of SOA in detail, and illustrate how to set up a SOA and how to improve its quality using a case of an order for supermarket. / Order system

Even though there are many software development and project management methodologies available, research and practice both show that IT software development projects still fail, and that the quality of software products does not always meet customers' expectations. There might be multiple causes for such failures, but some of these reasons can be seen to influence or create others. Therefore, the larger the project is, the higher its risk of failure, especially if the teams involved work remotely (distributed and outsourced). This increase in project complexity is considered the motivation for this paper. Similarly, there are other factors that can result in a project's failure and customers' dissatisfaction regarding software quality. All such factors identified by research conducted by organizations specializing in this area are analyzed in order to identify a common root of IT project failures. Once the root causes of these failures have been identified and analyzed, the goal of the Interface based software development methodology is to solve them. The solution offered by an Interface based software development methodology is to improve understanding of software requirements and to describe these requirements with interfaces in an object-oriented way. Interface based software development will support and drive development towards service-oriented architecture (SOA) and component-based development (CBD). The goal of interface based software development is to increase software testability and maintainability and to make it more easily feasible to execute various software development processes in parallel.

Interconnection between various types of IT systems used in an enterprise is crucial in these days. Most of companies are using many different kinds of applications in their daily running of the enterprise which leads to necessity of sharing data across those applications to enable all employees to make a right decision upon correct information. In my diploma thesis I deal with interconnection of two systems -- Business Process Management (BPM) and Business Intelligence (BI). Both systems belong to group of top IT systems with big influence on ongoing business and right decision making on all levels from operational to strategic. My paper contains theoretical as well as practical part of the solution for interconnection of BI and BPM systems. First part is about presenting and describing basic concepts and technologies which are used in process of integration of BI and BPM. At the beginning there is a short introduction to BPM, BI and SOA. Following part is including analysis of three major ways of interconnection between BI and BPM systems. Last part of the first theoretical section presents two products. IBM FileNet P8 representative of BPM system and IBM Cognos 8 BI as a representative of BI system. Second part deals with the practical example of real integration between BI and BPM systems. In first part of this section is simple description of the scenario -- business case. After that there is a detail depiction of two different kinds of integration of BI and BPM. Analysis of benefits, advantages and further possibilities are at the end of work.

Der wirtschaftliche Erfolg von Unternehmen wird heute von der Fähigkeit beeinflusst, die Geschäftsstrategie schneller umsetzen zu können als die Konkurrenz. Wichtige Ziele sind die Erschließung neuer Märkte, die Reduzierung von Kosten sowie die Steigerung der Effizienz. Eine Voraussetzung besteht darin, vorhandene Geschäftsprozesse flexibel anpassen und zügig neue Prozesse einführen zu können. Das bedingt wandlungsfähige und innovationsfördernde Systemlandschaften. An dieser Stelle setzen die durch Geschäftsprozesse getriebenen serviceorientierten Architekturen für ERP-Systeme an. Mit SOA-ERP-Systemen wird es möglich, selektiv und am Bedarf ausgerichtet neue Prozesse zu gestalten und das Prozess-Design mit der Einbindung von Lieferanten, Kunden und Partnern über Unternehmensgrenzen hinweg zu gestalten. SAP Enterprise-SOA bezeichnet die serviceorientierte ERP-Architektur der SAP AG. Die darauf basierenden Anwendungen entstehen – unter Einsatz der Enterprise-SOA Roadmap-Methodik – durch die gezielte Kombination von Plattform-, Ex-tension- und Composite-Applikationen. Letztere stellen hochflexible, aus Enterprise-Services/Services von Drittanbietern erstellte, Anwendungen dar. Deren Design durch SOA-Experten liegt ein hohes Maß an Erfahrungswissen zu Grunde. Dieses stellt den zentralen Aspekt der Speicherung und Wiederverwendung durch fallbasiertes Schließen dar. Im Gegensatz zum bestehenden Ansatz zur Beschreibung von Best-Practice Implementierungen im „SAP Community Network“ ermöglicht der hier dargestellte Vorschlag die strukturierte, prozessbezogene Speicherung sowie die ähnlichkeitsbasierte Wiederverwendung von Composite-Applikationen innerhalb des Roadmap-Prozesses. Schwerpunktmäßig werden dazu Indizes zum Aufbau von Zugriffsstrukturen in der Fallbasis sowie wie ein allgemeingültiges globales und ein beispielhaftes, kontextspezifisches lokales Indexvokabular erarbeitet. Weiterhin erfolgt die Angabe entsprechender Ähnlichkeitsmaße für die ausgeprägten Indizes sowie das Aufzeigen der Ähnlichkeitsbestimmung zwischen zwei Fällen durch einen Nearest-Neighbor Matching Algorithmus.

Supply chains in many industries are experiencing an ever-growing complexity. They involve many actors and, similar to intra-organizational processes, visibility is an important enabler for managing supply chains in an inter-organizational setting. It is the backbone of advanced sup-ply chain (event) management solutions, which serve to detect critical incidents in time and to determine alternative actions. Due to the numerous parties involved, distributed supply chains call for a modular system architecture that aims at re-using visibility data from standardized sources. Following the wide variety of supply chain configurations in many industries there are also many options to design such services. This paper sheds light on these aspects by conduct-ing a case study on EPCIS, a global service specification for capturing and sharing visibility data. Based on three implementations, it shows the main design options for a supply chain vis-ibility service, generic operator models as well as major potentials.:1. Introduction and motivation 2. Research questions and methodology 3. Literature analysis 4. EPCIS case study 4.1. Deutsche Post DHL 4.2. ThyssenKrupp 4.3. GS1 Germany 5. Discussion and findinds 5.1.Design options 5.2. Operator models 5.3. Potentials 6. Conclusions

Throughout history, humans have proven to develop and improve their quality of life constantly. Incorporating mechanical principles into otherwise manual labor was one such aspect. Today, introducing mechanization to the industry and steam power is regarded as the first industrial revolution. Since then, a second and a third have followed, introducing concepts such as electricity, automation, computers, and computerization. Finally, in 2011 the fourth industrial revolution was introduced as Industry 4.0 by a project started in Germany, which considers digitalization. Industry 4.0 uses concepts such as Cyber-Physical Systems (CPS), the Internet of Things (IoT), and cloud computing. The goal of these concepts is to be able to further the capabilities of automation in the industry, creating smart factories. A problem experienced today when making changes to the production line is that an immense amount of hard coding is required for the Programmable Logic Controller (PLC) controlling the system as well as for the system controlling the factory. The Eclipse Arrowhead Framework addresses these issues by applying a particular set of parameters to all systems within the IT infrastructure. The Arrowheadframework offers parameters such as orchestrator, authorization, and a service registry to each system incorporated within the framework. By applying this, the System of Systems (SoS) and the parameters provided by the Arrowhead framework create a local cloud. In doing so, each system within a factory belongs to its local cloud, building a factory made of a cluster of local clouds. By applying the ideas of Industry 4.0, a proof of concept is created, showing that today’s industry would benefit from using the concepts stated above with digital twins. The thesis explores and proves that, with the help of digital twins, today’s industry can cut down on manufacturing process development. In addition, it reduces the time it takes to apply changes to the production line by enabling machine learning to facilitate human interaction. A model factory created by fischertechnik is used, together with a PLC, as the physical twin in this master thesis. In addition, using Siemens Computer-Aided Design (CAD) software NX, a digital twin is created; this digital twin will communicate with the physical twin to simulate the behavior of the physical twin in real-time. A server has been created and is acting as a hub of communication for both of the twins. The use of the digital twin to communicate with the physical twin will enable tremendous advances in automation regarding industry 4.0.

The main subject of this master thesis is the Service-Oriented Architecture (SOA). It shows a complete overview of Web Services in terms of realisation of a SOA. The thesis mentions what is already done and what else remains to ful ll the basic SOA principles. Then, it reviews Java EE platform tools used to deal with the Web Services. Next, it introduces the Java Management Extensions (JMX) technology as a solution of the web service's area - SOA governance. Moreover, it examinates the possible usage of JMX for the web service's management and monitoring issues. Finally, it implements an exemplary web services management and monitoring application on GlassFish server for testing purposes.

Factory shop floors of the future will see a significant increase in interconnected devices for monitoring and control. However, if a Service Orientated Architecture (SOA) is implemented on all such devices then this will result in a large number of permutations of services and composite services. These services combined with other business level components can pose a huge challenge to manage as it is often difficult to keep an overview of all the devices, equipment and services. This thesis proposes an SOA based novel assimilation architecture for integrating disparate industrial hardware based processes and business processes of an enterprise in particular the plastics machinery environment. The key benefits of the proposed architecture are the reduction of complexity when integrating disparate hardware platforms; managing the associated services as well as allowing the Micro Injection Moulding (µIM) process to be monitored on the web through service and data integration. An Enterprise Service Bus (ESB) based middleware layer integrates the Wireless Sensor Network (WSN) based environmental and simulated machine process systems with frontend Google Gadgets (GGs) based web visualisation applications. A business process framework is proposed to manage and orchestrate the resulting services from the architecture. Results from the analysis of the WSN kits in terms of their usability and reliability showed that the Jennic WSN was easy to setup and had a reliable communication link in the polymer industrial environment with the PER being below 0.5%. The prototype Jennic WSN based µIM process monitoring system had limitations when monitoring high-resolution machine data, therefore a novel hybrid integration architecture was proposed. The assimilation architecture was implemented on a distributed server based test bed. Results from test scenarios showed that the architecture was highly scalable and could potentially allow a large number of disparate sensor based hardware systems and services to be hosted, managed, visualised and linked to form a cohesive business process.