Made available in DSpace on 2016-12-23T14:33:43Z (GMT). No. of bitstreams: 1 Dissertacao Lucas de Oliveira Arantes.pdf: 2264655 bytes, checksum: 67cdb0cba1670e3d591848c2ebb8e7fc (MD5) Previous issue date: 2010-08-27 / Documentos são mecanismos importantes para registro e disseminação de conhecimento e comunicação entre seres humanos. Organizações de software contam com esse mecanismo para a realização de projetos. Essas organizações, quando maduras, definem uma série de modelos de documento de software para apoiar o processo de documentação. Adicionalmente, as mesmas contam com processos e mecanismos para registrar o histórico evolutivo dos documentos envolvidos em um projeto. A quantidade de documentos gerados durante o ciclo de vida de um projeto de software pode ser consideravelmente grande. Apesar dos sistemas de controle de versão facilitarem o controle da evolução dos documentos, os mesmos não são capazes de apoiar a integração e a visualização objetiva de suas informações. Somado a isso, documentos são normalmente tratados como um mero conjunto de caracteres com estilos de formatação voltados para renderização em ferramentas de edição de texto (em inglês, document authoring tool). Neste contexto, a adição de metadados baseados em ontologias de domínio apoia o desenvolvimento de documentos semânticos que podem ser utilizados para contornar esse cenário. O processo de anotação semântica de documentos, quando feito de forma manual, é enfadonho e suscetível a erros. O uso de modelos de documento com anotações semânticas é uma opção viável para a automatização parcial desse processo. Assim, a união de mecanismos de integração contidos em sistemas de controle de versão e modelos de documento de software semanticamente anotados é um meio potencial de apoiar a integração de informações e, por conseguinte, a execução de projetos de software. Esta dissertação trata da utilização de modelos de documento de software anotados semanticamente e mecanismos de controle de versão para registrar a evolução do conteúdo semântico existente em documentos gerados e para prover serviços de integração e visibilidade dos dados relativos aos documentos. Para tal, uma Plataforma para Gerenciamento de Documentos Semânticos é definida / Documents are important mechanisms to register and disseminate knowledge and allow communication between human beings. Software Organizations use this mechanism to conduct projects. When these organizations reach a certain level of maturity they tend to use software document models in order to support the documentation process. Additionally, organizations count on processes and mechanisms to track the evolution of documents involved in a project. The amount of documents produced during a software project lifecycle can be considerably large. Despite the fact that version control systems support document centralization they are not capable of support information integration and visibility. Summing up, documents are treated as a set of characters tied with formatting styles because their primary goal is to be well rendered on a document authoring tool. In this context, adding domain ontology based metadata can help developing semantic documents, which, in turn, can help overcoming this scenario. Manual Semantic Annotation is notably dull and error prone. Combining document models semantic annotation is a viable option in order to achieve the annotation process automatization. Thus, uniting integration mechanisms provided by version control systems and software document models semantically annotated is a potential way of supporting information integration and, therefore, executing software projects. This work treats the use of software document models annotated semantically and version control mechanisms to track and register the evolution of a semantic document content (instantiated from a semantic model) and the provision of data visibility and integration services. In this sense, a Platform for Managing Semantic Documents is defined

Indiana University-Purdue University Indianapolis (IUPUI) / A Laboratory Information Management Systems (LIMS) is designed to manage laboratory processes and data. It has the ability to extend the core functionality of the LIMS through configuration tools and add-on modules to support the implementation of complex laboratory workflows. The purpose of this project is to demonstrate how laboratory data and processes from a complex workflow can be implemented using a LIMS. Genomic samples have become an important part of the drug development process due to advances in molecular testing technology. This technology evaluates genomic material for disease markers and provides efficient, cost-effective, and accurate results for a growing number of clinical indications. The preparation of the genomic samples for evaluation requires a complex laboratory process called the precision aliquotting workflow. The precision aliquotting workflow processes genomic samples into precisely created aliquots for analysis. The workflow is defined by a set of aliquotting scheme attributes that are executed based on scheme specific rules logic. The aliquotting scheme defines the attributes of each aliquot based on the achieved sample recovery of the genomic sample. The scheme rules logic executes the creation of the aliquots based on the scheme definitions. LabWare LIMS is a Windows® based open architecture system that manages laboratory data and workflow processes. A LabWare LIMS model was developed to implement the precision aliquotting workflow using a combination of core functionality and configured code.

The complex business applications are increasingly offered as services over the Internet, so-called software-as-a-Service (SaaS) applications. The SAP Netweaver Cloud offers an OSGI-based open platform, which enables multi-tenant SaaS applications to run in the cloud. A multi-tenant SaaS application is designed so that an application instance is used by several customers and their users. As different customers have different requirements for functionality and quality of the application, the application instance must be configurable. Therefore, it must be able to add new configurations into a multi-tenant SaaS application at run-time. In this thesis, we proposed concepts of a configuration management, which are used for managing and creating client configurations of cloud applications. The concepts are implemented in a tool that is based on Eclipse and extended feature models. In addition, we evaluate our concepts and the applicability of the developed solution in the SAP Netwaver Cloud by using a cloud application as a concrete case example.:List of Figures i List of Tables iii 1 Introduction 1 1.1 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2 The Structure of This Document . . . . . . . . . . . . . . . . . 2 2 Background 5 2.1 Cloud Computing . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Software Product Line Engineering . . . . . . . . . . . . . . . . 7 2.3 Role Based Access Control . . . . . . . . . . . . . . . . . . . . . 10 2.4 Staged Con guration . . . . . . . . . . . . . . . . . . . . . . . . 12 2.5 Work ow Modeling . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.5.1 Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.5.2 Work ow Modeling Languages . . . . . . . . . . . . . . . 16 2.5.3 Adaptive Work ow . . . . . . . . . . . . . . . . . . . . . 17 2.5.4 Adaptation Patterns . . . . . . . . . . . . . . . . . . . . 17 2.6 Graph Transformation . . . . . . . . . . . . . . . . . . . . . . . 18 2.7 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3 Analysis 23 3.1 Illustrative Example . . . . . . . . . . . . . . . . . . . . . . . . 23 3.1.1 Domain and Exiting Platform . . . . . . . . . . . . . . . 24 3.1.2 Yard Management System as a SaaS Application . . . . 28 3.2 Requirements Identi cation . . . . . . . . . . . . . . . . . . . . 28 4 Concept 31 4.1 Con guration Management Speci cation . . . . . . . . . . . . . 31 4.1.1 Variability Modeling . . . . . . . . . . . . . . . . . . . . 32 4.1.2 Stakeholder Views Modeling . . . . . . . . . . . . . . . . 34 4.1.3 Con guration Work ow Modeling . . . . . . . . . . . . . 36 4.2 Con guration Work ow Adaptations . . . . . . . . . . . . . . . 41 4.3 Mapping between Problem Space and Solution Space . . . . . . 47 4.4 Con guration Process Simulation . . . . . . . . . . . . . . . . . 50 5 Implementation 53 5.1 Con guration Speci cation . . . . . . . . . . . . . . . . . . . . . 54 5.1.1 Extended Feature Model Speci cation . . . . . . . . . . 55 5.1.2 View Model Speci cation . . . . . . . . . . . . . . . . . . 56 5.1.3 Con guration Work ow Model Speci cation . . . . . . . 57 5.2 Graph Transformation Rules . . . . . . . . . . . . . . . . . . . . 62 5.3 Mapping Realization . . . . . . . . . . . . . . . . . . . . . . . . 65 5.4 Con guration Management Tooling . . . . . . . . . . . . . . . . 67 5.5 Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6 Conclusions and Future Work 77 6.1 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.2 Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Bibliography i