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: Cecilia Mary Fischer Rubira / Dissertação (mestrado profissional) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-07T00:50:23Z (GMT). No. of bitstreams: 1 Pinho_HelderdeSousa_M.pdf: 1255692 bytes, checksum: 91ab06629ddbbf4b6885b93010e3511f (MD5) Previous issue date: 2006 / Resumo: O desenvolvimento baseado em componente (DBC) pennite que uma aplicação seja construída pela composição de componentes de software que já foram previamente especificados, construídos e testados, resultando em ganhos de produtividade e qualidade no software produzido. Para haver reuso de componentes, é necessário que usuários consIgam procurar e recuperar componentes previamente especificados ou implementados Um repositório de componentes é essencial para possibilitar tal reuso. Interoperabilidade é um requisito importante para repositórios, mas nem todas as ferramentas a tratam com a devida relevância. O modelo de metadados de um repositório para DBC deve contemplar características de componentes, tais como interface e separação entre especificação e implementação. Este trabalho apresentou o Rigel, um repositório de bens de software reutilizáveis com suporte para desenvolvimento baseado em componentes. O Rigel apresenta características que facilitam atividades executadas durante o desenvolvimento de sistemas baseados em componentes, tais como pesquisa, armazenamento e recuperação de bens e integração com CVS. O padrão RAS foi adotado como o fonnato de metadados e de empacotamento de bens, facilitando a integração do Rigel com outros sistemas. O modelo de metadados do RAS foi estendido para apoiar um modelo conceitual de componentes e arquitetura de software. Esta adaptação resultou na criação de quatro novos profiles RAS, para apoiar bens relacionados à DBC: componente abstrato, componente concreto, interface e configuração arquitetural. Um estudo de caso foi conduzido a fim de mostrar como o Rigel apóia um processo de desenvolvimento baseado em componentes. Conclui-se que as características do repositório Rigel facilitam um desenvolvimento baseado em componentes / Abstract: The component based development (CBD) permits an application to be built by composition of previously specified, build and tested components, resulting in increases in productivity and quality of the produced software. 1n order to make the reuse of components happen, it is necessary that users are able to search and retrieve previously specified or implemented components. A component repository is important to support this reuse. 1nteroperability is an important requirement for repositories, but not alI the tools consider it with the required relevance. The metadata model of a CBD repository must handle components features, such as interface and separation between specification and implementation. This work presents Rigel, a repository of reusable software assets with a support for component based development. Rigel presents features that make activities performed during the development of component based systems easier, such as search, storage and retrieval of assets and CVS integration. RAS standard was adopted as the asset metadata and packaging format, making Rigel integration with other systems easier. The RAS metadata model was extended to support a conceptual model of components and software architecture. This adaptation resulted in the creation of four new RAS profiles to support CBD related assets: abstract component, concrete component, interface and architectural configuration. A case study was conducted in order to show how Rigel supports a CBD processo We also conclude that Rigel repository features make the component based development easier / Mestrado / Engenharia de Computação / Mestre em Computação

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

ISO 26262 is an international standard valid for the automotive domain. It regulates all the activities to perform for developing safety critical systems in such domain. To be compliant with ISO 26262, all the required activities have to be performed and all the required work products have to be provided. Furthermore, in addition to develop a system in a safe way, following the safety standard guidelines, the achieved safety has also to be demonstrated. This is done through a safety case, a structured argument showing that a system is acceptably safe. ISO 26262 focuses on single systems and does not contain guidelines for product lines. Product line engineering is a valid approach to systematize reuse, aimed at reducing the effort needed to develop similar systems. But, it loses its strength when dealing with safety critical systems, since it is not aligned with safety standards. Hence, when developing a safety critical product line in the automotive domain, the work products required by ISO 26262 have to be provided every time from scratch, including the safety case, for each single system of the product line. This thesis work focuses on providing an approach for building and modeling a safety case for safety critical product lines in the automotive domain. Furthermore, the considered product line engineering approach is aligned with ISO 26262, through the inclusion of safety activities in the product line development process. Giving in this way, the concrete possibility to overtake to the current limitations, reducing the effort needed to develop and certificate each single system of a safety critical product line. To illustrate the validity of the proposed approach a safety critical product line developed by Scania is used as case study.

While several approaches exist for modeling goals and business processes in organizations, the relationships between these two views are often not well defined. This inhibits the effective reuse of available knowledge in models. This thesis aims to address this issue through the introduction of a Goal-oriented Pattern Family (GoPF) framework that helps constructing business process models from organization goals while expanding these goals, establishing traceability relationships between the goal and process views, and improving reusability. Methods for extracting domain knowledge as patterns, which are composed of goal model building blocks, process model building blocks, and their relationships, and for maintaining the patterns over time are also presented. The GoPF framework provides the infrastructure for defining pattern families, i.e., collections of related patterns for particular domains. The foundation of GoPF is formalized as a profile of the User Requirements Notation, a standard modeling language that supports goals, scenarios, and links between them. A method for the use of GoPF is defined and then illustrated through a case study that targets the improvement of patient safety in healthcare organizations. The framework and the extraction/maintenance methods are also validated against another case study involving aviation security in a regulatory environment. The GoPF framework is expected to have a positive impact on the scientific community through the formalization, evolution, and reuse of patterns in domain-specific business domains. From an industrial viewpoint, this framework will also help intermediary organizations (such as consulting firms) who are required to repeatedly create and document goal and process models for other organizations in their business domain.

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)

This study focuses on the development of novel two-stage esterification-transesterification synthesis of biodiesel from used cooking oil (UCO) using novel heterogeneous catalysts. The esterification of the UCO was investigated using three types of ion exchange resins catalysts including Purolite D5081, Purolite D5082 and Amberlyst 15. Of all the catalysts investigated, Purolite D5081 resin showed the best catalytic performance and was selected for further optimisation studies. From the optimisation study, it was found that the external and internal mass transfer resistance has negligible effect on the esterification reaction. At the optimum reaction conditions, Purolite D5081 achieved 92% conversion of FFA. During reusability study, the conversion of FFA dropped by 10% after each cycle and it was found that progressive pore blockage and sulphur leaching were dominant factors that decreased the catalytic performance of the Purolite D5081 catalyst. A kinetic modelling for FFA esterification was carried out using Purolite D5081 as a catalyst. Three types of kinetic models were investigated i.e. pseudo homogeneous (PH), Eley-Rideal (ER) and Langmuir-Hinshelwood-Hougen-Watson (LHHW). Experimental data obtained from the batch kinetic studies was successfully represented by the PH model and a good agreement between experimental and calculated values was obtained. The activation energy for esterification and hydrolysis reaction was found to be 53 and 107 kJ/moL. The transesterification of pre-treated cooking oil (P-UCO) was investigated using various types of heterogeneous catalysts including Purolite CT-122, Purolite CT-169, Purolite CT-175, Purolite CT-275, Purolite D5081, Diaion PA306s and Cs-supported heteropolyacids catalysts. Of all the catalysts investigated, Diaion PA306s catalyst showed the highest conversion of triglycerides and was selected for further optimisation studies. At the optimum reaction conditions, Diaion PA306s achieved ca. 75% of triglycerides conversion. During the reusability study, Diaion PA306s catalyst gave a similar conversion of triglycerides after being reused once. Therefore, it was concluded that the resin can be used several times without losing catalytic activity. Several purification methods have been investigated and dry washing method was chosen as the best alternative for biodiesel purification.

La lipase de Yarrowia lipolytica (EC 3.1.1.3) est une enzyme appartenant à la classe des hydrolases. La non pathogénicité et le caractère hyperproducteur en lipase de cette levure lui confèrent une place de choix au sein de lunité de Bio-industries du Centre Wallon de Biologie Industrielle. Ce présent travail sinscrit dans le cadre général du développement industriel de la lipase de Yarrowia lipolytica et concerne plus particulièrement le traitement post-culture de lenzyme afin de réaliser des formes liquides, poudres atomisées, immobilisées et enrobées à laide des polymères acryliques. Latomisation de la lipase en présence ou en absence de poudre de lait a permis lacquisition de poudres fluentes, stables à 4 et 20°C et présentant des températures de transition vitreuse comprises entre 51 et 79°C. Lactivité deau de conservation des poudres était ≤ 0.4. La stabilisation de lenzyme sous forme de liquide concentré réalisée avec le monopropylène glycol (MPG), les inhibiteurs de protéases et lirradiation aux rayons gamma ont révélé que le MPG à 50% et la technique dirradiation au rayon gamma permettaient la stérilisation et la préservation de lactivité enzymatique. Par ailleurs, limmobilisation de cette enzyme par trois techniques (adsorption, inclusion et liaison covalente) a révélé une amélioration de ses propriétés caractéristiques telles que la thermostabilté et la résistance aux solvants. La technique dimmobilisation par adsorption et par liaison covalente a permis une utilisation multiple de lenzyme. Létude préliminaire de faisabilité des formes galéniques à base de la lipase de Y. lipolytica a montré la capacité de cette enzyme à être mise sous forme de comprimés et de poudres encapsulées. La comparaison réalisée in vitro entre le Créon 150mg (produit pharmaceutique) et les formes galéniques à base de la lipase a montré des temps de gastro-résistance et de délitage similaires. Ces différentes formules de la lipase posent des jalons nécessaires pour leurs applications dans des secteurs agroalimentaires, environnementaux et pharmaceutiques. Yarrowia lipolytica lipase (EC.3.1.1.3) is an enzyme which belongs to the class of hydrolases. Nonpathogenicity and the high-lipase producing character of this yeast have emphasised its use within the laboratory of Bio-industry of the Walloon Center of Industrial Biology. The present work lies within the general scope of the industrial development of the lipase from Yarrowia lipolytica. More particularly it relates to the post-culture treatment of the enzyme in order to obtain liquid forms, atomized powders, immobilized and coated enzymes using acrylic polymers. The atomization of lipase in presence or absence of milk powder allowed the achievement of flowing, stable powders at 4 and 20°C, with glass transition temperatures ranging between 51 and 79°C. The water activity of preservation of the powders was ≤ 0.4. Stabilization of the enzyme under the form of concentrated liquid carried out with monopropylen glycol (MPG), proteases inhibitors and gamma irradiation revealed that MPG (50%) and gamma irradiation allowed sterilization and conservation of the enzymatic activity. In addition, the immobilization of the enzyme through three techniques (adsorption, inclusion and covalent bond) revealed an improvement of some properties such as thermostability and resistance to solvents. Immobilization by adsorption and covalent bond allowed multiple uses of the enzyme. The preliminary study of feasibility of galenic forms containing the lipase from Y. lipolytica showed the capacity of this enzyme to be put under the form of tablets and encapsulated powders. The in vitro comparison of Creon 150mg (pharmaceutical product) and galenic forms containing the lipase, showed similar times of acid-resistance and of disintegration. These various formulas of the lipase constitute milestones necessary for their applications in food, environmental and pharmaceutical industries.

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)

Submitted by Milena Rubi (milenarubi@ufscar.br) on 2017-06-01T17:00:50Z No. of bitstreams: 1 MORAES_Rodrigo_2016.pdf: 42751751 bytes, checksum: 25891a495567a6bce1d41328abf03d12 (MD5) / Approved for entry into archive by Milena Rubi (milenarubi@ufscar.br) on 2017-06-01T17:00:58Z (GMT) No. of bitstreams: 1 MORAES_Rodrigo_2016.pdf: 42751751 bytes, checksum: 25891a495567a6bce1d41328abf03d12 (MD5) / Approved for entry into archive by Milena Rubi (milenarubi@ufscar.br) on 2017-06-01T17:01:04Z (GMT) No. of bitstreams: 1 MORAES_Rodrigo_2016.pdf: 42751751 bytes, checksum: 25891a495567a6bce1d41328abf03d12 (MD5) / Made available in DSpace on 2017-06-01T17:01:09Z (GMT). No. of bitstreams: 1 MORAES_Rodrigo_2016.pdf: 42751751 bytes, checksum: 25891a495567a6bce1d41328abf03d12 (MD5) Previous issue date: 2016-11-25 / Não recebi financiamento / The APIs are becoming increasingly more popular and they play a important role in software development. However, many APIs are large and complex that makes them hard to learn. Among avaliable resources to learn to use an API, there are the code samples. A code sample can be used to demonstrate to a programmer how to use API’s components together to attain a specific goal. But, code sample are static and they haven’t information about how to adapt the code snippet shown as example to programmer’s context. Tools have been proposed to assist the programmers in finding and adapting code snippets that may be useful for a programming task. A specific type of these tools are the code template tools. Code templates are code snippets manually registered containing integration directives. The integration directives instruct the code template tool on how to adapt a code snippet to programmer’s context. In this work, code snippet tools are investigated and it is proposed a code template tool called IPS. It presents some novelties in relation to other code template tools. In the IPS, a code template can be associated to a Java class and the IPS has a code template recommender that is automatically updated as the source code is edited by the programmer. Also it is proposed the role parameters, a new concept for the parameters of code templates that extends the concept of the parameters associated to a type which is present in current code template tools. The role parameters has the objective of accepting arguments that would at first be incompatible with a specific type, but that obey a expected pattern. / As APIs têm se tornado cada vez mais populares e elas têm um papel fundamental no desenvolvimento de software. No entanto, muitas APIs são grandes e complexas o que torna a aprendizagem delas difícil. Entre os recursos disponíveis para se aprender a utilizar uma API, há os exemplos de código. Um exemplo de código pode demonstrar a um programador como componentes de uma API podem ser utilizados juntos para atingir um determinado objetivo. Porém, exemplos de código são estáticos e não contêm informações de como adaptar o trecho de código apresentado como exemplo para o contexto do programador. Ferramentas têm sido propostas para auxiliar os programadores a encontrarem e adaptarem trechos de códigos que possam ser úteis para uma tarefa de programação. Um tipo específico dessas ferramentas são as ferramentas de templates de código. Templates de código são trechos de códigos cadastrados manualmente contendo diretivas de integração. As diretivas de integração instruem a ferramenta a como adaptar um trecho de código para o contexto do programador. Neste trabalho, ferramentas de trechos de código são investigadas e é proposta uma ferramenta de template de código denominada IPS. Ela apresenta novidades em relação às outras ferramentas de templates de código. No IPS, um template de código pode ser associado a uma classe Java e o IPS possui um recomendador de templates de código que é automaticamente atualizado conforme o código fonte é editado pelo programador. Também é proposto os parâmetros do tipo role, um novo conceito que estende o conceito dos parâmetros associados a um tipo que está presente nas ferramentas de templates de código atuais. Os parâmetros do tipo role têm como objetivo aceitar argumentos que seriam a princípio incompatíveis com um determinado tipo, porém que sigam um determinado padrão esperado.