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

The purpose of this study is to present guidelines that can be followed when introducing Service-oriented architecture through the use of Web services. This guideline will be especially useful for organizations migrating from their existing legacy systems where the need also arises to consider the financial implications of such an investment whether it is worthwhile or not. The proposed implementation guide aims at increasing the chances of IT departments in organizations to ensure a successful integration of SOA into their system and secure strong financial commitment from the executive management. Service oriented architecture technology is a new concept, a new way of looking at a system which has emerged in the IT world and can be implemented by several methods of which Web services is one platform. Since it is a developing technology, organizations need to be cautious on how to implement this technology to obtain maximum benefits. Though a well-designed, service-oriented environment can simplify and streamline many aspects of information technology and business, achieving this state is not an easy task. Traditionally, management finds it very difficult to justify the considerable cost of modernization, let alone shouldering the risk without achieving some benefits in terms of business value. The study identifies some common best practices of implementing SOA and the use of Web services, steps to successfully migrate from legacy systems to componentized or service enabled systems. The study also identified how to present financial return on investment and business benefits to the management in order to secure the necessary funds. This master thesis is based on academic literature study, professional research journals and publications, interview with business organizations currently working on service oriented architecture. I present guidelines that can be of assistance to migrate from legacy systems to service-oriented architecture based on the analysis from comparing information sources mentioned above.

Active Documents is a technique for automating the handling and control of documents by making them a combination of service providers (mobile agents) and resources (compound documents) in the form of autonomous agents. The main focus of this solution is to provide an encapsulation of documents, including their data structures and related functionality, but also to enable documents to reflect upon themselves in respect of their computational environment, and take actions accordingly.

To support the difficult process of SOA adoption, SOA maturity models are published. In this thesis a literature analysis introduces the area of SOA maturity models and highlights benefits and criticism. As a result, the combined SOA maturity model (CSOAMM), a model to facilitate the interpretation and comparison of SOA maturity models, is proposed. CSOAMM is a model with 10 levels that describes SOA maturity by combining level characteristics of two recently published maturity models: SIMM and SOAMM. CSOAMM was created by a comparative analysis in combination with a relational content analysis. The model can be used for collaboration between companies and points out that a common understanding of SOA adoption exists.

För att dagens system och deras allt mer komplexa applikationer ska kunna integreras med varandra krävs det att de kommunicerar via tjänster. Denna tjänsteorienterade integration uppnås genom att man använder sig av Service Oriented Architecture (SOA) som bygger på löst kopplade tjänster som kommunicerar med varandra på ett standardiserat sätt. En viktig del i en integrationslösning är Enterprise Service Bus (ESB). I denna rapport kommer vi förklara grunderna i tjänsteorienterad integration och sedan fördjupa oss i ESB. Då ESB är ett luddigt begrepp ska vi på ett enkelt och lättbegripligt sätt ge vår syn på begreppet, samt dess fördelar och nackdelar. Vi kommer även att ge marknadens syn på ESB genom en enkätundersökning som innefattar både leverantörer, konsulter och kunder. / If today’s software systems and their complex applications shall be able to integrate with each other, they have to communicate through services. This service oriented integration can be accomplished by using Service Oriented Architecture (SOA) where all components are loosely coupled and communicate in a standardized way. An important part when building an integrated solution is the Enterprise Service Bus (ESB). In this report we will explain the basics of SOA and take a more detailed look at the world of ESB. The concept of ESB is not well defined and hence means different things to different people. We are going to present an interpretation of the ESB and its benefits and disadvantages. To find out what the market thinks about ESB we have been talking to producers, consultants and customers.

No description available.

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

Management of Virtual Organizations faces new challenges that traditional approaches cannot address. This research proposes a performance measurement framework for service oriented virtual organizations including a structural and a procedural component. The structural framework aligns the activities of partners in a virtual organization at three different layers. The first layer is designed for partners’ strategic alignment through coordination of the value creation network. In the second layer, performance dimensions of partners’ collaboration are defined and mapped to the service choreography model. The third layer focuses on assessing effectiveness and efficiency of partners’ domain specific services, which is designed based on ITIL V3 service level management guidelines. In order to consolidate the structural framework, these three layers are integrated using a method for extracting service choreography model and SLA aggregation patterns from the value network. The procedural framework, on the other side, defines the processes required to design the KPI structure, implement the solution, communicate the results, and derive improvements. We propose an implementation architecture that enables inter-organizational performance management in collaborative environments. Then, the IBM products for business process and performance management (IBM BPM, Business Monitor, and Cognos BI) are employed to implement the proposed architecture. The conceptual framework along with the implementation architecture provides an integrated solution for decentralized performance measurement without the need for a central authority. We demonstrate that the proposed solution enhances flexibility, scalability, and interoperability, and supports transparency of partners’ performance information at an agreed-upon level as a basis for mutual trust.

Service Oriented Virtual Organizations (SOVOs) business processes and services are subject to change to meet the internal and external requirements of the competitive, complex and rapidly changing environment they operate in. More practical and efficient ways of change management are needed to allow different partners to initiate changes to their business process and services in a faster and user-transparent manner. This thesis proposes a Change Management Framework for service oriented virtual organizations including a structural and a procedural framework. The structural framework categorizes changes in the SOVO into three layers of change; which include the value network layer, the collaborative process layer and the service providers’ layer, and identifies the impact of change on each layer. Furthermore, the structural framework identifies various triggers of changes which eventually lead to actions taken at the three layers. The change management procedural framework is derived from the ITIL V3, ECM and ECOLEAD best practices and recommendations, customized to fit the SOVO change requirements. It provides different components including the six layers for change processes, change control, change actors and related management processes. The change management procedural framework provides a sequence of steps and methods that the SOVO and its participated organizations can follow in initiating changes to their business processes or services. We design an implementation architecture and a prototype for building the change management console which enables the SOVO change management participants to initiate, assess, collaborate, monitor and authorize changes. The prototype is developed to realize and validate the change management process of change in the SOVO environment. We employ the various capabilities of the IBM Business Process Management (BPM) (including its recent Web 2.0 capabilities) to increase the collaboration between partners in the process of change. We demonstrate that the proposed solutions facilitate and enhance the process of change by effectively engaging the SOVO partners in the process of change.

This work deals with Service-Oriented Architecture (SOA) and its impact on SAP products. In the first part of the work we are outlining the development of information systems architectures, after that describing SOA architecture, its basic concept, benefits and risks, ways of implementing and other connections. In the next part we are introducing the SAP company and its big historic moments from the beginning till present. We are analyzing the impact of SOA on SAP product and introducing new solutions -- architectural concept Enterprise SOA and application and integration, service-oriented platform SAP NetWeaver. We are discussing its development and its future. In the last part we are demonstrating practically these new solutions.