Dissertations / Theses on the topic 'Component Reuse'
To see the other types of publications on this topic, follow the link: Component Reuse.
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Component Reuse.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
ALVARO, Alexandre. "Software component certification: a component quality model." Universidade Federal de Pernambuco, 2005. https://repositorio.ufpe.br/handle/123456789/2796.
Full textAbstract:
Made available in DSpace on 2014-06-12T16:01:14Z (GMT). No. of bitstreams: 2
arquivo7273_1.pdf: 859722 bytes, checksum: 0a10aaaffe0f345515ef1d4559599ff4 (MD5)
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2005Coordenação de Aperfeiçoamento de Pessoal de Nível Superior
Desenvolvimento de Software Baseado em Componentes tem sido amplamente adotado na academia e na prática, representando assim um mercado promissor para a indústria de software. A perspectiva de redução do custo e do ciclo de desenvolvimento do software tem sido a principal motivação para esta expansão. Entretanto, inúmeros problemas técnicos ainda permanecem sem solução antes mesmo que a indústria de componentes de software alcance a maturidade de outras indústrias de software. Problemas como a seleção de componentes, a carência de catálogos de componentes formalizados e a falta de informações sobre a qualidade dos componentes desenvolvidos trazem novos desafios para a comunidade de engenharia de software. Por outro lado, a área de certificação de componentes de software é relativamente imatura e necessita de consideráveis pesquisas para o estabelecimento de um padrão para certificação de componentes de software. Assim, esta dissertação apresenta um modelo de qualidade de componentes, baseada em características consistentes e bem definida, atributos de qualidade e métricas relacionadas para avaliação dos componentes. Um estudo experimental foi desenvolvimento visando analisar a viabilidade de utilização do modelo. Os resultados obtidos mostrar-se-iam que o modelo é um interessante candidato para avaliação da qualidade em componentes de software, e trabalhos futuros estão sendo planejamentos para que a evolução do modelo alcance o nível de maturação necessário e torne-o diretamente aplicável à indústria de software
2
Jonge, Merijn de. "To reuse or to be reused techniques for component composition and construction /." [S.l. : Amsterdam : s.n.] ; Universiteit van Amsterdam [Host], 2003. http://dare.uva.nl/document/71158.
Full textAbstract:
Proefschrift Universiteit van Amsterdam.Research carried out under the auspices of the research school IPA (Institute for Programming research and Algorithmics) Met lit. opg. - Met samenvatting in het Nederlands.
3
Mateas, Michael Joseph. "A Cognitively Motivated System for Software Component Reuse." PDXScholar, 1993. https://pdxscholar.library.pdx.edu/open_access_etds/4699.
Full textAbstract:
Software reuse via component libraries suffers from the twin problems of code location and comprehension. The Intelligent Code Object Planner (ICOP) is a cognitively motivated system that facilitates code reuse by answering queries about how to produce an effect with the library. It can plan for effects which are not primitive with respect to the library by building a plan that incorporates multiple components. The primary subsystems of ICOP are a knowledge base which describes the ontology of the library, a natural language interface which translates user queries into a formal effect language (predicates), a planner which accepts the effect and produces a plan utilizing the library components, and an explanation generator which accepts the plan and produces example code illustrating the plan. ICOP is currently implemented in Prolog and supports a subset of the Windows 3.0 APL
4
Pryce, Nathaniel Graham. "Component interaction in distributed systems." Thesis, Imperial College London, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.313411.
Full text
5
Karlsson, Daniel. "Towards Formal Verification in a Component-based Reuse Methodology." Licentiate thesis, Linköping : Univ, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-5696.
Full text
6
Good, Marissa Ann. "Developing a component reuse strategy for space launch vehicles." Thesis, Massachusetts Institute of Technology, 2017. http://hdl.handle.net/1721.1/112486.
Full textAbstract:
Thesis: S.M., Massachusetts Institute of Technology, Department of Aeronautics and Astronautics, in conjunction with the Leaders for Global Operations Program at MIT, 2017.Thesis: M.B.A., Massachusetts Institute of Technology, Sloan School of Management, in conjunction with the Leaders for Global Operations Program at MIT, 2017.
Cataloged from PDF version of thesis.
Includes bibliographical references (page 84).
Launch vehicle hardware is traditionally very expensive to design, develop, produce and certify, because it must operate in extreme environments with high reliability. The result is that most hardware for NASA-funded launch vehicles is custom built to execute a specific mission on a single platform. In contrast to other industries (e.g. automotive), very few components are used across product platforms, a strategy known as reuse that has the potential to decrease the cost, schedule and risk of new product introduction. Budget constraints on NASA's next launch vehicle, the Space Launch System (SLS), brought about a desire to realize some of the benefits associated with reuse. However, the reuse strategy as employed has met limited success. This brings about the fundamental question: is there something inherently unique about launch vehicle design that prevents or limits reuse? If not are there strategies that can be implemented to realize the benefits of proactive reuse during launch vehicle design? The Boeing Company, the prime contractor of the SLS cryogenic stages, would like to develop a reuse approach as they begin work on the next phase of the SLS, the Exploration Upper Stage (EUS), to improve project affordability. To develop this approach, a case study of the Core Stage (CS) was performed to identify lessons learned, resulting in the following insights: 1. Capturing the benefits of reuse is enabled by modularity and platforms within single-vehicle architectures rather than across vehicles. The time offset between any two launch vehicles is too great (20-30 year product lifecycles) for reuse across vehicles. Furthermore, manned and unmanned vehicles carry different requirements which must be considered when evaluating the potential for shared assets. 2. Race should be defined as the baseline, rather than as an opportunity. This requires aligning incentives and architecting the organization to enforce reuse from the outset. 3. Plan for forward reuse. Consider future requirements when designing the current vehicle. Reuse will not happen by coincidence; it must be designed into the system. These insights form the basis of a reuse approach for the Exploration Upper Stage (EUS). In combination with some organization and process-based suggestions, a strategy to realize the benefits of reuse has been developed for the EUS and other future launch vehicles.
by Marissa Ann Good.
S.M.
M.B.A.
7
Cornwell, Peter David. "Reusable component engineering for hard real-time systems." Thesis, University of York, 1998. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.263689.
Full text
8
Affonso, Frank José. "Metodologia para desenvolvimento de software reconfigurável apoiada por ferramentas de implementação: uma aplicação em ambiente de execução distribuído e reconfigurável." Universidade de São Paulo, 2009. http://www.teses.usp.br/teses/disponiveis/18/18152/tde-02072009-095730/.
Full textAbstract:
O desenvolvimento de software reconfigurável é uma abordagem que requer padrões nas atividades e nos artefatos produzidos ao longo da elaboração de um projeto de software. Além disso, também prevê uma conduta sistemática do pessoal envolvido, para que as diretrizes de uma metodologia sejam executadas e os benefícios por ela previstos sejam alcançados. Neste trabalho, uma metodologia para o desenvolvimento de software reconfigurável foi elaborada para apoiar essa abordagem de desenvolvimento. Como forma de auxiliar as atividades existentes nesta metodologia e padronizar as atividades por ela previstas, minimizando a participação de seres humanos (desenvolvedores), foi confeccionada uma ferramenta composta por um conjunto de subsistemas capazes de gerar, de maneira automática, informações necessárias, para que a padronização dos procedimentos possa ser realizada e, consequentemente, que a reconfiguração e reutilização dos artefatos ocorram de maneira natural. Essa ferramenta atua em um ambiente distribuído e organizado pelos domínios de atuação e a reutilização/reconfiguração pode ocorrer em artefatos confeccionados para atuar em domínio específico, mas que podem ser adaptados/reutilizados em outros.The reconfigurable software development is an approach that requires patterns in the activities and in the artifacts produced during the development of a software project. It also requires a systematic conduct of the staff involved in the methodology guidelines, so that the benefits provided can be achieved. In this work, a methodology for the reconfigurable software development was proposed to support this approach. As a way to assist the activities in this methodology and standardize the required activities, minimizing the involvement of humans (developers), a tool was proposed that consists in a set of subsystems capable of generating, in an automatic manner, information needed so that the standardization of information can be performed, therefore, that the reconfiguration and reuse of artifacts could be occur in a natural way. This tool operates in a distributed environment organized by areas of expertise, and reuse/reconfiguration can occur in artifacts constructed to operate in specific domains, but it can be adapted/reused in others.
9
Bleek, Morgan John. "Regeneration reuse in the context of the waste management cycle of the built environment." Thesis, Queensland University of Technology, 2013. https://eprints.qut.edu.au/60855/1/N7252579_BN71_Thesis_June_2013_ePrints_Ready_Issue.pdf.
Full textAbstract:
This original study creates a philosophy of regeneration reuse, which is a conceptual framework that utilises construction and demolition waste products by building component, relocation and adaptive reuse. Case studies from the greater Brisbane, wider southeast Queensland region and greater London area are used to demonstrate the principles of regeneration reuse through research activities, analysis and evaluation. The regeneration reuse conceptual process draws upon assessing embodied carbon and sustainable benefits to deconstruct rather than destruct, and consider alternative options to waste treatment technologies in the built environment. The importance of waste management is examined, specifically the impacts of governance to the principles of regeneration reuse through analysis of legislation in the Australian and UK jurisdictions. Design process considerations when incorporating the principles of regeneration reuse are defined, and phasing and staging assessment explored to determine the most effective point of intervention in the design process to include waste management strategies.
10
Mili, Rym. "Determining the reuse worthiness of a component, empirical and analytical approaches." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp04/nq21010.pdf.
Full text
11
Thomson, Derek Stewart. "The development of packaged, reusable building services components : a pilot study in the UK national health service." Thesis, Heriot-Watt University, 2000. http://hdl.handle.net/10399/1165.
Full text
12
Goodman, Steven. "The microwave induced pyrolysis of problematic plastics enabling recovery and component reuse." Thesis, Imperial College London, 2014. http://hdl.handle.net/10044/1/23937.
Full textAbstract:
Recent trends toward the effective utilisation of petroleum derived materials to increase the sustainability of their use (both for economic and environmental reasons), has resulted in an increased interest in the development of recycling methods for plastics including Acrylonitrile- co-Butadiene-co Styrene and Poly Vinylchloride. The recycling of these waste plastics that include mixed monomer compositions and halogens poses a great problem, with their decomposition making them hard to recycle due to loss of their material properties or through the production of problematic compounds e.g. HCl, PCBs, PCDD, and PCDF etc. This work has investigated the microwave induced decompositions of these plastics and explored the potential of a carbon (a microwave absorber) assisted microwave decomposition process. This culminated in the examination of the carbon assisted microwave decomposition of ABS and the potential of a one and two step process for the de-hydrochlorination, then pyrolysis of PVC, which is an untried and novel approach for PVC recycling. . The influence of microwave power, exposure time, along with the effect of the proportion of carbon, was investigated for its influence upon the yields of gases, oils, chars and product components. The proportions of gases, oils and chars were quantified in terms of their product distribution and subsequently analysed for their properties/composition by TGA, FT-IR, GCMS, Py-GCMS and bomb calorimetry. From their analyses product distributions in the oils and gases were derived and decomposition mechanisms evaluated. From these investigations it was found that the microwave decomposition process of both plastics was possible and demonstrated great versatility, with oil yields for ABS of between 2wt.% to 70wt.% and gas yields of 28wt.% to 77wt.% achieved in processing times as little as 3 minutes. From this it was also possible to identify that high quantities of monomer were also able to be recovered, significantly greater than that of a thermal process (39.5%TiC as to 34.5%TiC respectively for styrene monomer). For PVC, it was identified by initial investigations that the de-hydrochlorination of PVC was possible, confirming results of Ito et al., (2006) and Moriwaki et al., (2006). However, the discovery of amplitude dependent heating was of significant interest, not previously identified in any microwave decomposition process. It was also recognized that pyrolysis was not possible after de-hydrochlorination of PVC occurred as a result of the reduction in the materials ability to absorb microwaves (lesser dielectric constant), due to chlorine was removal. Hence it was necessary to investigate the use carbon additive to enable achieving sufficient temperatures to induce the pyrolysis of the remaining polyene structure. The identification of key parameters and ensuing relationships with microwave power, heating rate and temperatures was identified herein, giving the first detailed account of the relationship between specific polymer types and microwaves during a pyrolysis process.
13
Stovsky, Michael Philip. "A framework and environment supporting software component reuse for teams of developers /." The Ohio State University, 1990. http://rave.ohiolink.edu/etdc/view?acc_num=osu1487677267729988.
Full text
14
Hollingsworth, Joseph Eugene. "Software component design-for-reuse : a language-independent discipline applied to ada /." The Ohio State University, 1992. http://rave.ohiolink.edu/etdc/view?acc_num=osu1487778663285694.
Full text
15
Silva, Fernando Raposo da Camara. "A component testing approach supported by a CASE tool." Universidade Federal de Pernambuco, 2008. https://repositorio.ufpe.br/handle/123456789/1584.
Full textAbstract:
Made available in DSpace on 2014-06-12T15:51:15Z (GMT). No. of bitstreams: 1
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2008A reutilização de artefatos, ao invés de construí-los do zero, processo usualmente conhecido como reuso de software, mostra-se uma boa opção de vantagem competitiva para as empresas de desenvolvimento de software. Neste contexto, o desenvolvimento baseado em componentes é uma das técnicas mais aplicadas para promover o reuso de software estabelecendo um promissor mercado de componentes. Entretanto, os métodos mais consolidados de desenvolvimento de componentes estão mais focados em demonstrá-lo como uma abordagem viável, e algumas atividades importantes, por exemplo, atividades relacionadas com qualidade, e mais especificamente, relacionadas a teste, são muitas vezes negligenciadas. Produtores de componentes têm dificuldades para preparar seus produtos para funcionar corretamente em diferentes contextos, como também para serem validados pelos consumidores que pretendem adotá-los. Similarmente, os consumidores de componentes possuem limitações para poder testar se componentes externos funcionam como especificados, e se são capazes de serem integrados aos seus sistemas. Assim, esta dissertação apresenta uma abordagem para apoiar o teste de componentes definindo atividades para guiar produtores de componentes no preparo de seus produtos para serem testados por terceiros, como também atividades para os consumidores de componentes para compreender e testar componentes externos objetivando a sua integração com seus sistemas em desenvolvimento. Por fim, é apresentada uma ferramenta para realizar as atividades definidas para produtores e consumidores. Um experimento foi conduzido avaliando a abordagem proposta e sua ferramenta relacionada
16
Yilmaz, Levent. "Specifying and Verifying Collaborative Behavior in Component-Based Systems." Diss., Virginia Tech, 2002. http://hdl.handle.net/10919/26494.
Full textAbstract:
In a parameterized collaboration design, one views software as a collection of components that play specific roles in interacting, giving rise to collaborative behavior. From this perspective, collaboration designs revolve around reusing collaborations that typify certain design patterns. Unfortunately, verifying that active, concurrently executing components obey the synchronization and communication requirements needed for the collaboration to work is a serious problem. At least two major complications arise in concurrent settings: (1) it may not be possible to analytically identify components that violate the synchronization constraints required by a collaboration, and (2) evolving participants in a collaboration independently often gives rise to unanticipated synchronization conflicts. This work presents a solution technique that addresses both of these problems. Local (that is, role-to-role) synchronization consistency conditions are formalized and associated decidable inference mechanisms are developed to determine mutual compatibility and safe refinement of synchronization behavior. More specifically, given generic parameterized collaborations and components with specific roles, mutual compatibility analysis verifies that the provided and required synchronization models are consistent and integrate correctly. Safe refinement, on the other hand, guarantees that the local synchronization behavior is maintained consistently as the roles and the collaboration are refined during development. This form of local consistency is necessary, but insufficient to guarantee a consistent collaboration overall. As a result, a new notion of global consistency (that is, among multiple components playing multiple roles) is introduced: causal process constraint analysis. A method for capturing, constraining, and analyzing global causal processes, which arise due to causal interference and interaction of components, is presented. Principally, the method allows one to: (1) represent the intended causal processes in terms of interactions depicted in UML collaboration graphs; (2) formulate constraints on such interactions and their evolution; and (3) check that the causal process constraints are satisfied by the observed behavior of the component(s) at run-time.Ph. D.
17
Chan, Chibong. "Design and implementation of software to automate reuse in component-based system engineering." Thesis, Massachusetts Institute of Technology, 2004. http://hdl.handle.net/1721.1/33125.
Full textAbstract:
Thesis (M. Eng. and S.B.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2004.Includes bibliographical references (leaf 45).
The goal of this thesis is to develop software under the SpecTRM software package for the partial automation of tasks associated with reusing SpecTRM-RL component models. The automation software is designed to aid the application of component-based system engineering in SpecTRM, mainly by reducing the amount of manual work necessary in setting up component models for simulation. My thesis will examine the properties of component models, and the common tasks associated with component-based system engineering, so as to identify areas where automation is possible, and then present the user interfaces and algorithms necessary to achieve automation. The automation software will be implemented in Java under the Eclipse platform, in order to be seamlessly integrated into the SpecTRM software package.
by Chibong Chan.
M.Eng.and S.B.
18
Jobe, Jonathan Michael. "Multi-aspect component models enabling the reuse of engineering analysis models in SysML /." Thesis, Atlanta, Ga. : Georgia Institute of Technology, 2008. http://hdl.handle.net/1853/24810.
Full text
19
Rugrungruang, Fatida Mechanical & Manufacturing Engineering Faculty of Engineering UNSW. "An integrated methodology for assessing physical and technological life of products for reuse." Publisher:University of New South Wales. Mechanical & Manufacturing Engineering, 2008. http://handle.unsw.edu.au/1959.4/41272.
Full textAbstract:
Strategies for reuse of components are important in order to create a closed loop manufacturing system. Over decades, the notion has been gaining ground due to environmental and legislative reasons. Reuse of components is desirable and in many cases might be economically beneficial. However, the implementation of reuse strategies has been hindered by the requirement of reliable methodologies to assess the remaining life and reuse potential of used components. The estimation of the remaining life is problematic as the useful life of a component is affected by several causes of obsolescence. The common causes are due to physical and technological issues. So far, little research has attempted to address these issues simultaneously, and integrating them. This thesis seeks to develop methodologies that aid in predicting the integrated remaining lifetime of used components. There are three core parts of this research. First, the methodology determines the remaining life of used components from the physical lifetime perspective. This was derived from the estimation of physical failure using failure rate data, and the statistical analysis of usage intensity age as obtained from customers survey. Second, the research presents the use of the technological forecasting technique to predict the remaining technological life. As it is influenced by the technology progress, the forecast was developed on the basis of product technology clusters and market trend extrapolation analysis. Finally, the resulting estimations from the two aspects were combined to obtain an integrated assessment for estimating the remaining life of components. The potential for components in a product to be reused is justified when the remaining life is greater than the average expected lifespan of the product. Two cases of domestic appliances televisions and washing machines were used to highlight and demonstrate the validity of the proposed methodology. The results show that the proposed method provides the practitioners with a promising tool for end-of-life decision making. This is in particularly attractive when used as a preliminary decision support tool prior to the time consuming and costly processes such as disassembly and quality testing.
20
Al-Nuaimi, Mina, and Lina Widegren. "Component remanufacturing for improved lifecycle utilization." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-52845.
Full textAbstract:
Remanufacturing is the process of collecting end-of-life products from customers and then being dissembled, reprocessed and reassembled to create new products to meet the customers’ needs. The economic viability of the implementation of a remanufacturing strategy has being shown among many companies in the automobile industry. Also, the economic profitability of the remanufacturing process has been proven in many industrial case studies. Cummins Scania XPI Manufacturing in Södertälje considers implementing a remanufacturing process for their returned components, but there is a lack of a foundation of whether this process will provide an economic profitability or not. In order to decide whether the remanufacturing is profitable for the company, there are some factors to consider. This research aims to identify the reasons behind implementing a remanufacturing process and the factors that affect the economical profitability of it. In order to answer the research questions, a theoretical investigation as well as several interviews with Cummins Scania XPI Manufacturing in Södertälje and Cummins XPJ in Mexico has been done. The aim with the interviews with Cummins Scania XPI in Södertälje was to identify what factors they want to consider when determining whether the remanufacturing process can be economic beneficial for them. The interview with Cummins XPJ was done in order to get an understanding how their remanufacturing process work. The result shows that there can be three main reasons behind implementing a remanufacturing process: economic benefits, environmental benefits as well as legislation. When it comes to the considered factors when implementing the remanufacturing process, the reverse logistic with the aim to remanufacture is important to consider since the remanufacturing is a fundamental process of it. Thereafter the possible factors that can be occurred are one-time costs such as prices of machines, fixed costs such as operators’ costs and where to implement the process. The results of this research provide a possibility for companies to determine whether the remanufacturing process is economically profitable for them.
21
Smith, Robert. "A component-based layered abstraction model for software portability across autonomous mobile robots." Thesis, Queensland University of Technology, 2005. https://eprints.qut.edu.au/16406/1/Robert_Smith_Thesis.pdf.
Full textAbstract:
Today's autonomous robots come in a variety of shapes and sizes from all terrain
vehicles clambering over rubble, to robots the size of coffee cups zipping about a laboratory.
The diversity of these robots is extraordinary; but so is the diversity of the
software created to control them even when the basic tasks many robots undertake
are practically the same (such as obstacle detection, tracking, or path planning). It
would be beneficial if some reuse of these coded sub-tasks could be achieved. However,
most of the present day robot software is monolithic, very specialised and not
at all modular, which hinders the reuse and sharing of code between robot platforms.
One difficulty is that the hardware details of a robot are usually tightly woven
into the high-level controllers. When these details are not decoupled and explicitly
encapsulated, the entire code set must be revised if the robot platform changes. An
even bigger challenge is that a robot is a context-aware device. Hence, the possible
interpretations of the state of the robot and its environment vary along with its
context. For example, as the robots differ in size and shape, the meaning of concepts
such as direction, speed, and distance can change { objects that are considered far
from one robot, might seem near to a much larger robot. When designing reusable
robot software, these variable interpretations of the environment must be considered.
Similarly, so must variations in context dependent robot instructions { for example,
`move fast' has different abstractions; a `virtual robot' layer to manage the robot's platform abstractions;
and high-level abstraction components that are used to describe the state of the robot
and its environment. The prototype is able to support binary code portability
and dynamic code extensibility across a range of different robots (demonstrated on
eight diverse robot platform configurations).
These outcomes significantly ease the burden on robot software developers when
deploying a new robot (or even reconfiguring old robots) since high-level binary
controllers can be executed unchanged on different robots. Furthermore, since the
control code is completely decoupled from the platform information, these concerns
can be managed separately, thereby providing a flexible means for managing different
configurations of robots. These systems and techniques all improve the robot
software design, development, and deployment process.
Different meanings depending on the robot's size, environmental
context and task being undertaken.
What is needed is a unifying cross-platform software engineering approach for
robots that will encourage the development of code that is portable, modular and
robust. Toward this end, this research presents a complete abstraction model and
implementation prototype that contain a suite of techniques to form and manage the
robot hardware, platform, and environment abstractions. The system includes the
interfaces and software components required for hardware device and operating system abstractions; a `virtual robot' layer to manage the robot's platform abstractions;
and high-level abstraction components that are used to describe the state of the robot
and its environment. The prototype is able to support binary code portability
and dynamic code extensibility across a range of different robots (demonstrated on
eight diverse robot platform configurations).
These outcomes significantly ease the burden on robot software developers when
deploying a new robot (or even reconfiguring old robots) since high-level binary
controllers can be executed unchanged on different robots. Furthermore, since the
control code is completely decoupled from the platform information, these concerns
can be managed separately, thereby providing a flexible means for managing different
configurations of robots. These systems and techniques all improve the robot
software design, development, and deployment process.
22
Smith, Robert. "A component-based layered abstraction model for software portability across autonomous mobile robots." Queensland University of Technology, 2005. http://eprints.qut.edu.au/16406/.
Full textAbstract:
Today's autonomous robots come in a variety of shapes and sizes from all terrain vehicles clambering over rubble, to robots the size of coffee cups zipping about a laboratory. The diversity of these robots is extraordinary; but so is the diversity of the software created to control them even when the basic tasks many robots undertake are practically the same (such as obstacle detection, tracking, or path planning). It would be beneficial if some reuse of these coded sub-tasks could be achieved. However, most of the present day robot software is monolithic, very specialised and not at all modular, which hinders the reuse and sharing of code between robot platforms. One difficulty is that the hardware details of a robot are usually tightly woven into the high-level controllers. When these details are not decoupled and explicitly encapsulated, the entire code set must be revised if the robot platform changes. An even bigger challenge is that a robot is a context-aware device. Hence, the possible interpretations of the state of the robot and its environment vary along with its context. For example, as the robots differ in size and shape, the meaning of concepts such as direction, speed, and distance can change { objects that are considered far from one robot, might seem near to a much larger robot. When designing reusable robot software, these variable interpretations of the environment must be considered. Similarly, so must variations in context dependent robot instructions { for example, `move fast' has different abstractions; a `virtual robot' layer to manage the robot's platform abstractions; and high-level abstraction components that are used to describe the state of the robot and its environment. The prototype is able to support binary code portability and dynamic code extensibility across a range of different robots (demonstrated on eight diverse robot platform configurations). These outcomes significantly ease the burden on robot software developers when deploying a new robot (or even reconfiguring old robots) since high-level binary controllers can be executed unchanged on different robots. Furthermore, since the control code is completely decoupled from the platform information, these concerns can be managed separately, thereby providing a flexible means for managing different configurations of robots. These systems and techniques all improve the robot software design, development, and deployment process. Different meanings depending on the robot's size, environmental context and task being undertaken. What is needed is a unifying cross-platform software engineering approach for robots that will encourage the development of code that is portable, modular and robust. Toward this end, this research presents a complete abstraction model and implementation prototype that contain a suite of techniques to form and manage the robot hardware, platform, and environment abstractions. The system includes the interfaces and software components required for hardware device and operating system abstractions; a `virtual robot' layer to manage the robot's platform abstractions; and high-level abstraction components that are used to describe the state of the robot and its environment. The prototype is able to support binary code portability and dynamic code extensibility across a range of different robots (demonstrated on eight diverse robot platform configurations). These outcomes significantly ease the burden on robot software developers when deploying a new robot (or even reconfiguring old robots) since high-level binary controllers can be executed unchanged on different robots. Furthermore, since the control code is completely decoupled from the platform information, these concerns can be managed separately, thereby providing a flexible means for managing different configurations of robots. These systems and techniques all improve the robot software design, development, and deployment process.
23
Baig, Aftab, and Iftikhar Ahmad. "A web store based on reusable .NET components." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-13141.
Full textAbstract:
The thesis project describes the analysis, process and major factors in development of a simple component oriented Web Shop in ASP.NET. It addresses to the concepts used in the application as well as derivation of technical design and development from the concepts acquired by studying existing approaches. The report describes a brief summary of existing approaches and related technologies. It also lays the foundation of goal oriented approach by providing an overview of component based software engineering. The basic concepts for modularization were barrowed from entities identification, object models and component models pplication’s architecture is set to be a layered app roach combining the software layered architecture approach with multi tier architecture of web applications. Class models explaining the inner structure of each component have been provided and an overview of user interface pages is given to explain the application outer flow. The application sets out to prove the significance of component oriented approach as well as the support provided for it by ASP.Net. The resulting package proves to have scalable components that could be scaled for or reused in another application or in a later version of the same application.First and Final Version of our Thesis Report
SoftIn - Introducing methods and tools for software development in small and medium-sized enterprises
24
Shatnawi, Anas. "Supporting Reuse by Reverse Engineering Software Architecture and Component from Object-Oriented Product Variants and APIs." Thesis, Montpellier, 2015. http://www.theses.fr/2015MONTS140/document.
Full textAbstract:
La réutilisation est reconnue comme une démarche intéressante pour améliorer la qualité des produits et la productivité des projets logiciels. L'ingénierie des logiciels à base de composants (CBSE en anglais) et l'ingénierie des lignes de produits logiciels (SPLE en anglais) sont considérées parmi les plus importants paradigmes de réutilisation systématique. L'ingénierie à base de composants permet de développer de nouveaux systèmes logiciels par composition de briques préconstruites appelées composants. L'ingénierie des lignes de produits logiciels permet de dériver (construire) de nouveaux produits par simple sélection de leurs caractéristiques (feature en anglais). Cette dérivation est rendue possible grâce à la représentation et à la gestion de la variabilité et de la similarité des produits d'une même famille. Cependant, une des difficultés vers une large adoption de l'ingénierie des logiciels à base de composants et des lignes de produits est le coût à investir pour construire, à partir de rien, les composants et les artefacts de lignes de produits. Dans ce contexte, les travaux de cette thèse proposent de réduire ce coût par une démarche basée sur la rétro-ingénierie.La première contribution de cette thèse consiste à proposer une approche permettant d'identifier, par l'analyse d'un ensemble de variantes d'un produit logiciel orienté objet, les éléments du code source pouvant servir à l'implémentation de composants. Au contraire des approches existantes d'identification de composants basées sur l'analyse d'un seul produit, l'originalité de notre approche consiste en l'analyse de plusieurs variantes de produits en même temps. Notre objectif est l'amélioration de la réutilisabilité des composants extraits. L'évaluation expérimentale menée dans le cadre de cette thèse a montré la pertinence de cette démarche.La deuxième contribution consiste en la proposition d'une approche pour l'extraction d'une architecture à base de composants d'un ensemble de variantes d'un produit logiciel orienté objet. Il s'agit d'identifier la variabilité des composants architecturaux et la configuration architecturale. L'identification de la configuration architecturale est principalement basée sur l'utilisation de l'analyse formelle de concepts pour trouver les dépendances entre les éléments architecturaux. L'expérimentation conduite pour l'évaluation de l'approche proposée confirme la pertinence des éléments identifiés.La troisième contribution de cette thèse permet de restructurer les APIs orientées objet en composants. Nous exploitons la spécificité des classes des APIs d'être conçues pour être utilisées par des applications clientes pour identifier ces composants. Le code source de ces APIs et celui de leurs applications clientes sont analysés afin d'identifier des groupes de classes qui peuvent servir à l'implémentation de composants à extraire. L'identification de ces groupes de classes est basée sur l'analyse des liens structurels entre ces classes et sur la probabilité que ces classes soient utilisées ensemble par les applications clientes. Nous montrons à travers les résultats expérimentaux que la restructuration des API orientées objet en composants facilite la réutilisation et la compréhension des éléments de ces APIsIt is widely recognized that software quality and productivity can be significantly improved by applying a systematic reuse approach. In this context, Component-Based Software Engineering (CBSE) and Software Product Line Engineering (SPLE) are considered as two important systematic reuse paradigms. CBSE aims at composing software systems based on pre-built software components and SPLE aims at building new products by managing commonalty and variability of a family of similar software. However, building components and SPL artifacts from scratch is a costly task. In this context, our dissertation proposes three contributions to reduce this cost.Firstly, we propose an approach that aims at mining reusable components from a set of similar object-oriented software product variants. The idea is to analyze the commonality and the variability of product variants, in order to identify pieces of code that may form reusable components. Our motivation behind the analysis of several existing product variants is that components mined from these variants are more reusable for the development of new software products than those mined from single ones. The experimental evaluation shows that the reusability of the components mined using our approach is better than those mined from single software.Secondly, we propose an approach that automatically recovers the component-based architecture of a set of object-oriented software product variants. Our contribution is twofold: the identification of the architectural component variability and the identification of the configuration variability. The configuration variability is based on the identification of dependencies between the architectural elements using formal concept analysis. The experimental evaluation shows that our approach is able to identify the architectural variability.Finally, we propose an approach that aims at restructuring object-oriented APIs as component-based ones. This approach exploits specificity of API entities by statically analyzing the source code of both APIs and their software clients to identify groups of API classes that are able to form components. Our assumption is based on the probability of classes to be reused together by API clients on the one hand, and on the structural dependencies between classes on the other hand. The experimental evaluation shows that structuring object-oriented APIs as component-based ones improves the reusability and the understandability of these APIs
25
Unhale, Sudeep Prabhakar. "An environment for specifying and executing adaptable software components." Link to electronic thesis, 2003. http://www.wpi.edu/Pubs/ETD/Available/etd-0427103-145102.
Full textAbstract:
Thesis (M.S.)--Worcester Polytechnic Institute.Keywords: component adaptations; active interfaces; blackbox component adaptation; component specification language; software reuse. Includes bibliographical references.
26
Rossi, Ana Claudia. "Representação do componente de software na FARCSoft: ferramenta de apoio à reutilização de componentes de software." Universidade de São Paulo, 2004. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-03062004-101200/.
Full textAbstract:
Atualmente, as organizações estão cada vez mais dependentes de sistemas de informação para a realização de seus negócios. Com isso, uma das preocupações, na área de desenvolvimento de software, é a obtenção cada vez mais rápida de sistemas que atendam as necessidades atuais e que sejam flexíveis para acompanhar as mudanças de tecnologia e práticas de negócio. A reutilização de componentes de software tem sido considerada uma das formas para obter redução dos custos e do tempo de desenvolvimento e aumento da produtividade e da qualidade do produto de software. A implantação da reutilização de componentes é baseada em três elementos principais que consistem de um processo de desenvolvimento voltado para reutilização, de uma ferramenta adequada e de uma cultura de projeto. A ferramenta, por sua vez, deve ter a capacidade de armazenar os componentes e de fornecer recursos para uma recuperação eficiente. O objetivo deste trabalho é definir uma representação de componentes em um repositório, a qual permita armazenar diferentes tipos de componentes de software. Para isso, foi especificada a Ferramenta de Apoio à Reutilização de Componentes de Software, denominada de FARCSoft, que deve fornecer suporte à reutilização de componentes de software. Esta ferramenta apresenta recursos para armazenar, gerenciar, buscar e recuperar os componentes do seu repositório. A capacidade de representação foi avaliada por meio de um conjunto de componentes de tipos, porte e tecnologia diversos, os quais foram modelados e catalogados.Nowadays, organizations increasingly depend on information systems to carry out their business. Thus, one of the preoccupations in the software development area is the need to obtain systems faster and faster, attending to current needs and sufficiently flexible to accompany changes in technology and business practices. Software component reuse has been considered one of the ways to reduce costs and development time and increase productivity and software quality. The implantation of component reuse is based on three main elements, which consist in a development process oriented towards reuse, an adequate tool and a project culture. The tool, in turn, must be able to store the components and to supply resources for the sake of efficient recovery. This study aims to define a component representation in a repository, which allows for the storage of different kinds of software components. For this purpose, a Software Component Reuse Support Tool was specified, called FARCSoft, which should support the reuse of software components. This tool presents resources to store, manage, search and recover the components of a repository. Representation capacity was evaluated by means of a set of components with different types, sizes and technologies, which were modeled and catalogued.
27
Karlsson, Daniel. "Verification of Component-based Embedded System Designs." Doctoral thesis, Linköping : Department of Computer and Information Science, Linköping University, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-7473.
Full text
28
Nam, Jaechang. "Component Reusability Analysis for Exchanging Electronic Health Records." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4058.
Full textAbstract:
As Information Communication Technologies (ICTs) are growing, there have been ceaseless efforts to develop a National Health Information Infrastructure (NHII). One of the challenges in constructing a NHII is concerned with the management of Electronic Health Records (EHRs). In particular, exchanging EHRs is an important factor in establishing interoperability within a NHII, and the reusability of the functionality for exchanging EHRs is one of major solutions to construct an NHII. In this study, we obtain several component models, and conduct empirical studies to validate the component models in terms of component reusability. Using HL7 CDA (Health Level 7 Clinical Document Architecture) as an EHR standard, we implemented three prototypes of the EHR Exchanger based on JavaBeans, the exogenous connectors and the mediator connector respectively. As shown in the experiment results, the reuse approach using a mediator connector leads to better component reusability in terms of external dependency, total coupling between objects (CBO), additional lines of codes (LOC), and performance. Thus, we believe that the reuse approach using a mediator connector yields many benefits in terms of component reusability for the EHR Exchanger implementation.
29
Hudgins, B. Gene, and Jason Lucas. "THE CTEIP TEST AND TRAINING ENABLING ARCHITECTURE, TENA, AN IMPORTANT COMPONENT IN REALIZING DOD TEST AND TRAINING RANGE INTEROPERABILITY." International Foundation for Telemetering, 2005. http://hdl.handle.net/10150/604793.
Full textAbstract:
ITC/USA 2005 Conference Proceedings / The Forty-First Annual International Telemetering Conference and Technical Exhibition / October 24-27, 2005 / Riviera Hotel & Convention Center, Las Vegas, NevadaWhile military asset testing and training might be seen as complementary in supporting military prepareness, they cannot complement each other without an effective and efficient method of distributing data laterally across geographically separated data gathering, analysis, and display systems. This cost-effective integration of range data and telemetry resources is critical to ensuring the war worthiness of today’s advanced weapon systems such as the Joint Strike Fighter and the sensor and weapon platforms such as the highly sophisticated unmanned vehicles that are beginning to populate the air, land, and sea areas of operations. To ensure the advantages of range interoperability are available across the DoD Test and Training ranges, a Central Test and Evaluation Program (CTEIP) project has developed and is refining the Test and Training Enabling Architecture (TENA). The core of TENA is the TENA Common Infrastructure, including the TENA Middleware and TENA Repository. The TENA Middleware is the high-performance, real-time, low-latency communication infrastructure used by range instrumentation software and tools during execution of a range event. The TENA Object Model enables semantic interoperability among range resource applications by encoding the information to be communicated among those range applications. It may be seen as a range community-wide set of interface and protocol definitions encapsulated in an object-oriented design. The TENA tools, utilities, and gateways assist the user in creating and managing an integration of range resources, as well as in optimizing the TENA Common Infrastructure. TENA has proven to be a critical enabler of distributed live exercises to include the U.S. Joint Forces Command’s Millennium Challenge 2002, two major Joint National Training Capability exercises in 2004, Cope Thunder 04-02, and Joint Roving Sands/Red Flag 2005. TENA, as integral part of range data systems, has become an important component in the realization of range interoperability.
30
Dunlap, Ralph S. "Effective reuse of coupling technologies for Earth System Models." Diss., Georgia Institute of Technology, 2013. http://hdl.handle.net/1853/48943.
Full textAbstract:
Designing and implementing coupled Earth System Models (ESMs) is a challenge for climate scientists and software engineers alike. Coupled models incorporate two or more independent numerical models into a single application, allowing for the simulation of complex feedback effects. As ESMs increase in sophistication, incorporating higher fidelity models of geophysical processes, developers are faced with the issue of managing increasing software complexity.
Recently, reusable coupling software has emerged to aid developers in building coupled models. Effective reuse of coupling infrastructure means increasing the number of coupling functions reused, minimizing code duplication, reducing the development time required to couple models, and enabling flexible composition of coupling infrastructure with existing constituent model implementations. Despite the widespread availability of software packages that provide coupling infrastructure, effective reuse of coupling technologies remains an elusive goal: coupling models is effort-intensive, often requiring weeks or months of developer time to work through implementation details, even when starting from a set of existing software components. Coupling technologies are never used in isolation: they must be integrated with multiple existing constituent models to provide their primary services, such as model-to-model data communication and transformation. Unfortunately, the high level of interdependence between coupling concerns and scientific concerns has resulted in high interdependence between the infrastructure code and the scientific code within a model’s implementation. These dependencies are a source of complexity which tends to reduce reusability of coupling infrastructure.
This dissertation presents mechanisms for increasing modeler productivity based on improving reuse of coupling infrastructure and raising the level of abstraction at which modelers work. This dissertation argues that effective reuse of coupling technologies can be achieved by decomposing existing coupling technologies into a salient set of implementation-independent features required for coupling high-performance models, increasing abstraction levels at which model developers work, and facilitating integration of coupling infrastructure with constituent models via component-based modularization of coupling features. The contributions of this research include:
(1) a comprehensive feature model that identifies the multi-dimensional design space of coupling technologies used in high-performance Earth System Models,
(2) Cupid, a domain-specific language and compiler for specifying coupling configurations declaratively and generating their implementations automatically, and
(3) Component-based Coupling Operators (CC-Ops), a modular approach to code reuse of coupling infrastructure based on component technologies for high-performance scientific settings.
The Cupid domain-specific language is evaluated by specifying a coupling configuration for an example fluid dynamics model and measuring the amount of code generated by the Cupid compiler compared to a hand coded version. The CC-Op approach is evaluated by implementing several CC-Ops using an existing high-performance component framework and measuring performance in terms of scalability and overhead.
31
Inam, Rafia. "Hierarchical scheduling for predictable execution of real-time software components and legacy systems." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-26548.
Full textAbstract:
This dissertation presents techniques to achieve predictable execution of coarse-grained software components and for preservation of temporal properties of components during their integration and reuse. The dissertation presents a novel concept runnable virtual node (RVN) which interaction with the environment is bounded both by a functional and a temporal interface, and the validity of its internal temporal behaviour is preserved when integrated with other components or when reused in a new environment. The realization of RVN exploits techniques for hierarchical scheduling to achieve temporal isolation, and the principles from component-based software-engineering to achieve functional isolation. The proof-of-concept case studies executed on a micro-controller demonstrate the preserving of real-time properties within software components for predictable integration and reusability in a new environment, in both hierarchical scheduling and RVN contexts. Further, a multi-resource server (MRS) is proposed and implemented to enable predictable execution when composing multiple real-time components on a COTS multicore platform. MRS uses resource reservation for both CPU-bandwidth and memory-bus bandwidth to bound the interferences between tasks running on the same core, as well as, between tasks running on different cores. The later could, without MRS, interfere with each other due to contention on a shared memory-bus and memory. The results indicated that MRS can be used to "encapsulate" legacy systems and to give them enough resources to fulfill their purpose. In the dissertation, the compositional schedulability analysis for MRS is also provided and an experimental study is performed to bring insight on the correlation between the server budgets. We believe that the proposed approaches enable a faster software integration and support legacy reuse and that this work transcend the boundaries of software engineering and real-time systems.PPMSched
PROGRESS
32
Harish, Acharya Maniyoor, and Suppatarachai Sudsawat. "Improving the time frame reduction for reuse of roof rack components in cars using Case-based reasoning." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Produktutveckling - Datorstödd konstruktion, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-19289.
Full textAbstract:
Now a days where technological advancements are growing at a rapid pace, it has become a common norm for all the manufacturing companies to be abreast with these advancements for being competitive in market. This thesis deals with development of one such common norm for one of the products (Roof rack component) for company Thule. The main aim of the thesis is to curtail the products lead time to market and this was achieved by using an artificial intelligence technique i.e., Case-based reasoning (CBR). Roof rack component which is mounted on car roof is mainly constituted by two parts foot pad and bracket, this thesis main interest was concerned with only brackets and its geometry. This thesis is based on contemplating the already implemented concepts in this context, designer requirements and exploring better solutions. The methods of implementation adopted here was using CBR concept which is based on indexing , retrieve, adapt, review, retain and employing these concepts in form of an algorithm. The concept for developing the algorithm was based on Iterative closest point (ICP) approach which emphasise on assigning lower weight to pairs with greater point to point distance. The results portrayed are with respect to geometry and also with respect to application interface developed, which both together provides us a better solution.
33
Seriai, Abderrahmane. "Rendre réutilisables des composants extraits d’une application orientée-objets." Thesis, Lorient, 2015. http://www.theses.fr/2015LORIS360.
Full textAbstract:
La réutilisation est l’un des principaux objectifs de l’ingénierie logicielle. De nombreux concepts et mécanismes associés ont été proposés pour promouvoir la réutilisation des fonctionnalités offertes par le logiciel. L’ingénierie logicielle à base de composants (CBSE) est l’une des plus importantes approches qui ont été proposées pour augmenter la réutilisation des logiciels.Ainsi, plusieurs travaux ont été réalisés afin de restructurer les systèmes existants en systèmes à base de composants. Néanmoins, presque toutes les approches proposées visent plus l’identification des composants que l’identification des parties ré-utilisables. Ainsi, elles sont limitées à identifier des composants, correspondant à des ensembles de classes, permettantl’extraction d’une vue architecturale de l’ancien système. Mais, les composants identifiés ne peuvent pas être implantés avec un modèle concret de composants.Dans cette thèse, nous proposons deux approches pour améliorer la réutilisation des composants extraits, mais aussi faciliter la compréhension de l’architecture sous-jacente. Ainsi, la première approche vise l’identification des interfaces du composant extrait en fonction de ses interactions avec les autres composants. La seconde a pour objectif de rendre possible l’implantation des composants extraits avec un modèle concret de composants. Ceci est fait en utilisant des instances de classes (objets) qui composent les composants extraits pour déduire des instances possibles de composant.L’évaluation des approches proposées par une étude empirique montre que i) l’ensemble des interfaces identifiées correspondent aux différents aspects fonctionnels des composants extraits. ii) et, qu’il est possible d’implanter, dans un modèle concret de composants, les composants extraits sans modifier le comportement de l’applicationReuse is one of the main goals of software engineering. Many concepts and associated mechanisms were proposed to promote the reuse of features offered by the software. Component based software engineering (CBSE) is one of the important approaches which was proposed to increase the software reuse. Thus, several works were conducted in order to restructure legacy systems into component-based ones. Nevertheless, almost all proposed approaches are more targeted for component identification than for the identification of reusable parts. Thus, they are limited to identify components, corresponding to sets of classes, allowing an extraction of the architectural view of the legacy system. But, the identified components can not be easily implemented in a concrete component model.In this thesis, we propose two approaches to improve the reusability of the extracted components and by the way facilitate the comprehension of the underlying architecture. Thus, the first approach aims the identification of the extracted component’s interfaces according to its interactions with the other components. The second one aims to make extracted components implementable within a concrete component model. This is done by using class instances (objects) that compose the extracted components to infer possible component instances.The evaluation of the proposed approaches via an empirical study showed that i) overall the identified interfaces correspond to the different functional aspects of the extracted components. ii) and, that is possible to implement, within a concrete component model, the extracted components without altering the behavior of the application
34
Santos, Michael Shuenck dos. "X-ARM: um modelo de representa??o de artefatos de software." Universidade Federal do Rio Grande do Norte, 2006. http://repositorio.ufrn.br:8080/jspui/handle/123456789/18056.
Full textAbstract:
Made available in DSpace on 2014-12-17T15:48:02Z (GMT). No. of bitstreams: 1
MichaelSS.pdf: 1470554 bytes, checksum: 016748ab8192abef9067fea20f51d077 (MD5)
Previous issue date: 2006-10-16A great challenge of the Component Based Development is the creation of mechanisms to facilitate the finding of reusable assets that fulfill the requirements of a particular system under development. In this sense, some component repositories have been proposed in order to answer such a need. However, repositories need to represent the asset characteristics that can be taken into account by the consumers when choosing the more adequate assets for their needs. In such a context, the literature presents some models proposed to describe the asset characteristics, such as identification, classification, non-functional requirements, usage and deployment information and component interfaces. Nevertheless, the set of characteristics represented by those models is insufficient to describe information used before, during and after the asset acquisition. This information refers to negotiation, certification, change history, adopted development process, events, exceptions and so on. In order to overcome this gap, this work proposes an XML-based model to represent several characteristics, of different asset types, that may be employed in the component-based development. Besides representing metadata used by consumers, useful for asset discovering, acquisition and usage, this model, called X-ARM, also focus on helping asset developers activities. Since the proposed model represents an expressive amount of information, this work also presents a tool called X-Packager, developed with the goal of helping asset description with X-ARM
O Desenvolvimento Baseado em Componentes tem como grande desafio a cria??o de mecanismos que facilitem a identifica??o de assets reus?veis que satisfa?am os requisitos de sistemas particulares sob desenvolvimento. Neste sentido, reposit?rios de componentes t?m sido propostos como meios para se atender esta necessidade. Por?m, reposit?rios precisam representar as caracter?sticas de assets que possam ser levadas em considera??o pelos consumidores quando da escolha dos assets mais adequados ?s suas necessidades. Neste contexto, a literatura apresenta alguns modelos que foram propostos com a finalidade de descrever as caracter?sticas de assets, tais como identifica??o, classifica??o, requisitos n?o funcionais, informa??es de implanta??o e uso, arquivos que comp?em os assets, e interfaces de componentes. No entanto, o conjunto de caracter?sticas representadas por estes modelos ? insuficiente para descrever diversas informa??es usadas antes, durante e depois da aquisi??o dos assets, dentre as quais pode-se destacar informa??es de negocia??o e certifica??o, hist?rico de mudan?as, processo de desenvolvimento usado, eventos, exce??es. De forma a solucionar tais defici?ncias, este trabalho apresenta um modelo baseado em XML para a representa??o de diversas caracter?sticas, de diversos tipos de assets, que possam ser empregadas no desenvolvimento baseado em componentes. O modelo proposto, denominado X-ARM, fornece informa??es usadas n?o apenas pelos consumidores na identifica??o, aquisi??o e uso de assets, mas tamb?m para apoiar as atividades dos desenvolvedores de assets. Dado que o modelo proposto representa uma expressiva quantidade de informa??es, este trabalho tamb?m apresenta uma ferramenta chamada X-Packager, desenvolvida com o objetivo de auxiliar a descri??o de assets com X-ARM
35
An, Qiuyan. "Retrieving function components from a reuse library." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1998. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape10/PQDD_0014/MQ52505.pdf.
Full text
36
Cooper, Daniel. "Reuse of steel and aluminium without melting." Thesis, University of Cambridge, 2014. https://www.repository.cam.ac.uk/handle/1810/245141.
Full textAbstract:
Carbon dioxide emissions must be dramatically reduced to avoid the potentially dangerous effects of climate change. The steel and aluminium industries produce large amounts of carbon dioxide, accounting for 6% of anthropogenic emissions. Previous studies have shown that in these industries there is limited scope for further improvements in energy efficiency. Material efficiency strategies can, however, further reduce emissions. This thesis focuses on materially efficient reuse without melting. A scoping study of current reuse found three opportunities, an examination of which forms the basis of this thesis: reusing components at end of product life; extending the lifespan of products; and reusing manufacturing scrap. The opportunity to reuse components has received little attention to date and there is no clearly defined set of strategies or barriers to enable assessment of appropriate component reuse; neither is it possible to predict future levels of reuse. This thesis presents a global assessment of the potential for reusing steel and aluminium components. A combination of top-down and bottom-up analyses is used to allocate the final destinations of current global steel and aluminium production to final products. A substantial catalogue has been compiled for these products characterizing key features of steel and aluminium components including design specifications, requirements in use, and current reuse patterns. To estimate the fraction of end-of-life metal components that could be reused for each product, the catalogue formed the basis of a set of semi-structured interviews with industrial experts. The results suggest that approximately 30% of steel and aluminium used in current products could be reused. Barriers against reuse are examined, prompting recommendations for redesign that would facilitate future reuse. In order to understand how product lifespans can be extended it must first be understood why products are replaced. A simple framework with which to analyse failure is applied to the products that dominate steel use, finding that they are often replaced because a component/sub-assembly becomes degraded, inferior, unsuitable or worthless. In light of this, four products, which are representative of high steel content products in general, are analysed at the component level, determining profiles of cumulative steel mass over the lifespan of each product. The results show that the majority of the steel components are underexploited – still functioning when the product is discarded. In particular, the potential lifespan of the steel-rich structure is typically much greater than its actual lifespan. Evidence from twelve case studies, in which product or component life has been increased, is used to tailor life-extension strategies to each reason for product failure, providing practical guidelines for designers. There is currently no commercial method of reusing small manufacturing scrap; however, previous research has demonstrated that extruded profiles can be created from small clean aluminium scrap, the scrap fragments solid-state welding together when extruded. In order to evaluate potential applications for these profiles four case studies are conducted in collaboration with aluminium producers and product manufacturers. It was found that strong and formable profiles could be produced from scrap. However, contaminated scrap sources, unreliable bonding and poor surface quality limited their potential for commercial use. No model exists for solid-state weld strength that is applicable to scrap extrusion. This prevents optimisation of the existing extrusion process and the development of new, potentially better, processes. Subsequently, this thesis presents a new model of weld strength as a function of relevant deformation parameters. The model is evaluated using a new experiment in which the deformation conditions can be varied independently. The experiments establish the basic relationships between deformation parameters and weld strength. The model correctly predicts these trends with predicted weld strengths typically lying within the experimental error range. The technical assessment of reuse presented in this thesis demonstrates the scope of potential change. If implemented, the opportunities presented would greatly increase the reuse of steel and aluminium, reducing the emissions emitted from liquid metal production in conventional recycling.
37
Motta, Enrico. "Reusable components for knowledge modelling." Thesis, Open University, 1998. http://oro.open.ac.uk/57879/.
Full textAbstract:
In this work I illustrate an approach to the development of a library of problem solving components for knowledge modelling. This approach is based on an epistemological modelling framework, the Task/Method/Domain/Application (TMDA) model, and on a principled methodology, which provide an integrated view of both library construction and application development by reuse. The starting point of the proposed approach is given by a task ontology. This formalizes a conceptual viewpoint over a class of problems, thus providing a task-specific framework, which can be used to drive the construction of a task model through a process of model-based knowledge acquisition. The definitions in the task ontology provide the initial elements of a task-specific library of problem solving components. In order to move from problem specification to problem solving, a generic, i.e. taskindependent, model of problem solving as search is introduced, and instantiated in terms of the concepts in the relevant task ontology, say T. The result is a task-specific, but method-independent, problem solving model. This generic problem solving model provides the foundation from which alternative problem solving methods for a class of tasks can be defined. Specifically, the generic problem solving model provides i) a highly generic method ontology, say M; ii) a set of generic building blocks (generic tasks), which can be used to construct task-specific problem solving methods; and iii) an initial problem solving method, which can be characterized as the most generic problem solving method, which subscribes to M and is applicable to T. More specific problem solving methods can then be (re-)constructed from the generic problem solving model through a process of method/ontology specialization and method-to-task application. The resulting library of reusable components enjoys a clear theoretical basis and provides robust support for reuse. In the thesis I illustrate the approach in the area of parametric design.
38
Anguswamy, Reghu. "Factors Affecting the Design and Use of Reusable Components." Diss., Virginia Tech, 2013. http://hdl.handle.net/10919/23674.
Full textAbstract:
Designing software components for future reuse has been an important area in software engineering. A software system developed with reusable components follows a "with" reuse process while a component designed to be reused in other systems follows a "for" reuse process. This dissertation explores the factors affecting design for reuse and design with reusable components through empirical studies. The studies involve Java components implementing a particular algorithm, a stemming algorithm that is widely used in the conflation domain. The method and empirical approach are general and independent of the programming language. Such studies may be extended to other types of components, for example, components implementing data structures such as stacks, queues etc. Design for reuse: In this thesis, the first study was conducted analyzing one-use and equivalent reusable components for the overhead in terms of component size, effort required, number of parameters, and productivity. Reusable components were significantly larger than their equivalent one-use components and had significantly more parameters. The effort required for the reusable components was higher than for one-use components. The productivity of the developers was significantly lower for the reusable components compared to the one-use components. Also, during the development of reusable components, the subjects spent more time on writing code than designing the components, but not significantly so. A ranking of the design principles by frequency of use is also reported. A content analysis performed on the feedback is also reported and the reasons for using and not using the reuse design principles are identified. A correlation analysis showed that the reuse design principles were, in general, used independently of each other.
Design with reuse: Through another empirical study, the effect of the size of a component and the reuse design principles used in building the component on the ease of reuse were analyzed. It was observed that the higher the complexity the lower the ease of reuse, but the correlation is not significant. When considered independently, four of the reuse design principles: well-defined interface, clarity and understandability, generality, and separate concepts from content significantly increased the ease of reuse while commonality and variability analysis significantly decreased the ease of reuse, and documentation did not have a significant impact on the ease of reuse. Experience in the programming language had no significant relationship with the reusability of components. Experience in software engineering and software reuse showed a relationship with reusability but the effect size was small. Testing components before integrating them into a system was found to have no relationship with the reusability of components. A content analysis of the feedback is presented identifying the challenges of components that were not easy to reuse. Features that make a component easily reusable were also identified. The Mahalanobis-Taguchi Strategy (MTS) was employed to develop a model based on Mahalanobis Distance to identify the factors that can detect if a component is easy to reuse or not. The identified factors within the model are: size of a component, a set of reuse design principles (well-defined interface, clarity and understandability, commonality and variability analysis, and generality), and component testing.
Ph. D.
39
Niu, Hongjian. "Execution-based retrieval of object-oriented components for reuse." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1999. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape7/PQDD_0012/MQ52621.pdf.
Full text
40
Schiroky, Alex Marracci. "Modelagem e prototipação de um repositório extensível para componentes de software." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2002. http://hdl.handle.net/10183/11158.
Full textAbstract:
Várias ferramentas de desenvolvimento utilizam mecanismos para centralizar/gerenciar código compartilhado entre diferentes desenvolvedores ou equipes de desenvolvimento. Estes repositórios geralmente deixam muito a desejar em relação aos serviços que oferecem, não só aos desenvolvedores, mas também aos usuários de sistemas já desenvolvidos, que desejam ter atualizações e correções constantes em seus aplicativos. Surge então a necessidade de disponibilizar esses recursos em um ambiente de trabalho realmente cooperado. Este trabalho propõe a modelagem de um repositório de componentes de software, formado por uma área de armazenamento centralizada comum aos desenvolvedores, e com capacidade de gerenciar componentes e agregar serviços extras, administrando seu ciclo de vida de modo integrado. Para tal, várias tecnologias baseadas em Java foram integradas, tais como as seguintes API's: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) e Java Database Connection (JDBC).Para que o modelo aqui proposto possua um nível de funcionalidade adequado, são fornecidos vários serviços pelo repositório, atendendo assim às expectativas tanto de desenvolvedores, como dos usuários finais. Dentre outros, são providos os seguintes serviços: Serviço de Descrição, Serviço de Histórico, Serviço de Controle de Versões, Serviço de Teste OO, Serviço de Padrões de Projeto e Serviço de Invalidação de Componentes.Software development tools commonly use mechanisms for storing/managing code shared among different developers or development teams. These repositories generally are very poor in relation to the services they provide to developers and also to the users of already developed systems which need to make constant updates and corrections on their applications. There is a need to supply supporting services to software integration through a really cooperated development environment. This work considers the modeling of a software component repository comprising a common storage area to be accessed by developers, possessing capacity to manage components and to add extra services, and managing the development life cycle in an integrated mode. To accomplish this model, some technologies based on Java have been integrated, namely: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) and Java Database Connection (JDBC). For the model considered here to have an adjusted level of functionality, some repository services are supplied so assuring the expectations of developers and final users. Among the services provided, the following must be mentioned: Description Service, History Service, Version Control Service, OO Test Service, Design Patterns Service and Components Invalidation Service.
41
Pohthong, Amnart. "Design strategies for employing reusable software components." Thesis, Keele University, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.311736.
Full text
42
Saraiva, Tatiana Santos. "Diretrizes de projeto para possibilitar a desconstrução de edificações e seus componentes." Universidade Federal de Juiz de Fora (UFJF), 2013. https://repositorio.ufjf.br/jspui/handle/ufjf/2385.
Full textAbstract:
Submitted by Renata Lopes (renatasil82@gmail.com) on 2016-09-06T11:54:20Z
No. of bitstreams: 1
tatianasantossaraiva.pdf: 1079853 bytes, checksum: d1b7934865c40684f66047cc204e98ed (MD5)Approved for entry into archive by Diamantino Mayra (mayra.diamantino@ufjf.edu.br) on 2016-09-06T11:57:02Z (GMT) No. of bitstreams: 1 tatianasantossaraiva.pdf: 1079853 bytes, checksum: d1b7934865c40684f66047cc204e98ed (MD5)
Made available in DSpace on 2016-09-06T11:57:02Z (GMT). No. of bitstreams: 1 tatianasantossaraiva.pdf: 1079853 bytes, checksum: d1b7934865c40684f66047cc204e98ed (MD5) Previous issue date: 2013-02-28
Este trabalho discute a importância das diretrizes de projeto para a desconstrução de edificações com o intuito de, entre outros benefícios, reduzir o impacto ambiental e o custo gerado pelo setor de construção civil, bem como o aumento da vida útil do edifício e seus componentes. Assim, este estudo examina a necessidade da utilização destas diretrizes na fase de concepção do projeto, considerando que esta é a etapa crucial para a tomada de decisões tais como a escolha de materiais, métodos e processos de construção. Para que isso ocorra, alguns princípios devem ser observados, tais como a durabilidade e a redução de tipos dos materiais e componentes, a adaptabilidade da planta a outras funções, a preferência por conexões mecânicas, facilidade de acesso a todos os componentes e a identificação de materiais, entre outros aspectos. O levantamento destes princípios foi feito a partir da análise de literatura específica no assunto. Após a comparação dos resultados levantados, estes princípios foram tabulados e aplicados em análises a projetos arquitetônicos publicados no ano de 2012 em revistas nacionais do setor. Após concluir que, pela análise dos projetos em si, dos manuais existentes na literatura e pelo fato de que os arquitetos brasileiros parecem não estar preocupados com a descontrução em suas obras, foram propostos princípios de projeto para desconstrução adequados ao contexto da produção arquitetônica brasileira.
This work discusses the importance of design guidelines for the deconstruction in order to, among other benefits, reduce environmental impact and cost generated by the construction industry, as well as increasing the lifetime of the building and its components. Thus, this study examines the need to use these guidelines in the conceptual stage of the project, considering that is a crucial step for making decisions such as the choice of materials, construction methods and processes. For this to occur, certain requirements must be observed, such as durability and reduced types of materials and components, the adaptability of the plant to other functions, the preference for mechanical connections, easy access to all components and materials identification, among other things. The survey was done of these principles through the analysis of specific literature on the subject. After comparing the results collected, these principles were tabulated and applied in analysis of architectural projects published in national magazines sector, in 2012. After completing that, by analyzing the projects themselves, the existing manual in literature and the fact that the Brazilian architects do not seem to be concerned with deconstruction in his works, were proposed design principles for deconstruction appropriate to the context of architectural production in Brazil.
43
Shen, Yu. "Concept-based retrieval of object-oriented class components for software reuse." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 2000. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape3/PQDD_0018/MQ52662.pdf.
Full text
44
Alkazemi, Basem Yousef. "Exploiting the architectural characteristics of software components to improve software reuse." Thesis, University of Newcastle Upon Tyne, 2009. http://hdl.handle.net/10443/1763.
Full textAbstract:
Software development is a costly process for all but the most trivial systems. One of the commonly known ways of minimizing development costs is to re-use previously built software components. However, a significant problem that source-code re-users encounter is the difficulty of finding components that not only provide the functionality they need but also conform to the architecture of the system they are building. To facilitate finding reusable components there is a need to establish an appropriate mechanism for matching the key architectural characteristics of the available source-code components against the characteristics of the system being built. This research develops a precise characterization of the architectural characteristics of source-code components, and investigates a new way to describe how appropriate components for re-use can be identified and categorized.
45
Ferlander, Matilda, and Wedin Ellinor. "Reuse in Demolition Projects : A Systematic Multicriteria Approach to Rank andOptimize the Reuse of Building Components in Demolition Projects." Thesis, KTH, Fastigheter och byggande, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-298262.
Full textAbstract:
The waste framework directive from the European Commission states that 70 percent of allconstruction- and demolition waste (CDW) should be reused or recycled. In Sweden during theyear of 2018, 52,1 percent of the generated CDW was reused or recycled, but a report fromAvfall Sverige showed that reuse only accounted for small fractions of this. According to theEU's waste hierarchy, waste reduction followed by reuse are the most desirable ways to handlewaste. Research for how to reuse CDW is therefore considered an interesting and relevant topicfor research to help achieve the goal of the waste framework directive. The purpose of this master thesis was to further develop a Multi Criteria Analysis (MCA)model which was applied on different building components to evaluate how well suited theywere for reuse considering; (1) financial return, (2) environmental impact, (3) energyconsumption and (4) external aspects. The study was performed as a case study and the appliedmethods within the case study were interviews, a survey as well as the MCA model. To estimateaspects one to three of the MCA model, the theoretical framework consisted of a Cost BenefitAnalysis (CBA) and a Life Cycle Analysis (LCA) in accordance with the European standardEN15978. The fourth aspect was evaluated with help of a survey to assess qualitativedimensions of reuse. The study concluded that there are many challenges related to reuse in demolition projects.Some major challenges identified were the limited time frames, absence of competence andexperience among actors as well as logistical challenges. According to the results from theMCA model, there is a difference in how well suited the studied components were for reuse.The two most beneficial components to reuse out of the investigated ones in the case studywere crushed concrete and aluminum doors. It was also concluded that the MCA model issuitable to apply in this component specific context.Avfallsdirektivet från Europeiska kommissionen säger att 70 procent av allt bygg- ochrivningsavfall (CDW) ska återanvändas eller återvinnas. I Sverige under året 2018återanvändes eller återvanns 52,1 procent av den totala mängden genererad CDW. En rapportfrån Avfall Sverige visade dock att återanvändning endast stod för små andelar av dessa 52,1procent. Enligt EU:s avfallshierarki är avfallsminimering följt av återanvändning de mestönskvärda metoderna för hantering av avfall. För att uppnå målet i avfallsdirektivet är studierkring återbruk av CDW ett intressant och relevant ämne. Syftet med detta examensarbete var att vidareutveckla en MCA-modell (Multi CriteriaAnalysis) som tillämpades på olika byggkomponenter för att utvärdera hur lämpliga de var föråteranvändning. Fyra aspekter togs i beaktning i modellen, nämligen (1) finansiell avkastning,(2) miljöpåverkan, (3) energiförbrukning och (4) externa aspekter. Studien utfördes som enfallstudie och de tillämpade metoderna inom fallstudien var intervjuer, en enkät samt utförandetav MCA-modellen. Det teoretiska ramverket för att uppskatta aspekterna ett till tre i MCAmodellenvar en kostnadsnyttoanalys (CBA) och en livscykelanalys (LCA) som utfördes ienlighet med den europeiska standarden EN15978. Den fjärde aspekten utvärderades med hjälpav en enkät för att bedöma de kvalitativa dimensionerna av återanvändning. Slutsatsen av studien var att det finns många utmaningar relaterade till återanvändning irivningsprojekt. Några stora utmaningar som identifierats var begränsade tidsramar, avsaknadav kompetens och erfarenhet bland aktörer samt logistiska utmaningar. Enligt resultaten frånMCA-modellen finns det en skillnad i hur väl lämpade de studerade komponenterna var föråteranvändning. De två mest fördelaktiga komponenterna att återanvända av de undersökta ifallstudien var krossad betong och aluminiumdörrar. Vidare drogs slutsatsen att MCAmodellenär lämplig att använda i detta komponentspecifika sammanhang.
46
Sanches, Mauricio Gruhn. "Um estudo sobre os riscos inerentes a implantação do reuso de componentes no processo de desenvolvimento de software." [s.n.], 2005. http://repositorio.unicamp.br/jspui/handle/REPOSIP/276310.
Full textAbstract:
Orientador: Ana Cervigni GuerraDissertaçã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
47
BURÉGIO, Vanilson André de Arruda. "Specification, design and implementation of a reuse repository." Universidade Federal de Pernambuco, 2006. https://repositorio.ufpe.br/handle/123456789/2641.
Full textAbstract:
Made available in DSpace on 2014-06-12T15:59:51Z (GMT). No. of bitstreams: 2
arquivo5652_1.pdf: 2564164 bytes, checksum: 6b08baa8253889819823661c59e9a6a0 (MD5)
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2006A disciplina de Reuso de Software tem crescido em importância, tornando-se uma ferramenta estratégica para empresas que almejam um aumento de produtividade, a obtenção de baixos custos e a alta qualidade dos seus produtos. Porém, antes de obtermos as vantagens inerentes ao reuso, é preciso termos mecanismos hábeis a fim de facilitar o armazenamento, a busca, a recuperação e o gerenciamento dos artefatos reusáveis. Nesse contexto, encaixa-se a idéia de repositórios de reuso. Um repositório de reuso pode ser entendido como uma base preparada para o armazenamento e a recuperação de componentes. O mesmo pode ser visto também, como um grande facilitador, que atua como suporte aos engenheiros de software e outros usuários no processo de desenvolvimento de software para e com reuso. Na literatura, existem diversos trabalhos que exploram repositórios de reuso, porém, o foco desses trabalhos está, quase sempre, voltado a questões de busca e recuperação de componentes e, muitas vezes, aspectos importantes de repositórios de reuso não são explorados adequadamente, como, por exemplo, o uso destes como ferramenta para auxiliar gerentes no monitoramento e controle do reuso em uma organização. Por outro lado, algumas questões levantadas por empresas que desejam construir um repositório de reuso continuam mal respondidas. Tais questões geralmente incluem: Que papéis um repositório deve desempenhar no contexto de reutilização? Quais são os principais requisitos de um repositório de reuso? Quais as alternativas práticas existentes? Como um repositório de reuso pode ser projetado? Motivado por essas questões, esta dissertação apresenta a especificação, o projeto e a implementação de um repositório de reuso baseado na análise das soluções existentes e em uma experiência prática de construção de um ambiente de reuso para fábricas de software. Adicionalmente, são discutidos os resultados obtidos, os problemas encontrados, e as direções futuras para pesquisa e o desenvolvimento
48
Domingues, Paulo Eduardo. "Desenvolvimento de m?todo para consulta em linguagem natural de componentes de software." Pontif?cia Universidade Cat?lica de Campinas, 2007. http://tede.bibliotecadigital.puc-campinas.edu.br:8080/jspui/handle/tede/489.
Full textAbstract:
Made available in DSpace on 2016-04-04T18:31:20Z (GMT). No. of bitstreams: 1
Paulo Eduardo Domingues.pdf: 2694773 bytes, checksum: 8954b221ccf920e889584da2390badf6 (MD5)
Previous issue date: 2007-06-28The development based on components allows to create inter-operable components, with well defined interfaces, reducing the complexity in the software development. In this scene, the library of software components plays an important role in corporate level, supporting documentation, specification, storage and recovery of components. Inside organizations, a components library supplies infrastructure for components lifecycle management. This work considers the storage and the recovery of components of software with the use of an interface in natural language. A method to generate a representation form is described, to be stored in the library, for the texts that describe the characteristics of the components that live in the library. The text of the research generated for the user also is represented of similar form to allow the comparison between the descriptions of the components of the library and the question of the user. Additionally the method is presented to determine the similarity between parts of the representations of the text of the characteristics with the text of the research, of form to return as resulted in sequence decreasing indication from priority the components that better take care of the research of the user.
O desenvolvimento baseado em componentes permite criar componentes inter-oper?veis, com interfaces bem definidas, reduzindo a complexidade no desenvolvimento de software. Neste cen?rio, a biblioteca de componentes de software exerce um papel importante em um ambiente corporativo, suportando a documenta??o, especifica??o, armazenamento e recupera??o de componentes. Dentro das organiza??es, uma biblioteca de componentes fornece uma infra-estrutura para o gerenciamento do ciclo de vida dos componentes. Este trabalho prop?e o armazenamento e a recupera??o de componentes de software com a utiliza??o de uma interface em linguagem natural. ? descrito um m?todo para gerar uma forma de representa??o, a ser armazenada na biblioteca, para os textos que descrevem as caracter?sticas dos componentes que integram a biblioteca. O texto da consulta gerada pelo usu?rio tamb?m ? representado de forma semelhante para permitir a compara??o entre as descri??es dos componentes da biblioteca e a quest?o do usu?rio. Adicionalmente, ? apresentado o m?todo para determinar a semelhan?a entre partes das representa??es do texto das caracter?sticas com o texto das consultas, de forma a retornar como resultado a indica??o em ordem decrescente de prioridade os componentes que melhor atendem a consulta do usu?rio.
49
Marchetti, Guilherme Aren. "Um método de transformação de modelos UML para a inclusão de componentes de frameworks com o uso de planejador lógico." Universidade de São Paulo, 2012. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-21062013-104058/.
Full textAbstract:
Frameworks são ferramentas importantes no contexto atual da tecnologia de desenvolvimento de software, fornecendo funcionalidades através de código previamente testado, o que leva a uma redução na quantidade de código necessário para se implementar soluções e no tempo de implementação. Porém, devido a complexidade dos frameworks atuais, seu uso se torna trabalhoso, requerendo um gasto de tempo elevado para se aprender um framework novo. Neste trabalho de pesquisa foi desenvolvido o Framer, um método de transformação de modelos capaz de selecionar componentes de um framework, a partir de seu modelo UML, que são necessários para implementar as funcionalidades providas pelo framework para uma aplicação em desenvolvimento. Este método de transformação utiliza uma versão modificada do algoritmo NONLIN de planejamento, para identificar não somente os componentes que serão utilizados, mas como e em qual ordem devem ser invocados pela aplicação. Uma vez identificados os componentes, são criados os Diagramas UML necessários para representar sua utilização.Frameworks are important tools for current software development technology, providing functionalities through previously tested code, reducing the amount of code and time necessary to implement the solution. However, due to framework complexity, a developer needs a significant investment in time to learn it. This work presents the Framer, a model transformation method capable of selecting components, from a framework\'s UML model, that will be used to construct the functionalities of the target application. Once the components are identified, the UML Diagrams necessary to describe its use are created.
50
Mugisa, Ezra Kaahwa. "An approach to systematic software reuse based on plugging components into an architecture." Thesis, Imperial College London, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.392068.
Full text