<p>Den här rapporten avhandlar framtagandet av en prototyp för en tjänst där abonnenter hos telekomoperatörer ska kunna beställa och konfigurera sina egna tjänster i betydligt större utsträckning än vad som är möjligt idag.</p><p>Detta är möjligt och önskvärt tack vare att det pågår kontinuerlig modernisering av den teknik som idag används i telefonnät och telefonsystem.</p><p>Projektet genomfördes på uppdrag av Tieto i Kalmar som är ett konsultföretag som arbetar mycket med telekomteknik och som har flera stora kunder som arbetar med modernisering av sin teknik.</p><p>Resultatet har blivit en prototyp där användaren på ett flexibelt sätt kan skapa, redigera och radera sina egna tjänster, samt få en grafisk överblick över sina inställningar.</p><p>Prototypen är också enkel för uppdragsgivaren att anpassa för demonstration för olika kunder. Den är dessutom anpassad så att det ska gå så enkelt som möjligt att utveckla den vidare med nya komponenter.</p><p>Från början ingick en student från Rehabiliteringsprogrammet i projektet. Tanken var att kunna genomföra olika typer av användbarhetsanalyser och på så sätt göra prototypen så användarvänlig som möjligt. Då studenten av personliga skäl inte fullföljde projektet redovisas dessa delar av projektet inte i den här rapporten.</p> / <p>This thesis treats the development of a prototype for a service where telecom customers can order and configure their own services to a much higher degree than what is possible today.</p><p>This is possible and desireble due to a continuing modernisation of the technology beeing used in the telecom systems today.</p><p>The project was coducted on the request of Tieto, Kalmar. Tieto is a consulting company that is highly involved in the telecom industry and has several customers that are working with modernisation their technology.</p><p>The result is a prototype called: ”Effect: a prototype for an Easy to use, Flexible, Figurative, Extenable Configuration Tool”. It´s a web application where the users in a flexible way can order, configure and delete their own services, and also get an graphical overview of their settings.</p><p>The prototype is easy for Tieto to adjust when showing it to different customers. It is also adapted in a way that it is easy to extend it with new components.</p><p>In the beginning the project included a student från the Interaction design program. The idea was to conduct a series of usability analysis and with the help of that being able to make the prototype as user friendly as possible. Since the student, for personal reasons, did not finnish the projet, this report will not present anything on that part.</p>

The need of smart devices that uses sensors have never been higher and by the year 2020 it will be over 50 billion devices connected to the internet. All these devices that uses a sensor and are connected to the internet are a part of something called Internet of Things. The purpose of this study has therefore been to implement a stripped IoT platform that doesn’t use any external libraries to lower the cost for minor companies that doesn’t need the more advanced and expensive platforms. After the implementation various stress test will be performed to see the performance of the platform. The study has been done through web- based sources and as a programming language Java has been used in the development environment NetBeans, the database has been made with MySQL workbench. The result of the study has been a platform that uses REST to post and get data from the database. The external library mysql- connector-java-5.1.45 was essential for a connection to the database and therefore had to be used. The result of the stress test was that the platform performed well and could handle at least 500 REST calls per second with a small increase in response time, but the standard deviation was considerably higher. The conclusion was that the platform performed stable at 50 – 250 calls per second and because of it being stripped several platforms could be used in a company to divide the work load between them resulting in a both stable and scalable solution. / Behovet för smarta enheter som använder sensorer har aldrig varit högre och det är trott att vid år 2020 kommer mer än 50 miljarder enheter vara uppkopplad mot internet. Alla dessa enheter med sensorer som är anslutna mot internet går under namnet Internet of Things. Syftet med denna studie har därför varit att skapa en avskalad IoT plattform som inte använder externa bibliotek för att hålla ned kostnaderna för de mindre företagen som inte behöver de mer avancerade och dyrare plattformarna. Efter att plattformen blivit implementerad skulle stresstester utförs för att avgöra hur bra den presterar. Studien har genomförts med hjälp av webbaserade källor och programmeringen av plattformen har utförts i programmeringsmiljön NetBeans i språket Java och databasen är skapad i MySQL workbench. Resultatet av studien har gett en plattform som använder REST för att skicka till och hämta data från databasen. Att göra implementeringen utan att använda externa bibliotek gick inte då biblioteket mysql-connector-java-5.1.45 var essentiellt för uppkoppling mot databasen. Stresstesterna gav att plattformen presterade stabilt och kunde hantera åtminstone 500 REST förfrågningar per sekund med endast en liten ökning i svarstiden, dock blev standardavvikelsen för svarstiden betydligt högre. Slutsatsen av studien blev att eftersom plattformen fungerar stabilt för 50 – 250 förfrågningar per sekund och då den tar upp lite processorkraft kan flera plattformar användas i ett företag för att då fördela arbetskraften emellan dem vilket resulterar i en lösning som både är skalbar samt stabil.

Funcionalidades de software expostas como serviços Web são cada vez mais comuns e suas formas de composição e coordenação são cada vez mais imprescindíveis. Orquestração e coreografia, tradicionais abordagens de composição de serviços Web, são providas por ferramentas voltadas ao gerenciamento de processos de negócio com diferentes enfoques. Apesar do sucesso dessas abordagens, existem ainda desafios a serem superados, tais como a dificuldade de manutenção em fluxos de controle já existentes, o custo de comunicação associado às interações com os serviços Web, o conhecimento do processo de negócio por parte dos serviços e ainda a compatibilidade dos mesmos em uma composição. Como alternativa às abordagens tradicionais, esta dissertação propõe o uso da abordagem WED-flow para composição de serviços Web, de modo que a execução de processos de negócio seja orientada pelas alterações do estado dos dados. Na abordagem proposta, o fluxo de controle não é um requisito, mas sim uma consequência da execução dos serviços Web, o que proporciona maior flexibilidade para o desenvolvimento e a manutenção das aplicações. Mais concretamente, a primeira contribuição deste trabalho é a proposição e a avaliação de cenários possíveis de orquestração e coreografia de acordo com critérios pré-definidos. A segunda contribuição é a implementação da abordagem WED-flow para a composição de serviços Web, bem como sua validação prática e sua avaliação em relação aos cenários de coreografia e orquestração. / Features of software exposed as Web services are becoming more common and their forms of composition and coordination are increasingly essential. Orchestration and choreography, traditional approaches for Web service compositions, are provided by tools that manage business processes with different approaches. Despite the success of these approaches, there are still challenges to be overcome such as the difficulty of maintaining flows in existing control, the communication cost associated with Web service interactions, knowledge of the business process by the services and even their compatibility in service compositions. As an alternative to traditional approaches, this paper proposes the use of WED-flow approach for Web services composition, so that the execution of business processes is driven by changes in data states. In our approach, the control flow is not a requirement but a consequence of the Web service execution, which provides greater flexibility for the development and maintenance of applications. More specifically, the first contribution of this work is to propose and evaluate possible scenarios of orchestration and choreography according to predefined criteria. The second contribution of this work is the implementation of WED-flow approach for Web service compositions, as well as its validation in the choreography and orchestration scenarios.

DH Anticounterfeit, a company working against counterfeit products, has a mobile application that lacks a proper back-end system to handle and store DH Anticounterfeits data. There are plenty of ways to go about to x this problem, but this thesis is focused on the development of a REST API that will be replacing the non-existent system. The main goal is to create the API and run it within a containerized environment using Docker. The whole system should run on Amazon Web Services, that will be working as a server to keep the system going at all times. Nowadays, security is important due to plenty of ways to attack a system, which is why security and authorization will be a high priority. The result will be a well-functioning, high security system that uses MongoDB database to store and process data in a secure way.

Made available in DSpace on 2014-12-17T15:47:55Z (GMT). No. of bitstreams: 1 RodrigoPMA_DISSERT.pdf: 1860763 bytes, checksum: 380e4ec05d43fc5ef9f86cc19b22618b (MD5) Previous issue date: 2011-02-18 / On the last years, several middleware platforms for Wireless Sensor Networks (WSN) were proposed. Most of these platforms does not consider issues of how integrate components from generic middleware architectures. Many requirements need to be considered in a middleware design for WSN and the design, in this case, it is possibility to modify the source code of the middleware without changing the external behavior of the middleware. Thus, it is desired that there is a middleware generic architecture that is able to offer an optimal configuration according to the requirements of the application. The adoption of middleware based in component model consists of a promising approach because it allows a better abstraction, low coupling, modularization and management features built-in middleware. Another problem present in current middleware consists of treatment of interoperability with external networks to sensor networks, such as Web. Most current middleware lacks the functionality to access the data provided by the WSN via the World Wide Web in order to treat these data as Web resources, and they can be accessed through protocols already adopted the World Wide Web. Thus, this work presents the Midgard, a component-based middleware specifically designed for WSNs, which adopts the architectural patterns microkernel and REST. The microkernel architectural complements the component model, since microkernel can be understood as a component that encapsulates the core system and it is responsible for initializing the core services only when needed, as well as remove them when are no more needed. Already REST defines a standardized way of communication between different applications based on standards adopted by the Web and enables him to treat WSN data as web resources, allowing them to be accessed through protocol already adopted in the World Wide Web. The main goals of Midgard are: (i) to provide easy Web access to data generated by WSN, exposing such data as Web resources, following the principles of Web of Things paradigm and (ii) to provide WSN application developer with capabilities to instantiate only specific services required by the application, thus generating a customized middleware and saving node resources. The Midgard allows use the WSN as Web resources and still provide a cohesive and weakly coupled software architecture, addressing interoperability and customization. In addition, Midgard provides two services needed for most WSN applications: (i) configuration and (ii) inspection and adaptation services. New services can be implemented by others and easily incorporated into the middleware, because of its flexible and extensible architecture. According to the assessment, the Midgard provides interoperability between the WSN and external networks, such as web, as well as between different applications within a single WSN. In addition, we assessed the memory consumption, the application image size, the size of messages exchanged in the network, and response time, overhead and scalability on Midgard. During the evaluation, the Midgard proved satisfies their goals and shown to be scalable without consuming resources prohibitively / Nos ?ltimos anos, foram propostas diversas solu??es de plataformas de middleware para Redes de Sensores Sem Fio (RSSF). A maioria dessas plataformas n?o considera quest?es de como integrar os componentes a partir de arquiteturas de middleware gen?ricas. Muitos requisitos necessitam ser considerados em um projeto de middleware para RSSF e um aspecto desejado, neste caso, consiste na possibilidade de modificar o c?digo fonte do middleware sem mudar o comportamento externo do middleware. Assim, ? almejado que exista uma arquitetura gen?rica de middleware que seja capaz de oferece uma configura??o otimizada de acordo com os requisitos da aplica??o que se deseje atender a cada momento. A ado??o de middleware baseados em modelo de componentes consiste em uma abordagem promissora, pois permite uma melhor abstra??o, desaclopamento, modulariza??o e gerenciamento das funcionalidades internas do middleware. Outro problema presente nos middleware atuais consiste no tratamento da interoperabilidade com redes externas ?s RSSF, como por exemplo, a Web. A maioria dos middleware atuais n?o disp?e da funcionalidade de acessar os dados providos pela RSSF atrav?s da World Wide Web, de forma a tratar esses dados como recursos Web e que eles possam ser acessados atrav?s de protocolos j? adotados na World Wide Web. Diante dessas quest?es, esta disserta??o apresenta o Midgard, um middleware baseado em componentes especificamente concebido para RSSFs, que adota os padr?es arquiteturais microkernel e REST. O padr?o arquitetural microkernel complementa a estrat?gia arquitetural baseada em modelo de componentes, haja vista que o microkernel pode ser compreendido como um componente que encapsula o n?cleo do sistema, sendo esse n?cleo encarregado de inicializar apenas os servi?os necess?rios, assim como remov?-los quando n?o s?o mais necess?rios. J? o padr?o REST define uma forma padronizada e leve de comunica??o entre diferentes aplica??es baseada nos padr?es adotados na Web e atrav?s dele possibilita tratar os dados da RSSF como recursos Web, permitindo que sejam acessados atrav?s de protocolo j? adotado na World Wide Web. Os dois principais objetivos do Midgard s?o (i) prover f?cil acesso via Web aos dados gerados pela RSSF, tratando tais dados como recursos Web, seguindo os princ?pios do paradigma Web of Things, e (ii) prover aos desenvolvedores de aplica??es para RSSF capacidades para a instancia??o apenas dos servi?os espec?ficos exigidos pela aplica??o, dessa forma gerando um middleware customizado e economizando recursos dos n?s. O Midgard permite utilizar a RSSF como recursos Web e ainda prover uma arquitetura de software coesa e fracamente acoplada, endere?ando interoperabilidade e customiza??o no mesmo middleware. Al?m disso, prov? dois servi?os necess?rios para a maior parte das aplica??es de RSSF, os servi?os de configura??o e o de inspe??o e adapta??o. Novos servi?os podem ser implementados por terceiros e facilmente incorporados ao middleware, gra?as a sua arquitetura flex?vel e extens?vel. De acordo com a avalia??o realizada, o Midgard prov? interoperabilidade entre a RSSF e redes externas, como a Web, assim como entre aplica??es distintas dentro de uma mesma RSSF. Al?m disso, foram avaliados o consumo de mem?ria do Midgard, o tamanho da imagem da aplica??o, o tamanho das mensagens trafegadas na rede, assim como tempo de resposta, sobrecarga e escalabilidade. Durante a avalia??o realizada o Midgard provou cumprir seus objetivos e demonstrou ser escal?vel sem consumir recursos proibitivamente

I detta projekt har SharePoint integrerats i SiteVision. Flera av SiteVision AB:s kunder har efterfrågat en möjlighet att integrera produkten med SharePoint. Microsoft tillhandahåller inga direkta API:er för SharePoints objektmodell i Java som SiteVision är skrivet i. SiteVision AB visste inte hur kunderna ville kunna arbeta med SharePoint i SiteVision och var angelägna om att ta reda på detta. Det övergripande syftet med denna rapport har varit att möjliggöra en attraktiv integration av SharePoint från SiteVision. Detta har utförts genom att undersöka vilka delar av SharePoint som SiteVision AB:s kunder vill kunna komma åt från SiteVision och hur kunderna vill kunna komma åt dessa delar i SiteVision. Undersökningen har genomförts genom kvalitativa intervjuer med några av SiteVision AB:s kunder. Undersökningen har visat att kunderna helst vill ha en integration mot SharePoints dokumenthanteringssystem. De vill ha möjligheten att lista filer från SharePoint i SiteVision utifrån en given mapp eller metadata. De vill även kunna söka efter SharePoint-filer i SiteVision. Ett internt API för kommunikation mot SharePoint i Java har konstruerats. Efter kundernas önskemål har en SiteVision-modul som listar filer utifrån en angiven mapp skapats. Dessutom har en enkel prototyp till sökmodul konstruerats. Resultaten från intervjuerna kan inte anses vara representativa för hela kundkretsen men gav en indikation om vad som skulle utvecklas först. Projektets mål är uppfyllda men modulerna behöver utvecklas vidare innan de kan lanseras. / In this thesis project, SharePoint has been integrated in SiteVision. Several customers of SiteVision AB have requested an integration of SharePoint from SiteVision. Microsoft doesn’t provide any API for Java to SharePoint object model. SiteVision AB did not know in what form the customers wanted to access SharePoint from SiteVision but was keen to find out. The overall aim with this thesis has been to make an appealing integration of SharePoint from SiteVision possible. This has been accomplished by performing a study investigating what parts of SharePoint the customers wanted to access from SiteVision and in what form they wanted to access it. The study has been performed by qualitative interviews with some of the customers of SiteVision AB. The study has shown that the customers most of all wants to integrate the document management system of SharePoint. They want to be able to view SharePoint files inside SiteVision based on a provided folder, or file meta data. They also want to search for SharePoint files in SiteVision. An internal API for communication with SharePoint in Java has been constructed. Based on the customers’ requests, a SiteVision module that lists SharePoint files based on a folder has been created. Furthermore, a simple prototype for a search module has been constructed. The results from the study cannot be considered as representative of all customers but gave an indication of what should be developed first. The overall aim has been fulfilled but the modules need additional developing before they can be released.

Web API:er i dess olika former är ett vanligt sätt att tillgängliggöra tjänster via webben. Idag är REST den dominerande arkitekturen för utveckling av publika API:er. När flera web services slås samman kallas det för en mashup. Problemet som undersöks är hur flera REST API:er kan slås samman till en mashup. Syftet med det här arbetet är att föreslå en generell arkitektur för mashups vid sammanslagning av REST API:er. Arbetet utfördes som en designundersökning där målet var att ta fram en artefakt i form av en generell arkitektur för mashups av REST API:er. Med hjälp av tidigare forskning togs egenskaper fram som lägger grunden till den nya arkitekturen som föreslagits i det här arbetet. Arkitekturen implementerades som en applikation hos företaget Cygate AB. Arkitekturen utvärderades sedan av Cygate AB med hjälp av fyra kriterier vilka mäter kvalitén på mjukvara. Arkitekturen anses vara av god kvalité enligt den utvärdering som utfördes av Cygate AB. Slutsatsen drogs att arkitekturen är tillämpbar i liknande scenarion där flera REST API:er slås samman i en mashup. / Web APIs in their different shapes and sizes are a common way to make services accessible through the web. Today, the REST architectural style is the dominating approach to develop public APIs. When combining several web services, it is called creating a mashup. The problem explored in this thesis is how several REST APIs can be combined into a mashup. Consequently, the purpose of this thesis is to suggest a generic architecture for mashups combining REST APIs. A design science approach is used in this study to develop an artifact in the form of a generic architecture for mashups of REST APIs. By studying previous research, characteristics and properties are found that represent the basis of the proposed architecture. The architecture is implemented as an application in a real world scenario at Cygate AB. The architecture is, finally, evaluated by Cygate AB through four criteria that measure software quality. The architecture is deemed to be of good quality according to the evaluation performed by Cygate AB. Conclusions can be made that the architecture is applicable in similar scenarios where several REST APIs are combined to a mashup.

Den här rapporten avhandlar framtagandet av en prototyp för en tjänst där abonnenter hos telekomoperatörer ska kunna beställa och konfigurera sina egna tjänster i betydligt större utsträckning än vad som är möjligt idag. Detta är möjligt och önskvärt tack vare att det pågår kontinuerlig modernisering av den teknik som idag används i telefonnät och telefonsystem. Projektet genomfördes på uppdrag av Tieto i Kalmar som är ett konsultföretag som arbetar mycket med telekomteknik och som har flera stora kunder som arbetar med modernisering av sin teknik. Resultatet har blivit en prototyp där användaren på ett flexibelt sätt kan skapa, redigera och radera sina egna tjänster, samt få en grafisk överblick över sina inställningar. Prototypen är också enkel för uppdragsgivaren att anpassa för demonstration för olika kunder. Den är dessutom anpassad så att det ska gå så enkelt som möjligt att utveckla den vidare med nya komponenter. Från början ingick en student från Rehabiliteringsprogrammet i projektet. Tanken var att kunna genomföra olika typer av användbarhetsanalyser och på så sätt göra prototypen så användarvänlig som möjligt. Då studenten av personliga skäl inte fullföljde projektet redovisas dessa delar av projektet inte i den här rapporten. / This thesis treats the development of a prototype for a service where telecom customers can order and configure their own services to a much higher degree than what is possible today. This is possible and desireble due to a continuing modernisation of the technology beeing used in the telecom systems today. The project was coducted on the request of Tieto, Kalmar. Tieto is a consulting company that is highly involved in the telecom industry and has several customers that are working with modernisation their technology. The result is a prototype called: ”Effect: a prototype for an Easy to use, Flexible, Figurative, Extenable Configuration Tool”. It´s a web application where the users in a flexible way can order, configure and delete their own services, and also get an graphical overview of their settings. The prototype is easy for Tieto to adjust when showing it to different customers. It is also adapted in a way that it is easy to extend it with new components. In the beginning the project included a student från the Interaction design program. The idea was to conduct a series of usability analysis and with the help of that being able to make the prototype as user friendly as possible. Since the student, for personal reasons, did not finnish the projet, this report will not present anything on that part.

iSmart Taxi är en Android mobilapplikation (app) för taxiförarna på iSmart Taxi AB. Förarna kan med hjälp av denna applikation rapportera deras körningar. Denna applikation har skapats med hjälp av ett REST-API för att interagera med databasen.   Rapporten innehåller beskrivning om hur applikationen skapades och hur återkoppling från testfall som genomfördes av användarna påverkade applikationens design. / iSmart Taxi is a mobile application (app) for taxi drivers at iSmart TaxiAB. The application helps the drivers to register their fares on an Android mobile. A REST-API was build to interact with the database.   The report contains a description of how the application was created and how the feedback from the tests conducted by the users affected application design.

Funcionalidades de software expostas como serviços Web são cada vez mais comuns e suas formas de composição e coordenação são cada vez mais imprescindíveis. Orquestração e coreografia, tradicionais abordagens de composição de serviços Web, são providas por ferramentas voltadas ao gerenciamento de processos de negócio com diferentes enfoques. Apesar do sucesso dessas abordagens, existem ainda desafios a serem superados, tais como a dificuldade de manutenção em fluxos de controle já existentes, o custo de comunicação associado às interações com os serviços Web, o conhecimento do processo de negócio por parte dos serviços e ainda a compatibilidade dos mesmos em uma composição. Como alternativa às abordagens tradicionais, esta dissertação propõe o uso da abordagem WED-flow para composição de serviços Web, de modo que a execução de processos de negócio seja orientada pelas alterações do estado dos dados. Na abordagem proposta, o fluxo de controle não é um requisito, mas sim uma consequência da execução dos serviços Web, o que proporciona maior flexibilidade para o desenvolvimento e a manutenção das aplicações. Mais concretamente, a primeira contribuição deste trabalho é a proposição e a avaliação de cenários possíveis de orquestração e coreografia de acordo com critérios pré-definidos. A segunda contribuição é a implementação da abordagem WED-flow para a composição de serviços Web, bem como sua validação prática e sua avaliação em relação aos cenários de coreografia e orquestração. / Features of software exposed as Web services are becoming more common and their forms of composition and coordination are increasingly essential. Orchestration and choreography, traditional approaches for Web service compositions, are provided by tools that manage business processes with different approaches. Despite the success of these approaches, there are still challenges to be overcome such as the difficulty of maintaining flows in existing control, the communication cost associated with Web service interactions, knowledge of the business process by the services and even their compatibility in service compositions. As an alternative to traditional approaches, this paper proposes the use of WED-flow approach for Web services composition, so that the execution of business processes is driven by changes in data states. In our approach, the control flow is not a requirement but a consequence of the Web service execution, which provides greater flexibility for the development and maintenance of applications. More specifically, the first contribution of this work is to propose and evaluate possible scenarios of orchestration and choreography according to predefined criteria. The second contribution of this work is the implementation of WED-flow approach for Web service compositions, as well as its validation in the choreography and orchestration scenarios.