Thesis (Ph.D)--Computing, Georgia Institute of Technology, 2010. / Committee Chair: Yannis Smaragdakis; Committee Member: Oege de Moor; Committee Member: Richard LeBlanc; Committee Member: Santosh Pande; Committee Member: Spencer Rugaber. Part of the SMARTech Electronic Thesis and Dissertation Collection.

Orientador: Cecilia Mary Fischer Rubira / Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-09T23:14:42Z (GMT). No. of bitstreams: 1 Moronte_TiagoCesar_M.pdf: 2563765 bytes, checksum: c66bedbad911b6e9fe990bc2f1748ec0 (MD5) Previous issue date: 2007 / Resumo: Os paradigmas de arquitetura de software e de desenvolvimento baseado em componentes (DBC) são abordagens complementares para o desenvolvimento de sistemas de software. O DBC se baseia na construção de sistemas através da integração de componentes de software reutilizáveis. A arquitetura de software auxilia na forma como estes componentes são integrados levando em consideração atributos de qualidade, tais como confiabilidade e distribuição. Entretanto, observa-se atualmente a falta de consenso entre os conceitos, termos e definições utilizados nas abordagens de arquitetura de software e de DBC, dificultando a integração das respectivas técnicas e ferramentas. As ferramentas e ambientes atuais para descrição de arquiteturas de software não apóiam todas as fases dos processos de DBC, normalmente não geram implementações das arquiteturas e não implementam conceitos importantes de DBC, tais como especificações de interfaces providas e requeridas. Por outro lado, ferramentas e ambientes DBC atuais, em geral, são baseados em modelagem UML e não englobam todos os conceitos presentes em arquitetura de software, tais como estilos arquiteturais e uso explícito de conectores. Este trabalho apresenta uma infra-estrutura de software para construção de arquiteturas de software baseadas em componentes, composta por um conjunto de ferramentas que estentem o ambiente integrado de desenvolvimento Eclipse. As ferramentas foram construídas sobre um metamodelo conceitual integrado para arquitetura de software e DBC, que define e relaciona os conceitos existentes nas duas abordagens. Esta infra- estrutura faz parte do ambiente Bellatrix, um ambiente integrado de desenvolvimento que oferece apoio ao DBC com ênfase na arquitetura de software. As ferramentas apóiam a construção de arquiteturas de software baseadas em componentes desde a sua especificação, passando pelo seu projeto até a sua materialização em forma de código. O modelo de componentes utilizado é o COSMOS, um modelo de implementação de componentes que materializa os conceitos de arquiteturas de software em uma linguagem de programação. No caso do ambiente Bellatrix, a linguagem de programação adotada é Java / Abstract: Component-based development (CBD) and architecture-centric development are two complementary approaches for developing software systems. CBD is based on the construction of systems using the integration of reusable software components. Software architecture centric development complements the CBD paradigm because it is responsible for the component integration, achieving the final system's desired quality requirements, such as dependability and distribution. However, there is a lack of consensus among the concepts, terms, and definitions used in the software architecture and CBD paradigms, hindering the integration of techniques and tools. Existing software architecture environments and tools do not support all the phases involved in CBD process, normally do not generate architecture implementations and do not implement the main CBD concepts, e.g. specification of provided and required interfaces. CBD tools and environments, in general, use UML modeling and do not cover the main software architecture concepts, e.g. architectural styles and architectural connectors. In this work, we propose a software infrastructure to construct component-based software architectures. It has been built as a set of tools that extend the Eclipse integrated development environment. These tools were constructed based on an integrated conceptual metamodel for software architectures and CBD. This metamodel defines and relates the main concepts of the two paradigms. The infrastructure is included in the Bellatix environment, an integrated development environment that supports CBD with emphasis on software architecture. The tools support the construction of component-based software architectures since the specification phase, through the design, until its materialization in code. The component model used is COSMOS, a component implementation model that materializes the elements of a software architecture using the concepts available in object-oriented programming languages. In Bellatix environment, the adopted programming language is Java / Mestrado / Sistemas de Informação / Mestre em Ciência da Computação

Orientador: Ana Cervigni Guerra / Dissertação (mestrado profissional) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-05T06:59:49Z (GMT). No. of bitstreams: 1 Sanches_MauricioGruhn_M.pdf: 621110 bytes, checksum: b9818d8d518e03c417515cfe58fe3990 (MD5) Previous issue date: 2005 / Resumo: No mundo globalizado de hoje, a necessidade de se prover sistemas para o gerenciamento do grande volume de informações gerado a cada dia torna imperativa a busca contínua por novas práticas e formas de desenvolvimento de software para a manipulação dessas informações. Isso está vinculado também à necessidade de se conseguir ganhos de qualidade, produtividade e redução de custos em tais desenvolvimentos, pois esses são fatores fundamentais no sucesso do negócio de empresas ligadas à tecnologia da informação. Nesse cenário, o reuso de componentes no processo de desenvolvimento de software vem a exercer um papel importante na concretização desses objetivos. Este trabalho apresenta os conceitos envolvidos no contexto de um processo de desenvolvimento de software baseado em componentes reusáveis. São apresentadas as diferentes formas de reuso, o conceito de componentes reusáveis e as formas que esses componentes podem assumir dentro de um domínio de aplicação. Componentes possuem características diferentes, podem ser originados a partir de diversas fontes e carregam detalhes importantes que devem ser considerados durante a sua documentação. Todos esses aspectos influenciam o grau de reuso de um componente dentro do projeto ou organização. São apresentadas algumas tecnologias que promovem a aplicação do reuso de componentes e os conceitos envolvidos na definição, gerenciamento e implantação de repositórios de componentes reusáveis, fundamentais na consolidação do processo de reuso. Novos papéis e responsabilidades envolvidos no processo de reuso são apresentados, além de exemplos de métricas a serem utilizadas com o intuito de auxiliar a medição dos benefícios proporcionados pelo reuso dentro de um processo já consolidado. O resultado desse trabalho é uma análise crítica em relação aos benefícios do reuso e os riscos associados à sua implementação no processo de desenvolvimento de software, considerandose os aspectos tecnológicos, humanos e econômicos envolvidos em cada tópico abordado ao longo do trabalho / Abstract: In a globalized world, the needs to release new systems to manage the large volume of information generated every day force a continuous search for new software development practices in order to handle this information. This is related to the needs to obtain quality and productivity improvements, as well as cost reduction in such development, because these are the main success factors of Information Technology companies. In this scenario, the component reuse in the software development process plays an important role in order to achieve these goals. This work presents the concepts around the context of a software development process based on reusable components. Different types of reuse are explained, as well as the concept of a reusable component and types of components inside an application domain. Components have different characteristics, are originated from different sources and carry on important details that should be analyzed during its documentation. All these aspects have influence on the reuse level of the components inside the project or the company. Some technologies that promote the component reuse and the concepts involved in the definition, management and implementation of reusable software components, which are the basis to consolidate the reuse process, are presented. New roles and responsibilities involved in the reuse process are shown, and also some metrics used to help to measure the benefits due to a consolidated reuse process. The results of this work are a critical analysis about the reuse benefits and the risks associated to its implementation in the software development process, taking into account the technological, human and economic factors involved on each topic discussed along this work / Mestrado / Engenharia de Software / Mestre Profissional em Computação

Orientador: Eliane Martins / Dissertação (mestrado profissional) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-07T10:05:17Z (GMT). No. of bitstreams: 1 Cardoso_JosianeAparecida_M.pdf: 1727201 bytes, checksum: 2b03579fc8602d15cc944cb59e39086e (MD5) Previous issue date: 2006 / Resumo: O desenvolvimento baseado em componentes vem sendo cada vez mais utilizado hoje em dia, pois permite que um sistema seja construído através da reutilização de software. Um problema associado à reutilização de componentes é o fato de que um componente implementado para um determinado contexto pode ser reaproveitado em um outro contexto com especificações diferentes. Esse tipo de problema pode comprometer a construção de um novo sistema de software confiável baseado em componentes. Falhas devem ser encontradas não só nos componentes, mas na integração dos componentes. No contexto de testes de integração, estratégias têm sido propostas considerando apenas abordagens estáticas com base no diagrama de classes do sistema para se definir uma ordenação para os testes de integração minimizando o número de stubs necessários. Esse trabalho propõe um método de testes de integração para sistemas baseados em componentes que se baseia na arquitetura do sistema considerando uma abordagem dinâmica sem a necessidade do código fonte do componente / Abstract: Nowadays the development based on components is being more frequently used since it allows a system to be constructed through the reuse of software. A problem associated to the reuse of components is that one component implemented for a specific context may be reused in another context with different specifications. This kind of problem may jeopardize the construction of a new reliable software system based on components. Faults must be found not only in the components, but in the integration of the components as well. In the context of integration testing, strategies have been proposed considering only the structural approaches based on the class diagram of the system to define an ordering for the integration testing, minimizing the number of stubs needed. This work proposes a method of integration testing for system based on components, which bases itself on the architecture of the system, considering a behavioral approach without the need for the component source code / Mestrado / Engenharia de Computação / Mestre em Computação

This study evaluates three different ways of structuring a software library for an object-oriented system. The traditional class/subclass tree (CIS) is used as well as two methods from the mental model literature: hierarchical cluster analysis (HCA) of sorting data and modal block clustering (MBC) of attribute rating data (Shurtleff, Jenkins, and Sams, 1988; Tullis, 1985). Also examined in this context are two software metrics: depth-in- inheritance-tree (D IT) and response-for-class (RFC) (Lei, 1991, 1993). These two metrics had been found by Lei to correlate with the ease of maintenance of software. It was conjectured that they might also be useful in the study of mental model methods for software. Finally, student and professional programmers are explicitly compared. There has been much debate on the applicability of software-related data generated from student subjects but little research on the topic. The results indicate that subject performance with the MBC representation was worse than with the CIS representation. Also found was that performance with the HCA representation was not sufficiently better to justify the effort involved in creating the new representation. Student programmers were found in this study to be no worse than professional programmers and thus appear to be acceptable substitutes for professional programmers in a class-based search task. This study's results indicate that student response time to locate a class could be used as the lower boundary for professional programmer class locating time. The student error rates, however, could be used as the upper boundary for professional programmer error rate performance in class locating tasks. A "middle" problem was also found. Classes 1n the middle of a library representation proved to be more difficult to locate as measured by time and error rate. Finally, a higher RFC was found to increase search time for a class when it was in the middle of a library representation. A higher RFC also reduced programmer reusability ratings of a class and the programmer's confidence in the reusability rating. / Ph. D.

Approved for public release; distribution is unlimited / This thesis builds upon work previously done in the development of the Computer Aided Prototyping System (CAPS) and the Prototype System Description Language (PSDL), and presents a conceptual design for the Software Base Management System (SBMS) component of CAPS. The SBMS is the most critical component of CAPS as it will coordinate the retrieval and integration of Ada software modules. A robust SBMS that enables a software system designer to successfully retrieve reusable Ada components will expedite the prototype development process and enhance designer productivity. Implementation of the conceptual design will be the basis for further work in this area. (Ada is a registered trademark of the United States Government, Ada Joint Program Office.) / http://archive.org/details/conceptualdesign00gali / Lieutenant Commander, United States Navy

published_or_final_version / Computer Science / Doctoral / Doctor of Philosophy

Abstraction mechanisms in programming languages aim to allow orthogonal pieces of functionality to be developed separately; complex software can then be constructed through the composition of these pieces. The effectiveness of such mechanisms lies in their support for modularity and reusability: The behavior of a piece of code should be reasoned about modularly---independently of the specific compositions it may participate in; the computation of a piece of code should allow specialization, so that it is reusable for different compositions. This dissertation introduces structural abstraction: a mechanism that advances the state of the art by allowing the writing of highly reusable code---code whose structure can be specialized per composition, while maintaining a high level of modularity. Structural abstraction provides a disciplined way for code to inspect the structure of its clients in composition, and declare its own structure accordingly. The hallmark feature of structural abstraction is that, despite its emphasis on greater reusability, it still allows modular type checking: A piece of structurally abstract code can be type-checked independently of its uses in compositions---an invaluable feature for highly reusable components that will be statically composed by other programmers. This dissertation introduces two structural abstraction techniques: static type conditions, and morphing. Static type conditions allow code to be conditionally declared based on subtyping constraints. A client of a piece of code can configure a desirable set of features by composing the code with types that satisfy the appropriate subtyping conditions. Morphing allows code to be iteratively declared, by statically reflecting over the structural members of code that it would be composed with. A morphing piece of code can mimic the structure of its clients in composition, or change its shape according to its clients in a pattern-based manner. Using either static type conditions or morphing, the structure of a piece of code is not statically determined, but can be automatically specialized by clients. Static type conditions and morphing both guarantee the modular type-safety of code: regardless of specific client configurations, code is guaranteed to be well-typed.

Orientador: Islene Calciolari Garcia / Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-11T15:53:44Z (GMT). No. of bitstreams: 1 Oliveira_MarciliodaSilva_M.pdf: 2563654 bytes, checksum: a5cf71efc67be68a783a10873fd26809 (MD5) Previous issue date: 2006 / Resumo: Arquiteturas Peer-to-Peer (P2P) têm sido uma alternativa bastante atraente para tornar a Internet mais acessível. Desde programas de compartilhamento de conteúdo a sistemas de comunicação têm utilizando esta abordagem de arquitetura e dando importantes contribuições para melhorias nas tecnologias e metodologias relacionadas as redes P2P. Neste contexto, o presente trabalho apresenta a definção da arquitetura de uma rede P2P para distribuição e compartilhamento de componentes de software, visando montar uma rede descentralizada, na qual qualquer participante possa se conectar, fornecer e buscar por componentes de software. Os componentes de software são módulos independentes, com interfaces bem definidas, que podem ser reutilizados em diferentes situações. O reuso de software vem se destacando como grande promessa para aumentar a produtividade no desenvolvimento de sistemas. A aplicação do reuso de software se concentra principalmente na reutilização e integração de partes prontas e previamente testadas. Este trabalho apresenta também a concepção de um modelo de repositório para armazenamento de componentes de software. Estes repositórios podem se comunicar através do protocolo de rede desenvolvido, montando uma rede de compartilhamento P2P. Através da construção da arquitetura, do mecanismo de busca e modelagem dos repositórios, propomos aqui a estrutura fundamental para a criação de redes e sub-redes independentes, visando compartilhar componentes de software entre grupos de pesquisa, universidades, desenvolvedores e empresas. Esta arquitetura constitui a estrutura de distribuição da Rede de Compartilhamento de Componentes de Software (RCCS). A RCCS 'e um projeto de construção de uma rede pública para compartilhamento de componentes, desenvolvido no Laboratório de Inovação Ci&T/Unicam / Abstract: Peer-to-peer (P2P) architectures have become a very attractive alternative to make the Internet more accessible. This approach has been widely used, from content sharing programs through communications systems, which has provided the P2P networks with considerable improvements in the technology and methodologies related. In this context, the current work presents the architecture definition of a decentralized P2P network for distribution and sharing of software components in which any participant can get connected, offer and search for software components. Software components are interdependent modules with well-defined interfaces that can be reused in different situations. Software reuse has been considered the big boom when it comes to productivity in software development. Reusing is related to the integration of ready and previously tested pieces of software. This work also presents the conception of a repository model for storing software components. These repositories can communicate with one another using the custom built network protocol, resulting in a strong and reliable P2P sharing network. Through the architecture definition, the search mechanism and the modeling of the repositories, we propose the fundamental structure for the creation of independent network and sub-networks so as to share software components between research groups, universities and developers. Such architecture constitutes the distribution structure of the Software Component Sharing Network. The project focused on developing this public network for sharing components has been hosted at the Ci&T/Unicamp Innovation Lab / Mestrado / Sistemas Distribuidos / Mestre em Ciência da Computação

The software development continues to become more competitive and demanding, placing pressure on developers. Changes in the international political climate have resulted in shrinking military budgets, putting developers of defence software under further pressure. At present, systematic reuse is probably the most realistic way of addressing this pressure by improving software development productivity and quality. Software product line (SPL) engineering provides a comprehensive approach to systematic software reuse and is becoming widely accepted. The focus of this interpretive case study was ground station software development in a small multidisciplinary project-centric company which produces avionics systems for military aircraft. The purpose of the study was to investigate the potential implementation of systematic software reuse in the company. The study consisted of three phases, a literature study, a contextualisation and a set of field interviews, and used elements of the Carnegie-Mellon Software Engineering Institute (SEI) Product Line Practice Framework to examine the suitability of SPL engineering for the company. The findings of the study highlight the potential challenges that SPL engineering poses for the company, and emphasise how the company's project-centric structure could impede its implementation of systematic software reuse. / Computing / M.Sc. (Information Systems)