Service-Oriented Architecture (SOA) represents an emerging architectural approach that is able to tackle challenges in the contemporary service-based economy, in which the global market revenues are shifting from the manufacture of traditional off-the-shelf products to the provision of diversified services that suffice for customers’ needs. In such a service-based economy, one can envisage an entirely “service-oriented” world, where a massive number of distributed services with different natures and capabilities are provided by various professionals around the world. Problems arise when business applications demand desirable services through different sources and providers that are appropriate for their own benefits and preferences. Therefore, it can be very challenging to design an SOA infrastructure that enables users to exploit this great level of service heterogeneity and quantity. One of the key issues in service-oriented architecture is to achieve efficient service discovery and loosely-coupled service distribution while maintaining a satisfactory degree of scalability, usability, and Web consistency. This thesis deals with SOA infrastructure-level design and implementation issues. It approaches this SOA infrastructure within the scope of Web services, which capture an important, and perhaps the best, ‘realisation’ of SOA. It investigates and formulates how public Web services distributed across the World Wide Web can be augmented by a software platform that enables scalable, user-centred,semantic-enabled, and integration-oriented service retrieval, selection, and matching. The primary goal of this thesis is thus to propose a conceptual framework of an enhanced SOA infrastructure with regard to service distribution and discovery. / It also aims to design and implement a platform (PWSP), by means of which a large number of public Web services on the Web can be distributed based on service demands, retrieved based on service descriptions, selected based on service qualities, and matched based on service messages in a user-centred, scalable, and Web-consistent manner without augmenting existing Web services standards.

<p>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.</p> / Order of supermarket

Detta examensarbete behandlar Service Oriented Architecture (SOA) och dess implementeringar Jini och Web services. SOA beskriver hur applikationsintegration mellan olika plattformar skall ske och innebär att applikationer designas som tjänster för att enkelt integreras med andra applikationer. Dynamisk lokalisering av tjänster via en registertjänst används för att applikationer skall finna andra applikationer. Vi designar och implementerar en mekanism i Web services som gör det möjligt att byta en tjänst under exekvering. Ett sådant byte kan vara intressant av två skäl, tjänster kan registreras utan att vara tillgängliga, eller att det uppstår ett fel under exekvering som gör att tjänsten blir otillgänglig. / This degree project is about Service Oriented Architecture (SOA) and its implementations Jini and Web services. SOA is a description of how application integration between different platforms can be carried out by designing applications as services, which implies an easier integration with other applications. Dynamic location of services is carried out by consultation with a register service so that applications can find other applications. We design and implement a mechanism in Web services that makes it possible to change service during execution. A change of service can be interesting for two reasons, the service might be registered but not available or there might be some sort of fault during execution that makes the service unavailable.

Made available in DSpace on 2014-06-12T15:58:03Z (GMT). No. of bitstreams: 2 arquivo3244_1.pdf: 2061206 bytes, checksum: d9bbab1debda0a2122b877cceb8484ed (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010 / Conselho Nacional de Desenvolvimento Científico e Tecnológico / O reuso de software é um fator extremamente importante para empresas interessadas em aumentar sua produtividade, diminuir os custos e o tempo durante o desenvolvimento de sistemas e melhorar a qualidade de seus produtos e serviços. Nesse contexto, Linhas de Produto de Software (LPS) e Arquitetura Orientada a Serviços (SOA) são duas estratégias que estão atualmente recebendo uma grande atenção, tanto na área acadêmica quanto na indústria de software. Os conceitos de linhas de produto e arquitetura orientada a serviços compartilham alguns objetivos e características que podem ser usados em conjunto para aumentar as taxas de reuso de software. No entanto, para o resultado dessa junção ser otimizado, é necessário utilizar um processo de desenvolvimento bem definido. Caso contrário, a equipe de desenvolvimento poderá produzir software de maneira não sistemática, aumentando as chances de falha, o tempo e o custo de desenvolvimento. Com essa visão, esse trabalho apresenta uma abordagem para o projeto de arquiteturas para linhas de produto orientada a serviços, constituída de um conjunto de atividades e sub atividades com entradas e saídas especificadas, sendo cada uma delas realizada por um conjunto predefinido de papéis com responsabilidades definidas. Essa abordagem visa ajudar arquitetos de software a projetar arquitetura orientada a serviços para domínios específicos. Para garantir a qualidade da abordagem desenvolvida, uma pesquisa extensiva foi realizada para analisar o atual estado da arte de processos para o desenvolvimento orientado a serviços. Foram então considerados os pontos fracos e fortes dos processos estudados com o intuito de identificar e preencher as lacunas neles existentes. Por fim, essa abordagem foi validada e refinada por meio de um estudo acadêmico experimental preliminar

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 of supermarket

Next Generation Networks (NGNs) aim to provide a unified network infrastructure to offer multimedia data and telecommunication services through IP convergence. NGNs utilize multiple broadband, QoS-enabled transport technologies, creating a converged packet-switched network infrastructure, where service-related functions are separated from the transport functions. This requires significant changes in the way how networks are managed to handle the complexity and heterogeneity of NGNs. This thesis proposes a Service Oriented Architecture (SOA) based management framework that integrates heterogeneous management systems in a loose coupling manner. The key benefit of the proposed management architecture is the reduction of the complexity through service and data integration. A network management middleware layer that merges low level management functionality with higher level management operations to resolve the problem of heterogeneity was proposed. A prototype was implemented using Web Services and a testbed was developed using trouble ticket systems as the management application to demonstrate the functionality of the proposed framework. Test results show the correcting functioning of the system. It also concludes that the proposed framework fulfils the principles behind the SOA philosophy.

Le travail de recherche présenté dans ce mémoire s’intéresse aux problèmes d’interopérabilité dans le domaine du Product Lifecycle Management (PLM) et vise à proposer une méthodologie capable d’y remédier. Nous définissons l’objectif stratégique du PLM comme la maîtrise de la complexité qui caractérise le développement et le suivi des produits. Dans ce cadre, l’objectif de l’interopérabilité est le contrôle des interactions entre constituants de ce système complexe PLM. Nous montrons que cet objectif est atteint si on assure la continuité et la conservation du flux sémantique qui circule dans le système. Notre étude est restreinte aux seuls domaines de la conception et de la production, mais a l’ambition de pouvoir s’appliquer à d’autres domaines. La continuité du flux sémantique est assurée par une architecture que nous avons baptisée « médiation multi-échelle orientée services ». Le cœur de cette architecture, le médiateur, se charge d’orienter les flux sémantiques vers les systèmes concernés, et met en correspondance sémantique les informations échangées en s’appuyant sur un méta-modèle d’unification. Nous montrons que pour assurer la robustesse, la flexibilité et l’agilité du système ainsi constitué, il faut privilégier le choix d’un méta-modèle standard générique et extensible. A cet effet, nous proposons une cartographie du standard STEP permettant de choisir le méta-modèle pertinent. Nous illustrons le choix et la définition de ce méta-modèle dans le cas de deux problèmes d’interopérabilité des domaines de la conception et de la production : l’interopérabilité CAO/PDM et l’interopérabilité PDM/ERP. Nous expliquons notre démarche dans la mise en œuvre de la norme PLCS. Par ailleurs, nous introduisons un modèle d’annotations sémantiques du produit qui permet de reconstruire des vues multiples correspondant à différents besoins métiers. Un ensemble de démonstrateurs permet de valider nos propositions et nos résultats. / Research work presented in this manuscript deals with interoperability issues in the domain of Product Lifecycle Management (PLM) and aims at proposing a methodology able to remedy it. We define the objective of PLM as the control of the complexity that characterizes the development and monitoring of the product. In this context, the objective of the interoperability is to control the interactions between components of this PLM complex system. We demonstrate that this objective is reached if we ensure the continuity and the conservation of the semantic flow inside the system. Our study is restricted to design and production fields, but can be extended to other domains. The continuity of the semantic flow is guaranteed by an architecture that we entitled “service-oriented multi-layered mediation”. The main part of this architecture, the mediator, takes care to orientate the semantic flows towards the adequate systems, and semantically connect the exchanged information by relying on an unification meta-model. We demonstrate that, to ensure the robustness the flexibility and the agility of the so-constituted system, the choice of a generic and extensible standard meta-model should be favored. We thus proposed a mapping of STEP standard allowing to choose the adequate meta-model. We illustrate the choice and the definition of this meta-model in the case of two interoperability problems in the design and production domains: the interoperability CAD/PDM and the interoperability PDM/ERP. We illustrate our methodology in the implementation of the PLCS standard. Moreover, we introduce a model of product semantic tags that allows to rebuild the multiple product views corresponding to different actor needs. A set of demonstrators validate our propositions and our results.

The need for adapting rapidly to IT and business changes, reducing costs, delivering improved functionality of services and better integration push organizations towards service oriented architecture (SOA) adaption. Delivering SOA requires building systems at the business level, not just at the IT level. Delivery of services needs concentration on the business needs first. As people are the most important factors in defining business requirements, processes and making business decisions, their active involvement in SOA adoption is essential. SOA adoption is evolutionary rather than revolutionary; it is not possible to be accomplished without cooperation of stakeholders who have effect on the system. Many organizations fail to deliver SOA since they underestimate the role of key business people in SOA development. In order to evolve SOA successfully from business perspective, stakeholder involvement should be conducted from early phases of SOA when important decisions are made and business processes are defined. Service identification is one of the important and main activities in SOA development. This study therefore focuses on service identification of SOA from a business view and regard to stakeholders. Text analysis and interviews are the method components used in this research. Some aspects covering the importance of service identification in SOA development, role of stakeholders in service identification and role of scenarios in stakeholder involvement have been identified through text analysis. And three interviews with experts within the area have verified the identified aspects. The result shows that co-design is an appropriate strategy for conducting service identification regard to stakeholders in an effective way. Different ideas can be visualized, explored and examined through this perspective and a realistic appropriate solution can be found. The challenges of co-design in addressing SOA benefits are also studied through theoretical and empirical parts of the study, and the result is summarized in a table which shows the strengths and weaknesses of co-design strategy in service identification process in addressing SOA goals. The results are categorized to two forms of service identification, consultant driven service identification and internal staff driven service identification. The result of the study can be a contribution in determining the employment of co-design in service identification considering different situations. / Program: Magisterutbildning i informatik

<p>Att designa en generell och utbyggbar mjukvara är inte enkelt, då det krävs en bred kompetens inom många olika områden. Vi belyser i detta arbete en del av problematiken kring design. Utgångspunkten är ett praktikfall vars målmiljö rör processer och integrationer. Huvudfokus ligger på designmönster, men även en bredare genomgång av ämnen så som utvecklingsmetodik, Service Oriented Architecture (SOA), Web Services (WS) och utvecklingsmiljöer presenteras. Arbetet bedrivs i enlighet med riktlinjer från Rational Unified Process (RUP) och slutprodukten är en checklista på tre punkter. De tre punkterna speglar de lärdomar vi dragit av arbetet genom saker vi gjort och saker vi borde ha gjort. God design kan uppnås genom att förstå den uppgift man åtagit sig, utvärdera sitt resultat och delresultat samt genom användandet av rätt verktyg. Framtida forskningsområden med anknytning till vårt rör förslagsvis metoders betydelse för mjukvarudesign, dynamiska perspektiv hos utvecklare och mer enhetlighet kring begreppet SOA.</p>

<p>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.</p> / Order system