Spelling suggestions: "subject:"serviceoriented"" "subject:"derviceoriented""
51 |
Uma infra-estrutura de desenvolvimento de sistemas de informação orientados a serviços distribuídos para agricultura de precisão. / An infrastructure for developing distributed service-oriented information systems for precision agriculture.Murakami, Edson 18 August 2006 (has links)
Interpretar a enorme quantidade de dados coletados, entender as causas e propor estratégias para gerenciar a variabilidade do campo, freqüentemente são apontados como alguns dos principais problemas para o avanço da agricultura de precisão, AP. Os sistemas de informação tornam-se fundamentais na solução desses problemas, mas apesar de existirem muitos pacotes de software disponíveis no mercado, variando de muito simples a muito sofisticados e diversos sistemas originados de experiências de pesquisas, a natureza proprietária e monolítica das soluções impedem o uso em larga escala. A AP envolve uma grande variedade de técnicas de análise, fontes e formatos de dados, perfis de usuário, e muitos outros aspectos que tornam uma aplicação muito complexa do ponto de vista da engenharia de software. Com o objetivo de fornecer a base para o desenvolvimento de sistemas de informação para AP baseados em padrões abertos e plataformas de software livre, uma infra-estrutura de desenvolvimento de sistemas de informação para a agricultura de precisão é proposta. Com base nas idéias seminais dessa proposta, são desenvolvidos protótipos para a condução de experimentos, os quais exploram caminhos de evolução para a infra-estrutura, com especial atenção sobre aspectos de arquitetura de software. Como estudo de caso, uma aplicação web que realiza filtragem de dados de monitores de produtividade é apresentada. Usando a metodologia de desenvolvimento em espiral, sucessivas versões dessa aplicação foram criadas e os resultados usados para propor melhoramentos à infra-estrutura. A infra-estrutura final contém cinco componentes: uma arquitetura de referência para sistemas de informação orientados a serviços para AP, uma linguagem padrão para troca de dados entre serviços agrícolas, um barramento para conexão de serviços agrícolas, um provedor de serviços geoespaciais e um portal para serviços agrícolas. Ela se mostrou adequada para a criação de sistemas de informação para AP interoperáveis, de baixo custo e com capacidade de evolução, mudando o paradigma dos sistemas para AP preponderantemente proprietários e monolíticos para abertos e orientados a serviços distribuídos. / Interpreting the huge amount of data collected, understanding the causes and being able to propose sound strategies for the field variability management are frequently pointed out as major issues for the advance of precision agriculture. Therefore, the information systems become fundamental for the solution of these problems. Although there are many available software packages in the market, varying from simple to very sophisticated and diverse systems deriving from experiences of research, the monolithic and proprietary nature of the solutions hinder their use in wide scale. Precision agriculture involves a great variety of techniques of data analysis, data sources, data formats, user profiles, and many other aspects that make it a complex application from the software engineering point of view. Aiming to supply the base for the development of open standards-based precision agriculture information systems and free software platforms, an infrastructure for developing precision agriculture information systems is proposed. Based on the fundamentals of that proposal, prototypes are developed which explore different evolutionary paths for the infrastructure, with special attention to software architecture aspects. As a case study, a yield monitor data filtering web application is presented. Using the spiral development methodology, successive versions of this application were created and the results used to improve the infrastructure. The final infrastructure contains five components: a service-oriented reference architecture for precision agriculture information systems, a standard language for data exchange between agricultural services, a service bus for connecting agricultural services, a geospatial services provider, and an agricultural services portal. It revealed to be adequate for the creation of precision agriculture interoperable systems, of low cost and with capacity for evolution, moving the paradigm of systems for AP preponderantly monolithic and proprietary to open and distributed service-oriented.
|
52 |
Projeto e implementação de um gerador automático de serviços web a partir de diagramas de classes / Design and implementation of an automatic generator of web services from class diagramsSchettini Filho, Domenico 21 March 2016 (has links)
A indústria de desenvolvimento de software está em constante evolução e em busca de novos desafios, como por exemplo: novas tecnologias, linguagens de programação e estratégias para aumentar a produtividade no desenvolvimento. Com o passar do tempo, essa evolução desejada tem se concretizado, em especial com o surgimento de conceitos como Service Oriented Architecture (SOA) e Model-Driven Development (MDD). Nesse contexto, ganha importância a reutilização de software, por exemplo por meio do uso de serviços que facilitam a interoperabilidade entre diferentes sistemas. Ambientes de desenvolvimento de software, em especial ambientes de reúso de software, poderiam se adequar à arquitetura SOA para facilitar a disponibilização de serviços a outros ambientes, promovendo sua integração e aumentando a possibilidade de reúso. Após um levantamento bibliográfico sobre ambientes integrados de reúso que utilizassem serviços para permitir o compartilhamento de recursos, percebeu-se que os trabalhos nessa direção são poucos. Ao mesmo tempo, observou-se que para integração de sistemas por meio de serviços é necessário criar camadas de acesso às entidades dos sistemas que compartilharão informações. A implementação desses serviços de forma manual é repetitiva e sujeita a erros, principalmente por programadores que não estão familiarizados com SOA. Por outro lado, diagramas de classes em UML (Unified Modeling Language) são de amplo conhecimento por parte de desenvolvedores e estão em um nível de abstração que é suficientemente detalhado para permitir a derivação de serviços de acesso às suas classes. Desta forma, para atender uma demanda crescente de sistemas que precisam oferecer serviços para possibilitar sua integração com outros sistemas, este mestrado tem por objetivo promover a geração automatizada de código de serviços por meio de transformações de modelo para texto, em que o modelo de entrada é um diagrama de classes derivado da UML e os serviços gerados cobrem operações básicas do tipo CRUD. O gerador resultante foi validado por meio de duas provas de conceito e mostrou-se adequado para cumprir os objetivos estabelecidos, visto que o desenvolvedor trabalha com um modelo em alto nível de abstração, não precisando conhecer os detalhes inerentes à implementação dos serviços. / The software development industry is constantly evolving and looking for challenges, such as: new technologies, programming languages and strategies to increase developers productivity. During the course of time, this required evolution has been concretized, especially with the emergency of concepts such as Service Oriented Architecture (SOA) and Model-Driven Development (MDD). In this context, software reuse gains importance, for example through the use of services that ease the interoperability of different systems. Software development environments, in special reuse environments, could be adapted to the SOA architecture to ease the availability of services to other environments, thus promoting its integration and possibility of reuse. After a literature review about integrated reuse environments that use services to allow resources sharing, it has been observed that there are only a few works in this direction. At the same time, it was observed that for system integration through services it is required to create an access layer for the system entities that share information. The manual implementation of these services is repetitive and error prone, especially for programmers who are not familiar with SOA. On the other hand, UML (Unified Modeling Language) class diagrams are widely known by developers and are at a level of abstraction that is sufficiently detailed to allow the derivation of access services to their classes. Thus, to meet a growing demand for systems that need to provide services to enable its integration with other systems, this masters dissertation aims to promote the automated generation of service code through transformations from model to text, where the input model is a class diagram derived from UML, and the generated services cover the basic CRUD operations. The resulting generator has been validated through two proofs of concepts and was adequate to meet the stated objectives, as the developer works with a model in a high abstraction level, and does not need to know the details related with the service implementation.
|
53 |
A Static Analysis Approach For Service Oriented Software Engineering (sose) DesignsCermikli, Can 01 September 2010 (has links) (PDF)
In this thesis, a static analysis approach is introduced in order to develop correct business
processes according to the Web Service Business Process Execution Language (WS-BPEL)
specification. The modeling of the business processes are conducted with Business Process
Execution Language (BPEL) which is a popular orchestrator of Service Oriented Architectures
(SOA) based system through the description of workflow. This approach is also integrated
to the Service Oriented Software Engineering (SOSE) design technique. The integration
of this approach aims the development of complex business processes more robust and
implementation of them more accurate and low error prone. Moreover, this approach will also
decrease the development cost of the system and rework in the implementation phase. The
implementation of the approach is also conducted and it is integrated to the existing service
oriented architecture based tool named Service Oriented Software Engineering Tool (SOSECASE).
This integration forwards the SOSECASE a step forward to an all-in-one service
oriented architecure software development tool.
|
54 |
Proceedings of the 3rd Ph.D. Retreat of the HPI Research School on Service-oriented Systems EngineeringJanuary 2009 (has links)
Design and Implementation of service-oriented architectures imposes a huge number of research questions from the fields of software engineering, system analysis and modeling, adaptability, and application integration. Component orientation and web services are two approaches for design and realization of complex web-based system.
Both approaches allow for dynamic application adaptation as well as integration of enterprise application.
Commonly used technologies, such as J2EE and .NET, form de facto standards for the realization of complex distributed systems.
Evolution of component systems has lead to web services and service-based architectures. This has been manifested in a multitude of industry standards and initiatives such as XML, WSDL UDDI, SOAP, etc. All these achievements lead to a new and promising paradigm in IT systems engineering which proposes to design complex software solutions as collaboration of contractually defined software services.
Service-Oriented Systems Engineering represents a symbiosis of best practices in object-orientation, component-based development, distributed computing, and business process management. It provides integration of business and IT concerns.
The annual Ph.D. Retreat of the Research School provides each member the opportunity to present his/her current state of their research and to give an outline of a prospective Ph.D. thesis. Due to the interdisciplinary structure of the Research Scholl, this technical report covers a wide range of research topics. These include but are not limited to: Self-Adaptive Service-Oriented Systems, Operating System Support for Service-Oriented Systems, Architecture and Modeling of Service-Oriented Systems, Adaptive Process Management, Services
Composition and Workflow Planning, Security Engineering of Service-Based IT Systems, Quantitative Analysis and Optimization of Service-Oriented Systems, Service-Oriented Systems in 3D Computer Graphics, as well as Service-Oriented Geoinformatics. / Der Entwurf und die Realisierung dienstbasierender Architekturen wirft eine Vielzahl von Forschungsfragestellungen aus den Gebieten der Softwaretechnik, der Systemmodellierung und -analyse, sowie der Adaptierbarkeit und Integration von Applikationen auf.
Komponentenorientierung und WebServices sind zwei Ansätze für den effizienten Entwurf und die Realisierung komplexer Web-basierender Systeme. Sie ermöglichen die Reaktion auf wechselnde Anforderungen ebenso, wie die Integration großer komplexer Softwaresysteme.
Heute übliche Technologien, wie J2EE und .NET, sind de facto Standards für die Entwicklung großer verteilter Systeme. Die Evolution solcher Komponentensysteme führt über WebServices zu dienstbasierenden Architekturen. Dies manifestiert sich in einer Vielzahl von Industriestandards und Initiativen wie XML, WSDL, UDDI, SOAP. All diese Schritte führen letztlich zu einem neuen, Zielversprechenden Paradigma für IT Systeme, nach dem komplexe Softwarelösungen durchdie Integration vertraglich vereinbarter Software-Dienste aufgebaut werden
sollen.
„Service-Oriented Systems Engineering“ repräsentiert die Symbiose bewährter Praktiken aus den Gebieten der Objektorientierung, der Komponentenprogrammierung, des verteilten Rechnen sowie der Geschäftsprozesse und berücksichtigt auch die Integration von Geschäftsanliegen und Informationstechnologien.
Die Klausurtagung des Forschungskollegs „Service-oriented Systems Engineering“ findet einmal jährlich statt und bietet allen Kollegiaten die Möglichkeit den Stand ihrer aktuellen Forschung darzulegen.
Bedingt durch die Querschnittstruktur des Kollegs deckt dieser Bericht ein große Bandbreite aktueller Forschungsthemen ab. Dazu zählen unter anderem Self-Adaptive Service-Oriented Systems, Operating System Support for Service-Oriented Systems, Architecture and Modeling of Service-Oriented Systems, Adaptive Process Management, Services Composition and Workflow Planning, Security Engineering of Service-Based IT Systems, Quantitative Analysis and Optimization of Service-Oriented Systems, Service-Oriented Systems in 3D Computer Graphics sowie Service-Oriented Geoinformatics.
|
55 |
Proceedings of the 4th Ph.D. Retreat of the HPI Research School on Service-oriented Systems EngineeringAlnemr, Rehab, Polyvyanyy, Artem, AbuJarour, Mohammed, Appeltauer, Malte, Hildebrandt, Dieter, Thomas, Ivonne, Overdick, Hagen, Schöbel, Michael, Uflacker, Matthias, Kluth, Stephan, Menzel, Michael, Schmidt, Alexander, Hagedorn, Benjamin, Pascalau, Emilian, Perscheid, Michael, Vogel, Thomas, Hentschel, Uwe, Feinbube, Frank, Kowark, Thomas, Trümper, Jonas, Vogel, Tobias, Becker, Basil January 2010 (has links)
No description available.
|
56 |
A Reference Architecture for Service Lifecycle Management – Construction and Application to Designing and Analyzing IT SupportFischbach, Michael 10 November 2014 (has links) (PDF)
Service-orientation and the underlying concept of service-oriented architectures are a means to successfully address the need for flexibility and interoperability of software applications, which in turn leads to improved IT support of business processes. With a growing level of diffusion, sophistication and maturity, the number of services and interdependencies is gradually rising. This increasingly requires companies to implement a systematic management of services along their entire lifecycle. Service lifecycle management (SLM), i.e., the management of services from the initiating idea to their disposal, is becoming a crucial success factor.
Not surprisingly, the academic and practice communities increasingly postulate comprehensive IT support for SLM to counteract the inherent complexity. The topic is still in its infancy, with no comprehensive models available that help evaluating and designing IT support in SLM. This thesis presents a reference architecture for SLM and applies it to the evaluation and designing of SLM IT support in companies. The artifact, which largely resulted from consortium research efforts, draws from an extensive analysis of existing SLM applications, case studies, focus group discussions, bilateral interviews and existing literature.
Formal procedure models and a configuration terminology allow adapting and applying the reference architecture to a company’s individual setting. Corresponding usage examples prove its applicability and demonstrate the arising benefits within various SLM IT support design and evaluation tasks. A statistical analysis of the knowledge embodied within the reference data leads to novel, highly significant findings. For example, contemporary standard applications do not yet emphasize the lifecycle concept but rather tend to focus on small parts of the lifecycle, especially on service operation. This forces user companies either into a best-of-breed or a custom-development strategy if they are to implement integrated IT support for their SLM activities. SLM software vendors and internal software development units need to undergo a paradigm shift in order to better reflect the numerous interdependencies and increasing intertwining within services’ lifecycles. The SLM architecture is a first step towards achieving this goal.
|
57 |
Proceedings of the 7th Ph.D. Retreat of the HPI Research School on Service-oriented Systems EngineeringMeinel, Christoph, Plattner, Hasso, Döllner, Jürgen, Weske, Mathias, Polze, Andreas, Hirschfeld, Robert, Naumann, Felix, Giese, Holger, Baudisch, Patrick January 2014 (has links)
Design and Implementation of service-oriented architectures imposes a huge number of research questions from the fields of software engineering, system analysis and modeling, adaptability, and application integration. Component orientation and web services are two approaches for design and realization of complex web-based system. Both approaches allow for dynamic application adaptation as well as integration of enterprise application.
Commonly used technologies, such as J2EE and .NET, form de facto standards for the realization of complex distributed systems. Evolution of component systems has lead to web services and service-based architectures. This has been manifested in a multitude of industry standards and initiatives such as XML, WSDL UDDI, SOAP, etc. All these achievements lead to a new and promising paradigm in IT systems engineering which proposes to design complex software solutions as collaboration of contractually defined software services.
Service-Oriented Systems Engineering represents a symbiosis of best practices in object-orientation, component-based development, distributed computing, and business process management. It provides integration of business and IT concerns.
The annual Ph.D. Retreat of the Research School provides each member the opportunity to present his/her current state of their research and to give an outline of a prospective Ph.D. thesis. Due to the interdisciplinary structure of the Research Scholl, this technical report covers a wide range of research topics. These include but are not limited to: Self-Adaptive Service-Oriented Systems, Operating System Support for Service-Oriented Systems, Architecture and Modeling of Service-Oriented Systems, Adaptive Process Management, Services Composition and Workflow Planning, Security Engineering of Service-Based IT Systems, Quantitative Analysis and Optimization of Service-Oriented Systems, Service-Oriented Systems in 3D Computer Graphics sowie Service-Oriented Geoinformatics. / Der Entwurf und die Realisierung dienstbasierender Architekturen wirft eine Vielzahl von Forschungsfragestellungen aus den Gebieten der Softwaretechnik, der Systemmodellierung und -analyse, sowie der Adaptierbarkeit und Integration von Applikationen auf. Komponentenorientierung und WebServices sind zwei Ansätze für den effizienten Entwurf und die Realisierung komplexer Web-basierender Systeme. Sie ermöglichen die Reaktion auf wechselnde Anforderungen ebenso, wie die Integration großer komplexer Softwaresysteme.
Heute übliche Technologien, wie J2EE und .NET, sind de facto Standards für die Entwicklung großer verteilter Systeme. Die Evolution solcher Komponentensysteme führt über WebServices zu dienstbasierenden Architekturen. Dies manifestiert sich in einer Vielzahl von Industriestandards und Initiativen wie XML, WSDL, UDDI, SOAP. All diese Schritte führen letztlich zu einem neuen, vielversprechenden Paradigma für IT Systeme, nach dem komplexe Softwarelösungen durch die Integration vertraglich vereinbarter Software-Dienste aufgebaut werden sollen.
"Service-Oriented Systems Engineering" repräsentiert die Symbiose bewährter Praktiken aus den Gebieten der Objektorientierung, der Komponentenprogrammierung, des verteilten Rechnen sowie der Geschäftsprozesse und berücksichtigt auch die Integration von Geschäftsanliegen und Informationstechnologien.
Die Klausurtagung des Forschungskollegs "Service-oriented Systems Engineering" findet einmal jährlich statt und bietet allen Kollegiaten die Möglichkeit den Stand ihrer aktuellen Forschung darzulegen. Bedingt durch die Querschnittstruktur des Kollegs deckt dieser Bericht ein große Bandbreite aktueller Forschungsthemen ab. Dazu zählen unter anderem Self-Adaptive Service-Oriented Systems, Operating System Support for Service-Oriented Systems, Architecture and Modeling of Service-Oriented Systems, Adaptive Process Management, Services Composition and Workflow Planning, Security Engineering of Service-Based IT Systems, Quantitative Analysis and Optimization of Service-Oriented Systems, Service-Oriented Systems in 3D Computer Graphics sowie Service-Oriented Geoinformatics.
|
58 |
ApAM : un environnement pour le développement et l'exécution d'applications ubiquitaires / ApAM : An environment for the development and execution of ubiquitous applicationsDamou, Elmehdi 25 October 2013 (has links)
Simplifier notre interaction avec les entités informatiques interconnectées de notre environnement et faciliter l'exploitation des informations générées par celles-ci est l'objectif des environnements et applications ubiquitaires. Le comportement des applications ubiquitaires dépend de l'état et de la disponibilité des entités (logicielles ou dispositifs) qui compose l'environnement ubiquitaire dans lequel ils évoluent, ainsi que des préférences et localisation des utilisateurs. Développer et exécuter des applications ubiquitaires est un véritable défi que notre approche essaie de relever au travers de l'environnement d'exécution ApAM. Considérant que l'environnement d'exécution est imprévisible, nous partons du principe qu'une application ubiquitaire doit disposer d'une grande flexibilité dans le choix de ses composants et que cette composition doit être automatique. Nous proposons une description abstraite et implicite de la composition (où les composants et les liens entre eux ne sont pas décrits explicitement), ce qui permet de construire l'application incrémentalement pendant la phase d'exécution. La plate-forme d'exécution ApAM implémente ces mécanismes de composition incrémentale et s'en sert pour conférer aux applications ubiquitaires la capacité de « résister » et de s'adapter aux changements imprévisibles de l'environnement d'exécution. Cette propriété dite de résilience est au cœur de notre approche car elle permet aux programmeurs de développer « simplement » des applications « résilientes » sans avoir à décrire les diverses adaptations à réaliser, et même sans connaitre toutes les perturbations de l'environnement auquel elles seront soumises. Notre proposition offre le moyen de développer et d'exécuter des applications ayant un haut niveau de résilience vis-à-vis des évolutions de leur contexte d'exécution, grâce à des mécanismes automatiques capables de construire et de modifier à l'exécution l'architecture logicielle des applications ubiquitaire. Les mécanismes fournis sont génériques mais peuvent être étendus et spécialisés pour s'adapter plus finement à certaines applications ou à des domaines métiers spécifiques. / The goal of ubiquitous environments and applications is to simplify our interaction with interconnected software and hardware entities, and to allow the exploitation of the information that they gather and generate. The behavior of ubiquitous applications depends on the state and the availability of the software and hardware entities that compose the ubiquitous environment in which they are constantly evolving, as well as, the preferences and locations of users. Developing and executing ubiquitous applications is a difficult challenge that our approach attempts to address with the creation of the ApAM execution environment. Knowing that the execution environment is unpredictable, we believe that ubiquitous applications require a large amount of flexibility in choosing the components that compose the application, and that the composition should be automated. We propose an abstract and implicit description of the composition, where components and bindings are not explicitly described. This allows to incrementally building an application at runtime. The ApAM execution platform implements the mechanisms to achieve incremental composition and uses them to provide ubiquitous applications with the resilience and adaptability necessary to face unpredictable changes that originate in the execution environment. Resilience is a core property of our approach because it allows developers to easily build applications without the need to either describe nor predict the multiple adaptations required to support environmental disturbances which the applications will encounter. Our proposal offers the means of developing and executing applications with a high level of resilience in regards to their continuously evolving context. This is possible thanks to the mechanisms described in this dissertation that allow building and changing, at runtime, ubiquitous applications. These mechanisms are generic but can be extended or specialized in order to solve domain or application-specific issues.
|
59 |
Using a Multi-Method Approach for Evaluating Service Identification Methods in Service-Oriented Product LinesVALE, Tassio Ferreira 03 1900 (has links)
Submitted by Daniella Sodre (daniella.sodre@ufpe.br) on 2015-03-09T12:32:57Z
No. of bitstreams: 2
MSc Dissertation -Tassio Ferreira Vale.pdf: 3047313 bytes, checksum: 266f36d93884380708ea06bafe535341 (MD5)
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-09T12:32:57Z (GMT). No. of bitstreams: 2
MSc Dissertation -Tassio Ferreira Vale.pdf: 3047313 bytes, checksum: 266f36d93884380708ea06bafe535341 (MD5)
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Previous issue date: 2012-03 / A combinação de Linhas de Produto de Software (LPS) e Computação Orientada a
Serviços (COS) tem recebido atenção de pesquisadores e praticantes, já que uma área
é capaz de solucionar determinados problemas da outra. A junção dessas duas áreas é
chamada de Linha de Produto Orientada a Serviços (LPOS), e tem se mostrado uma área
de pesquisa emergente nos últimos anos.
No contexto da Computação Orientada a Serviços, identificação de serviços é uma das
primeiras atividades para modelagem de uma solução COS, e consiste na determinação
de serviços candidatos. Essa não é uma tarefa trivial, e os erros adquiridos durante a
identificação de um serviço pode propagar-se para as atividades subsequentes do processo
de desenvolvimento orientado a serviços.
Existem diversas propostas para identificação de serviços. Apesar da diversidade, não
existe um método de identificação de serviços capaz de adequar-se a diversos contextos e
necessidades. Considerando a heterogeneidade desses métodos, esta dissertação tem o
objetivo de verificar quais métodos podem ser aplicados em linhas de produto de software,
bem como as vantagens, desvantages e desafios existentes neste campo.
Esta pesquisa utilizou uma abordagem multi-métodos, que combina estudos primários
e secundários a fim de incrementar o corpo de conhecimento em determinada área baseada
nos achados de tal investigação. Desta forma, este trabalho utilizou um método secundário
(revisão sistemática) e dois métodos primários com o intuito de aumentar a confiabilidade
dessa pesquisa.
Além disso, foi realizada uma revisão da literatura a fim de coletar as abordagens
de identificação de serviços existentes, visando propor uma recomendação dos métodos
mais adequados considerando três cenários de LPS: top-down, bottom-up e hybrid. Esta
recomendação foi avaliada através de um estudo de caso com uma linha de produto
de sistemas médicos, usando dois metodos classificados no cenário o qual os sistemas
médicos encontram-se, top-down.
A principal contribuição dessa pesquisa é prover um instrumento que auxilie os
interessados em identificar serviços a escolher um método apropriado, levando em
consideração o cenário SPL a ser aplicado. Os resultados do estudo de caso mostram que
as abordagens de identificação de serviços podem ser aplicadas num contexto de LPS.
Além disso, este métodos facilitam a realização da atividade de identificação. / The combination of Software Product Line (SPL) and Service-Oriented Computing (SOC)
have started to receive attention by researchers and practitioners, since they can address
issues of each other. Putting these two areas together is called Service-Oriented Product
Lines Enginering (SOPLE), presenting itself as an emerging area in the last years.
In the Service-Oriented Computing, service identification is one of the first activities
in the modeling of a SOC solution, that consists of determining candidate services. This
is not a trivial task, and the errors made during the identification can propagate mistakes
to the next activities of the service-oriented development process.
There are several proposals addressing service identification for several contexts.
However, an unified method for identifying services has not yet been reached. Regarding
the heterogeneity of these methods, this dissertation aims to verify which methods can be
applied in the SPL context, the advantages, disadvantages and the existing challenges of
this field.
This research used a multi-method approach that combines primary and secondary
studies in order to increase the availability of empirical knowledge based on the findings
of the investigation. Thus, this work used one secondary method (systematic review) and
two primary methods (survey and case study) to address it.
Furthermore, it was performed a literature review in order to collect all existing
approaches of service identification, aiming to propose a set of decision models that
recommend the most suitable methods according to three SPL scenarios: bottom-up, topdown
and hybrid, onde decision model for each scenario. One of the decision models was
evaluated through a case study in a medical applications domain, using two approaches
classified in the decision model of the top-down scenario.
The main contribution of this research is to provide an instrument that can help the
service identification stakeholders to choose a suitable method, taking consideration of
their SPL scenarios. In addition, these systematic methods facilitate the application of
the identification activity. The case study results evaluated some service identification
approaches and presented evidence that the methods can be applied in SPL.
|
60 |
Mobila Applikationer : En utvärderande studie om hur mobila applikationer påverkar webbtjänsterRodling, Joakim, Tibblin, Jonas January 2011 (has links)
De teknologiska framstegen inom mobiltelefoni de senaste åren, har bidragit till att människor kan utföra sysslor oberoende av plats. För företag som tillhandahåller webbtjänster är mobila applikationer någonting som kan utnyttjas för att öka användning av deras tjänst. I uppsatsen undersöks om detta stämmer eller ej.För företag blir det viktigt hur en mobil applikation integreras mot den befintliga webbtjänsten. Det är dessutom relevant för företag att veta hur applikationen påverkar användningen av den initiala webbtjänsten.I studien utvecklas en mobil applikation från grunden för att se vilka potentiella problem företag kan stöta på vid utveckling av en mobil applikation. Intervjuer görs med företag som utvecklat mobila applikationer till befintliga webbtjänster, för att undersöka hur de upplevt effekterna av applikationen efter lansering.Resultaten visar att lansering av en mobil applikation ofta görs till mer än en typ av mobiltelefon. För att underlätta integration av mobila applikationer mot företagets tjänst, undersöks i uppsatsen vilka förutsättningar som krävs av det underliggande systemet. Med en flexibel arkitektur kan företaget vid vidare utveckling spara resurser.Vidare visar resultaten att tjänster i helhet ser ökad användning vid implementering av en mobil applikation. Funktioner i tjänster tenderar dessutom att delas upp mellan den mobila applikationen och webbtjänsten. / The technological advancements in the mobile technology industry have enabled people to perform tasks regardless of time or place. For companies that provide web services, mobile applications can boost service usage. In this thesis we examine if the usage of a service tends to increase in general, by using mobile applications.For companies it is important to know how mobile applications can be integrated with an existing web service. It is also relevant to know about the mobile applications’ effects on the usage of the initial web service.In this study a mobile application is developed from scratch in order to explore potential difficulties that companies can run into while developing a mobile application. Interviews are made with companies that provide web services to their customers, in order to get answers on how mobile applications have affected usage of their respective web services.Results show that the launch of a mobile application is often done towards more than one mobile platform. In the study, we investigate which requirements that has to be met to ease integration of a mobile application to an existing web service. By implementing flexible back-end system architecture, companies can save resources for future development. Furthermore, results show that services in general tend to see increased usage after a mobile application has been launched. Service-specific functionality also tends to get split up between the mobile application and the initial web service.
|
Page generated in 0.081 seconds