O reúso de software enfrenta inúmeras barreiras gerenciais, técnicas e culturais na sua adoção, e a definição da estrutura de ativos reutilizáveis de software é uma dessas barreiras técnicas. Para solucionar isso, o Reusable Asset Specification (RAS) é um padrão de facto proposto pela OMG. Uma especificação como o RAS define e padroniza um modelo de ativos (assets) reutilizáveis, e é a base para a construção e para o uso de um repositório de ativos que apoia a reutilização de software. No entanto, para ser adotado na prática, o RAS necessita resolver suas lacunas através da sua extensão e da definição de informações complementares. Essas lacunas estão detalhadas neste trabalho. Solucionando estas lacunas, o RAS torna-se útil para auxiliar efetivamente na padronização do empacotamento dos ativos reutilizáveis e para guiar a estrutura do repositório de reutilização de software. Alguns trabalhos anteriores já responderam parcialmente essa questão, porém eles atendiam propósitos muito específicos, não possuíam uma ferramenta de apoio ou não haviam sido avaliados em contexto real de (re)uso. Esse trabalho propõe o Software Profile RAS (SW-RAS), uma extensão do Profile de componentes do RAS, que propõe soluções para diversas de suas lacunas, incluindo informações úteis e artefatos relevantes apontados na literatura, baseados em outros modelos de ativos reutilizáveis, em outras extensões do RAS e na experiência do processo de reúso no desenvolvimento de software. Particularmente, o SW-RAS estende as categorias de classificação, solução, uso e ativos relacionados, cujos detalhes estão descritos no texto. Visando à experimentação da proposta através de um estudo de caso, desenvolveu-se o Lavoi, um repositório de ativos reutilizáveis baseado no SW-RAS, que foi avaliado num ambiente real de reutilização e desenvolvimento de software de uma grande companhia pública de TI. Uma descrição deste processo de avaliação em um contexto real é também apresentada neste trabalho. A principal contribuição desta dissertação é a proposta, a avaliação e a consolidação de uma extensão do RAS que atende várias de suas lacunas e é suportada por uma ferramenta de software livre. / The software reuse faces numerous managerial, technical and cultural barriers in its adoption, and the definition of the structure of reusable software assets is one of these technical barriers. To solve this, the Reusable Asset Specification (RAS) is a de facto standard proposed by OMG. A specification such as the RAS defines and standardizes a reusable asset model, and it is the foundation for the construction and for the use of an asset repository that supports the software reuse. However, for being adopted in the practice, the RAS needs to solve its lacks through its extension and the definition of complementary information. These lacks are detailed in this work. Solving these lacks, the RAS becomes useful to help effectively in the standardization of packaging reusable assets and to guide the structure of the software reuse repository. Some previous works have already partially answered this question, but they attended very specific purposes, did not have a support tool or have not been evaluated in a real context of (re)use. This work proposes the Software Profile RAS (SW-RAS), an extension of the component Profile of RAS, which proposes solutions for its various lacks, including useful information and relevant artifacts pointed out in the literature, based on other reusable asset models, on other RAS extensions and on the experience in the reuse process at software development. Particularly, the SW-RAS extends the categories of classification, solution, usage and related assets, whose details are described in the text. Aiming at the experimentation of the proposal through a case study, the Lavoi was developed, a reusable asset repository based on the SW-RAS, which is was evaluated in a real environment of reuse and software development of a large public IT company. A description of this evaluation process in real context is also presented in this work. The main contribution of this dissertation is the proposal, the evaluation and the consolidation of an extension of RAS that addresses several of its lacks and is supported by a free software tool.

A engenharia de software tem buscado, nas últimas décadas, assemelhar-se a outras disciplinas de engenharia, introduzindo métodos, técnicas e ferramentas que possibilitem a melhoria da produtividade e qualidade no desenvolvimento de software em ordem de grandeza similar à alcançada pela indústria de manufatura. Uma das abordagens mais bem sucedidas neste sentido tem sido o emprego das práticas de reuso sistematizado de software, como o desenvolvimento baseado em componentes e, em especial, as linhas de produtos de software ou engenharia de família de produtos. No Brasil, um dos segmentos que mais produz e consome software é o setor financeiro, uma vez que todos os seus produtos e serviços são entregues através da tecnologia da informação. Por este motivo, torna-se fundamental a compreensão de como acontecem os processos de reuso de software neste segmento e como estes contribuem para o sucesso dos projetos. Esta pesquisa apresenta o mapeamento do cenário de reuso de software no setor financeiro no Brasil, baseado em estudos de caso conduzidos em cinco, dos dez maiores bancos instalados no país. / During last decades, Software Engineering has been aiming at be more disciplined as other engineering disciplines, by introducing methods, techniques and tools that provide productivity and quality improvement in the same levels reached by manufacturing industries. One of the most successful approaches towards this goal has been the use of systematic software reuse practices, such as component based development and, specially, software product lines or product family engineering. In Brazil, one of the most active sectors in consuming and producing software products is the financial sector, once all of its products and services are delivered through Information Technology. This is the reason why is so important to understand how software reuse processes occurs in this sector and how do they contribute to projects success. This research presents scenario of software reuse in the financial sector in Brazil, based on case research conducted in five of the ten largest banks installed in the country.

Submitted by Filipe dos Santos (fsantos@pucsp.br) on 2017-09-04T18:05:32Z No. of bitstreams: 1 Marcela Cristina Pereira.pdf: 1085475 bytes, checksum: 427d918ecf2e85cca7f74cca6a5f5ec6 (MD5) / Made available in DSpace on 2017-09-04T18:05:32Z (GMT). No. of bitstreams: 1 Marcela Cristina Pereira.pdf: 1085475 bytes, checksum: 427d918ecf2e85cca7f74cca6a5f5ec6 (MD5) Previous issue date: 2017-09-24 / Many softwares, which are using by the companies, have the objective to support their business activities. This kind of support happens by means of processes controls and/or accomplishment of business processes. The software used in the companies executes humans being activities and it stays in the same environment of the business process. However, the environment is not static, the software application needs change according the company needs. The software changings are necessary by his useful life and for by his degradation too, because the business process representation inside the software becomes more complex. The complexity is one of the limitation to change the software without high cost and risks for organization until the impossibility of the his maintenance. There are many approaches to extend the use time of software until his replacing in the company. This research uses concepts like evolution, modernization and degradation of software with the objective to discuss and offer indicators metrics based in needs of business processes. The objective is identify which moment the company should makes plan to do the modernization approaches for extend the time of software useful / Muitos sistemas de software utilizados pelas empresas tem como objetivo apoiar suas atividades. Este apoio pode acontecer através de controles e/ou realização dos processos de negócio da empresa. Este tipo de software mecaniza atividades humanas e está inserido no meio ao qual modela. Como o ambiente organizacional é mutável, a aplicação precisa ser alterada de acordo com as novas necessidades da empresa. Porém, estas alterações são responsáveis pela degradação do software porque o torna cada vez mais complexo. A complexidade é limitadora para que novas modificações sejam realizadas sem existirem custos e riscos elevados para a organização até que seja inviável manter o sistema de software. Existem abordagens, chamadas de modernização, que podem prolongar o tempo de uso do software até sua substituição. A pesquisa utiliza os conceitos de evolução, degradação e modernização de software para propor indicadores baseados nas necessidades do processo de negócio atendido pelo software para identificar o momento que a organização precisa realizar ações para prolongar o tempo de uso da aplicação

Web-based user interfaces are used widely. They are replacing conventional desktop-based user interfaces in many domains and are emerging as front-ends for online businesses. The technologies for web user interfaces have advanced considerably to support high-quality user interfaces. However, the usability of web interfaces continues to be an issue. We still encounter web forms where basic interactive features are missing or work unexpectedly. User interface is a costly and error-prone area of software construction. This is particularly true for web user interfaces. They are typically implemented with fewer reusable components on programmers' toolboxes than conventional user interfaces built using user interface frameworks such as Windows Forms, Cocoa, and Qt. Consequently, web interface programmers tend to struggle with low productivity, or low quality and high defect rates. This thesis focuses on property models, a declarative approach to programming user interfaces. In this approach, common user interface behaviors are automatically derived from the specifications of the data manipulated by user interfaces. The approach aims to reuse user interface algorithms that are common across interfaces and allow the programmers to focus on application-specific concerns. This thesis work is a part of project "hotdrink," a JavaScript implementation of the property model system, which has the goal of providing the benefits of property models for web interfaces. This thesis builds on previous work on property models, and adds to it three reusable help and convenience features, which can be especially useful for web forms. In particular, this thesis describes the generic mechanisms of the following user interface features: (1) validating data coming from a user and presenting useful messages that help the user to fix errors, (2) controlling the flow of data through "pinning," and (3) canceling the user's previous actions through undoing. The main contributions of the thesis are the mechanisms and the software architecture that enable implementing these behaviors in a reusable manner. This thesis also presents several examples to illustrate the benefits of the proposed mechanisms.

Software reuse is prevalent in software development. It is not uncommon that one software product may depend on numerous libraries/products in order to build, install, or run. Software reuse is difficult due to the complex interdependency relationships between software packages. In this work, we presented four approaches to retrieve such dependency information, each technique focuses on retrieving software dependency from a specific source, including source code, build scripts, binary files, and Debian spec. The presented techniques were realized by a prototype tool, DEx, which is applied to a large collection of Debian projects in a comprehensive evaluation. Through the comprehensive analysis, we evaluate the presented techniques, and compare them from various aspects. / Graduate

A engenharia de software tem buscado, nas últimas décadas, assemelhar-se a outras disciplinas de engenharia, introduzindo métodos, técnicas e ferramentas que possibilitem a melhoria da produtividade e qualidade no desenvolvimento de software em ordem de grandeza similar à alcançada pela indústria de manufatura. Uma das abordagens mais bem sucedidas neste sentido tem sido o emprego das práticas de reuso sistematizado de software, como o desenvolvimento baseado em componentes e, em especial, as linhas de produtos de software ou engenharia de família de produtos. No Brasil, um dos segmentos que mais produz e consome software é o setor financeiro, uma vez que todos os seus produtos e serviços são entregues através da tecnologia da informação. Por este motivo, torna-se fundamental a compreensão de como acontecem os processos de reuso de software neste segmento e como estes contribuem para o sucesso dos projetos. Esta pesquisa apresenta o mapeamento do cenário de reuso de software no setor financeiro no Brasil, baseado em estudos de caso conduzidos em cinco, dos dez maiores bancos instalados no país. / During last decades, Software Engineering has been aiming at be more disciplined as other engineering disciplines, by introducing methods, techniques and tools that provide productivity and quality improvement in the same levels reached by manufacturing industries. One of the most successful approaches towards this goal has been the use of systematic software reuse practices, such as component based development and, specially, software product lines or product family engineering. In Brazil, one of the most active sectors in consuming and producing software products is the financial sector, once all of its products and services are delivered through Information Technology. This is the reason why is so important to understand how software reuse processes occurs in this sector and how do they contribute to projects success. This research presents scenario of software reuse in the financial sector in Brazil, based on case research conducted in five of the ten largest banks installed in the country.

No description available.

This research models the effects of software reuse on object-oriented software development, in particular, the reuse of C++ classes. Two types of reuse (with and without modification) are compared. The common traits of programmers who tend to reuse are identified, and some object-oriented software metrics are correlated with the inherent reusability of a C++ class. These issues are important because software reuse has been shown to increase productivity within the software development process. This research effort describes three experiments. The first characterizes the effects of reusing C++ classes on object-oriented software development using nine development process indicators. The second experiment uses ten similar process indicators to differentiate the effects of writing C++ classes from scratch versus reusing them without modification versus inheriting new classes from existing ones. The last experiment correlates some object-oriented metrics with the expert opinions of the reusability of C++ classes. This research has shown that the black box reuse (reuse without modification) of C++ classes is beneficial to object-oriented software development in many ways. Development time is reduced and system reliability increases. For abstract data type C++ classes, a set of fifteen skills and experiences are shown to be prominent in frequent class reusers. Lastly, a set of object-oriented metrics is used to predict C++ class reusability. All of these results can be used to increase programmer productivity when developing C++ software systems. / Ph. D.

One of the problem that plagues Human-Computer Interaction (HCI) software is its development cost. Many software companies forego the usability engineering aspect of their projects due to the time required to design and test user interfaces. Unfortunately, there is no "silver bullet" for user interface design and implementation because they are inherently difficult tasks. As computers are moving off the desktop, the greatest challenge for designers will be integrating these systems seamlessly into our everyday lives. The potential for reuse in user interfaces lies in reducing the time and effort required for this task, without sacrificing design quality. In this work we begin with an iterative development cycle for a claims library based on prominent literature within the HCI and software engineering fields. We constructed the Claims Library to be a repository of potentially reusable notification system claims. We examine the library through theoretical and practical perspectives. The theoretical perspective reveals tradeoffs in the initial implementation that relate to Krueger's taxonomy of reuse. The practical perspective stems from experience in designing and conducting usability testing for an in-vehicle input device using the Claims Library. While valuable, these examinations did not provide a distinct method of improving the library. Expecting to uncover a specific diagnosis for the problems in the library, it was unclear how they should be approached with further development efforts. With this realization, we saw that a more important and immediate contribution would not be another iteration of the Claims Library design. Rather, a clarification of the underlying theory that would better inform future systems development seemed a more urgent and worthy use of our experience. This clarification would need to have several characteristics to include: composed of a staged or prioritized architecture, represents an ideal model grounded in literature, and possesses intermediate development objectives and assessment points. As a solution, we propose the Claims Library Capability Maturity Model (CL-CMM), based on the theoretical deficiencies that should guide development of a claims library, as noted in the two evaluations. This thesis delivers a five-stage model to include process areas, goals, and practices that address larger threads of concern. Our capability maturity model is patterned after models in software engineering and human resource management. We include a full description of each stage, a gap analysis method of appraisal, and an example of its use. Several directions for future work are noted that are necessary to continue development and validation of the model. / Master of Science

Previous research shows that software reuse can have a positive impact on software development economics, and that the adoption of a specific open source license can influence how a software product is received by users and programmers. This study attempts to bridge these two research areas by examining how the adoption of an open source license affects software reuse. Two reuse metrics were applied to 9,570 software packages contained in the Fedora Linux software repository. Each package was evaluated to determine how many external components it reuses, as well as how many times it is reused by other software packages. This data was divided into subsets according to license type and software category. The study found that, in general, (1) software released under a restrictive license reuse more external components than software released under a permissive license, and (2) that software released under a permissive license is more likely to be reused than software released under a restrictive license. However, there are exceptions to these conclusions, as the effect of license choice on reuse varies by software category. / Master of Science