Orientadores: Mario Jino, Jacques Wainer / Dissertação (mestrado profissional) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-08T22:10:35Z (GMT). No. of bitstreams: 1 Lima_EwertonRodriguesde_M.pdf: 987163 bytes, checksum: e7f810e7d978629a3fdf409175cc29c9 (MD5) Previous issue date: 2006 / Resumo: Este trabalho trata de estimação e medição de esforço necessário para aplicação de Gerência de Configuração de Software (GCS) nos projetos de uma organização específica, com os objetivos de: 1) tornar a equipe de GCS capaz de relatar o esforço mensal dos analistas em atividades de GCS, provendo visibilidade da demanda gerada pelos projetos; 2) estimar o esforço necessário para aplicar GCS em novos projetos, permitindo adequar a força de trabalho à nova demanda. A abordagem para medição do esforço consistiu em dois passos: 1) identificação das atividades envolvidas na aplicação de GCS para as quais faz sentido registrar esforço; 2) desenvolvimento de uma ferramenta para facilitar o registro de todas as atividades realizadas pela equipe. Os dados acumulados pela ferramenta foram utilizados para acompanhar, analisar e relatar o esforço mensal de cada analista e para identificar os fatores influenciadores de esforço demandado pelos projetos, permitindo a definição de parâmetros e um método de estimação. Para sistematizar o uso desse método outra ferramenta foi desenvolvida; essa última identifica as características dos novos projetos, sua relação com os fatores influenciadores de esforço e estima o número de horas mensais requeridas na aplicação de GCS, com base em dados de esforço de projetos já finalizados. O método de estimação de esforço foi aplicado em projetos já iniciados, para os quais o consumo mensal de esforço é conhecido e cujos dados não foram considerados na calibração da ferramenta. Os resultados obtidos são satisfatórios e as duas ferramentas são atualmente utilizadas pela organização / Abstract: This work deals with estimation and measurement of the effort necessary to apply Software Configuration Management (SCM) to a particular organization¿s projects, aiming to: make the SCM team able to report the monthly effort of analysts in performing SCM activities, providing visibility of the demand generated by the projects; 2) estimate the effort necessary to apply SCM to new projects, enabling to adequate the work force to the new demand. The approach for effort measurement consisted of two steps: 1) identification of the activities in SCM for which it makes sense to record effort; 2) development of a tool to record all activities performed by SCM team. Data acquired by the tool were used to track, analyze and report the monthly effort of each analyst and to identify the factors which affect the effort required by the projects, enabling definition of parameters and of an estimation method. To systematize this method¿s usage another tool was developed; it identifies the new project¿s characteristics, their relationship with the factors which affect the effort and estimates the number of hours required monthly in the application of SCM, based on finished projects data. The estimation method has been applied to current projects, for which the monthly consumed effort is known and whose data were not used for tool calibration. The obtained results are satisfactory and both tools are currently being used in the organization / Mestrado / Engenharia de Computação / Mestre em Engenharia de Computação

Software prototyping is considered to be one of the most important tools that are used by software engineersnowadays to be able to understand the customer’s requirements, and develop software products that are efficient,reliable, and acceptable economically. Software engineers can choose any of the available prototyping approaches tobe used, based on the software that they intend to develop and how fast they would like to go during the softwaredevelopment. But generally speaking all prototyping approaches are aimed to help the engineers to understand thecustomer’s true needs, examine different software solutions and quality aspect, verification activities…etc, that mightaffect the quality of the software underdevelopment, as well as avoiding any potential development risks.A combination of several prototyping approaches, and brainstorming techniques which have fulfilled the aim of theknowledge extraction approach, have resulted in developing a prototyping approach that the engineers will use todevelop one and only one throwaway prototype to extract more knowledge than expected, in order to improve thequality of the software underdevelopment by spending more time studying it from different points of view.The knowledge extraction approach, then, was applied to the developed prototyping approach in which thedeveloped model was treated as software prototype, in order to gain more knowledge out of it. This activity hasresulted in several points of view, and improvements that were implemented to the developed model and as a resultAgile Prototyping AP, was developed. AP integrated more development approaches to the first developedprototyping model, such as: agile, documentation, software configuration management, and fractional factorialdesign, in which the main aim of developing one, and only one prototype, to help the engineers gaining moreknowledge, and reducing effort, time, and cost of development was accomplished but still developing softwareproducts with satisfying quality is done by developing an evolutionary prototyping and building throwawayprototypes on top of it.

The Unified Modeling Language (UML) became part of the curriculum in the Department of Computer Science at California State University, San Bernardino (CSUSB) in September 1997. The intent was to integrate the object-oriented paradigm in the undergraduate courses. Subsequently, this use has shifted to the graduate level. The purpose of this thesis is: 1) to determine what the students know about UML, 2) to reveal if the students were using UML, 3) to clarify how students use the UML.

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.

Introdução – A área de pesquisa de estimativa de esforço de software busca melhorar a acurácia das estimativas de projetos e atividades de software. Objetivo – Este trabalho descreve o desenvolvimento e uso de uma ferramenta web de coleta de dados gerados durante a execução da técnica de estimativa Planning Poker e a análise dos dados coletados para investigação do impacto da revisão de dados históricos de esforço. Método – Foram realizadas estimativas com e sem revisão, em experimentos com alunos de computação da Universidade Tecnológica Federal do Paraná, coletando os dados relacionados à tomada de decisão em uma ferramenta web. Após isso, foi analisado o impacto causado pelas revisões na acurácia da estimativa de esforço de software utilizando Planning Poker. Resultados Obtidos – Foi analisado o comportamento de 14 grupos de estimativas. Dentre esses times, 8 deles tiveram uma melhora na acurácia maior que 50% das estimativas analisadas. Em 3 deles, a soma das estimativas que tiveram melhora com as estimativas que permaneceram estáveis ultrapassou os 50%. Em apenas 3 deles, as estimativas tiveram redução de acurácia maior que 50%. Conclusões – A Revisão de Atividades Executadas, utilizando Planning Poker, melhorou a estimativa de esforço na maioria dos casos analisados, podendo ser um importante método para aprimorar o processo de desenvolvimento de software. / Abstract – Background – The software effort estimation research area aims to improve the accuracy of this estimation in software projects and activities. Aims – This study describes the development and usage of a web application tocollect data generated from the Planning Poker estimation process and the analysis of the collected data to investigate the impact of revising previous estimates when conducting similar estimates in a Planning Poker context. Method – Software activities were estimated by Universidade Tecnológica Federal do Paraná (UTFPR) computer students, using Planning Poker, with and without revising previous similar activities, storing data regarding the decision-making process. And the collected data was used to investigate the impact that revising similar executed activities have in the software effort estimates' accuracy.Obtained Results – The UTFPR computer students were divided into 14 groups. Eight of them showed accuracy increase in more than half of their estimates. Three of them had almost the same accuracy in more than half of their estimates. And only three of them had loss of accuracy in more than half of their estimates. Conclusion – Reviewing the similar executed software activities, when using Planning Poker, led to more accurate software estimates in most cases, and, because of that, can improve the software development process.

Introdução – A área de pesquisa de estimativa de esforço de software busca melhorar a acurácia das estimativas de projetos e atividades de software. Objetivo – Este trabalho descreve o desenvolvimento e uso de uma ferramenta web de coleta de dados gerados durante a execução da técnica de estimativa Planning Poker e a análise dos dados coletados para investigação do impacto da revisão de dados históricos de esforço. Método – Foram realizadas estimativas com e sem revisão, em experimentos com alunos de computação da Universidade Tecnológica Federal do Paraná, coletando os dados relacionados à tomada de decisão em uma ferramenta web. Após isso, foi analisado o impacto causado pelas revisões na acurácia da estimativa de esforço de software utilizando Planning Poker. Resultados Obtidos – Foi analisado o comportamento de 14 grupos de estimativas. Dentre esses times, 8 deles tiveram uma melhora na acurácia maior que 50% das estimativas analisadas. Em 3 deles, a soma das estimativas que tiveram melhora com as estimativas que permaneceram estáveis ultrapassou os 50%. Em apenas 3 deles, as estimativas tiveram redução de acurácia maior que 50%. Conclusões – A Revisão de Atividades Executadas, utilizando Planning Poker, melhorou a estimativa de esforço na maioria dos casos analisados, podendo ser um importante método para aprimorar o processo de desenvolvimento de software. / Abstract – Background – The software effort estimation research area aims to improve the accuracy of this estimation in software projects and activities. Aims – This study describes the development and usage of a web application tocollect data generated from the Planning Poker estimation process and the analysis of the collected data to investigate the impact of revising previous estimates when conducting similar estimates in a Planning Poker context. Method – Software activities were estimated by Universidade Tecnológica Federal do Paraná (UTFPR) computer students, using Planning Poker, with and without revising previous similar activities, storing data regarding the decision-making process. And the collected data was used to investigate the impact that revising similar executed activities have in the software effort estimates' accuracy.Obtained Results – The UTFPR computer students were divided into 14 groups. Eight of them showed accuracy increase in more than half of their estimates. Three of them had almost the same accuracy in more than half of their estimates. And only three of them had loss of accuracy in more than half of their estimates. Conclusion – Reviewing the similar executed software activities, when using Planning Poker, led to more accurate software estimates in most cases, and, because of that, can improve the software development process.

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