Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: Component software.
Дисертації з теми "Component software"
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся з топ-50 дисертацій для дослідження на тему "Component software".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Переглядайте дисертації для різних дисциплін та оформлюйте правильно вашу бібліографію.
1
ALVARO, Alexandre. "A software component quality framework." Universidade Federal de Pernambuco, 2009. https://repositorio.ufpe.br/handle/123456789/1372.
Повний текст джерелаАнотація:
Made available in DSpace on 2014-06-12T15:49:28Z (GMT). No. of bitstreams: 1
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2009<br>Coordenação de Aperfeiçoamento de Pessoal de Nível Superior<br>Um grande desafio da Engenharia de Software Baseada em Componentes
(ESBC) é a qualidade dos componentes utilizados em um sistema. A
confiabilidade de um sistema baseado em componentes depende da
confiabilidade dos componentes dos quais ele é composto. Na ESBC, a busca,
seleção e avaliação de componentes de software é considerado um ponto chave
para o efetivo desenvolvimento de sistemas baseado em componentes. Até agora
a indústria de software tem se concentrado nos aspectos funcionais dos
componentes de software, deixando de lado uma das tarefas mais árduas, que é
a avaliação de sua qualidade. Se a garantia de qualidade de componentes
desenvolvidos in-house é uma tarefa custosa, a garantia da qualidade utilizando
componentes desenvolvidos externamente os quais frequentemente não se
tem acesso ao código fonte e documentação detalhada se torna um desafio
ainda maior. Assim, esta Tese introduz um Framework de Qualidade de
Componentes de Software, baseado em módulos bem definidos que se
complementam a fim de garantir a qualidade dos componentes de software. Por
fim, um estudo experimental foi desenvolvido e executado de modo que se possa
analisar a viabilidade do framework proposto
2
Banda, Ravi S. "Interoperable components across multiple component architectures." Morgantown, W. Va. : [West Virginia University Libraries], 1998. http://etd.wvu.edu/templates/showETD.cfm?recnum=232.
Повний текст джерелаАнотація:
Thesis (M.S.)--West Virginia University, 1998.<br>Title from document title page. Document formatted into pages; contains vi, 53 p. : ill. Vita. Includes abstract. Includes bibliographical references (p. 50-51).
3
O'Fallon, Andrew Steven. "Component-based software engineering qualification of components during design /." Online access for everyone, 2004. http://www.dissertations.wsu.edu/Thesis/Summer2004/A%5FOFallon%5F073004.pdf.
Повний текст джерела
4
Eler, Marcelo Medeiros. ""Um método para o desenvolvimento de software baseado em componentes e aspectos"." Universidade de São Paulo, 2006. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-04072006-114542/.
Повний текст джерелаАнотація:
Uma investigação sobre como a programação orientada a aspectos combinada com a tecnologia de componentes pode encapsular os interesses transversais de um sistema é apresentada. Como resultado desta investigação, um método para o desenvolvimento de software baseado em componentes e aspectos é proposto, cujas etapas, atividades e artefatos são mostrados por meio do exemplo de um Sistema de Reservas de Hotéis, juntamente com sua implementação nas linguagens JAsCO e AspectJ. O método é uma extensão do método UML Components e utiliza a UML com algumas adaptações. Além disso, uma estratégia de generalização e documentação de componentes transversais para que possam ser reusados em outras aplicações é proposta. Adicionalmente, o método proposto foi usado para o projeto de um Sistema de Locação de Carros e o resultado foi comparado com uma outra solução para o mesmo problema, baseada em UML Components e uma arquitetura geral para sistemas na Web. O resultado dessa comparação é apresentado e discutido.<br>An investigation about how aspect oriented programming combined with the components technology can encapsulate the crosscuting concerns of a system is presented. As result of this research, a method for the aspect and component based software development is proposed, whose phases, activities and designs elements are shown by means of an example of a Hotel Reservation System, with its implementation in the JAsCO and AspectJ languages. The method is an extension of the UML Components method and uses UML with some adaptations. Moreover, a strategy to the generalization and documentation of crosscutting (or aspectual) components to be reused in other applications is proposed. Additionally, the proposed method was used to design a Car Rental System and the result was compared with another solution for the same problem, based on UML Components and a general architecture for Web systems. The results of the comparation are presented and discussed.
5
ALVARO, Alexandre. "Software component certification: a component quality model." Universidade Federal de Pernambuco, 2005. https://repositorio.ufpe.br/handle/123456789/2796.
Повний текст джерелаАнотація:
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: 2005<br>Coordenação de Aperfeiçoamento de Pessoal de Nível Superior<br>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
6
Peres, Darley Rosa. "Modelo de qualidade para componentes de software." Universidade de São Paulo, 2006. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-29012007-112338/.
Повний текст джерелаАнотація:
Dentre as tecnologias de desenvolvimento de software que promovem o reuso com o objetivo de construir sistemas com prazos e custos menores, sem sacrificar a qualidade dos produtos, está o Desenvolvimento Baseado em Componentes (DBC). O Desenvolvimento Baseado em Componentes consiste na construção de sistemas pela composição de componentes de software de acordo com um processo de desenvolvimento específico. Para garantir a qualidade desses sistemas, é importante garantir a qualidade de seus componentes. A falta da garantia da qualidade dos componentes de software destinados à reutilização é um dos fatores de inibição do DBC, e existe certa carência de pesquisas sobre a qualidade de componentes de software. Desta maneira, o principal objetivo deste trabalho foi a definição de um modelo de qualidade específico para componentes de software, fornecendo a base para a especificação de requisitos de qualidade e para a avaliação de qualidade dos mesmos. O Modelo está embasado nas normas ISO/IEC 9126 e ISO/IEC 12119, e também na literatura especializada. Uma ferramenta para apoiar avaliações de componentes (e de produtos de software de forma geral) também foi desenvolvida. Foram realizadas ainda quatro avaliações de componentes através de estudos de casos para verificar a aplicabilidade e utilidade do modelo de qualidade e da ferramenta desenvolvida. Dois questionários foram respondidos pelos avaliadores responsáveis pelas avaliações coletando assim, suas considerações sobre o modelo de qualidade e sobre a ferramenta<br>Among the software development technologies that promote the reuse aiming to build systems with periods and smaller costs, without sacrificing the quality of products, is the Component-Based Development (CBD). The Component-Based Development consists on the construction of systems by the composition of software components according to a specific development process. To guarantee the quality of those systems, it is important to guarantee the quality of their components. The lack of warranty of the quality of the software components destined to reuse is one of the inhibition factors of CBD, and there is certain lack of researches about quality of software components. This way, the main objective of this work was the formalization of a specific quality model for software components, supplying the base for the specification of quality requirements and for the quality evaluation of the same ones. The model is based on the norms ISO/IEC 9126 and ISO/IEC 12119, and also in the specialized literature. A tool to support components evaluations (and software products in a general way) was also developed. It was realized four components evaluations through case studies to verify the applicability and usefulness of the quality model and the developed tool. Two questionnaires were answered by the appraisers responsible for the evaluations collecting thereby, their considerations on the quality model and the tool
7
Abdullahi, Abdille. "Component-based Software development." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2335.
Повний текст джерелаАнотація:
<p>Component-based Software development is a promising way to improve quality, time to market and handle the increasing complexity of software management. However, The component-based development is still a process with many problems, it is not well de_ned either from theoretical or practical point of view. This thesis gives a brief overview of Component-Based Software development and starts with brief historical evolution followed by a general explanation of the method. A detailed discussion of the underlying principles like components, component framework and compent system architecture are then presented. Some real world component stadards such as .net framework, CORBA CCM and EJB are given in detail. Finally, simple fille-sharing-program based on Apache's Avalon framework and another one based on .net framework are developed as a case study.</p>
8
Gayard, Leonel Aguilar 1983. "CosmosLoader : uma ferramenta de apoio ao gerenciamento de configuração baseado no modelo Cosmos*." [s.n.], 2013. http://repositorio.unicamp.br/jspui/handle/REPOSIP/275621.
Повний текст джерелаАнотація:
Orientador: Cecília Mary Fischer Rubira<br>Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação<br>Made available in DSpace on 2018-08-23T21:56:13Z (GMT). No. of bitstreams: 1
Gayard_LeonelAguilar_M.pdf: 1532057 bytes, checksum: 8324b0d9bd3eebedc13daca6f31c7c6b (MD5)
Previous issue date: 2013<br>Resumo: Nos últimos anos, o desenvolvimento baseado em componentes (DBC) e a arquitetura de software emergiram como disciplinas complementares para promover o reuso no desenvolvimento de software. O desenvolvimento baseado em componentes promove o desenvolvimento de componentes reutilizáveis e a formação de novos sistemas de software a partir da integração de componentes existentes. A arquitetura de um sistema de software descreve o sistema em termos de seus componentes arquiteturais, das propriedades destes e das conexões entre eles. Modelos de componentes possibilitam concretizar elementos de DBC como componentes e conectores a partir de conceitos tradicionais de desenvolvimento de software, como por exemplo, orientação a objetos e arquivos, de modo que um conjunto de classes e arquivos complementares podem formar um componente se seguirem as regras do modelo. A adequação a um modelo de componentes oferece benefícios para o sistema de software: por exemplo, o modelo de componentes EJB possibilita que um componente seja implantado em um contêiner e se beneficie do gerenciamento de segurança e transparência de localização oferecidos pelo contêiner; o modelo Cosmos estabelece regras para a criação de componentes baseados em conceitos de linguagens orientadas a objetos, como classes, interfaces e pacotes. Assim, a integração de componentes para a composição de um sistema de software de acordo com uma arquitetura e um modelo de componentes se torna uma atividade importante no desenvolvimento de um novo sistema de software. Uma configuração concreta é um conjunto de determinadas versões de componentes de software conectados de acordo com uma arquitetura. No entanto, observa-se que, se modelos facilitam a criação de componentes de software, ainda é necessário um esforço de desenvolvimento para integrar componentes e formar novos sistemas. O uso de ambientes de desenvolvimento orientados a arquitetura e DBC, e também de ferramentas de automatização, reduzem o esforço necessário para a integração de componentes. O ambiente Bellatrix é um ambiente de desenvolvimento integrado que permite a especificação de elementos arquiteturais e a modelagem de arquiteturas de software. No entanto, ainda existe um hiato entre a arquitetura de um sistema modelada no ambiente Bellatrix e a configuração do sistema a partir de componentes concretos. Esta dissertação apresenta a ferramenta CosmosLoader, que auxilia o gerenciamento de configurações de componentes baseados no modelo Cosmos. A solução proposta se baseia na extensão do ambiente Bellatrix e no modelo de componentes Cosmos* ("Cosmos estrela"), que estende o modelo Cosmos com o conceito de composição hierárquica de componentes. Por fim, são descritos estudos de caso realizados com essas ferramentas<br>Abstract: In the last years, Component-Based Development (CBD) and Software Architecture emerged as complementary disciplines that promote reuse in software development. Component-Based Development promotes the development of reusable software components and the creation of new software systems by integrating existing software components. The architecture of a software system describes such system in terms of its architectural components, their properties and the connections between them. Component models materialize concepts from CBD such as components and connectors from traditional concepts of software development, such as object orientation and files, so that a set of classes and complementary files form a component if they follow the component model's rules. The adequacy to a component model brings benefits to a software system: for instance, the EJB component model allows a component to be deployed to a container and benefit from the security management and location transparency provided by the container; the Cosmos component model allows the creation of components using only concepts from object-oriented languages, such as classes, interfaces and packages. Therefore, the integration of components to compose a new software system according to an architecture and a component model becomes an important activity in the development of a new software system. A concrete configuration is the set of specific versions of software components connected according to an architecture. However, it can be observed that while models ease the creation of software components, a development effort is still necessary to integrate components and form new systems. The use of development environments oriented towards architecture and CBD, and also of automations tools, reduce the effort needed to integrate components. The Bellatrix development environment is an integrated development environment that allows the specification of architectural elements and modeling of software architectures. However, there still is a gap between the architecture of a system modeled in Bellatrix and the configuration of a system from concrete software components. This dissertation presents the CosmosLoader tool, which assists in managing the configuration of components based on the Cosmos model. The proposed solution is based on an extension to the Bellatrix development environment and on the Cosmos* component model ("Cosmos star"), which extends the Cosmos component model with hierarchical composition of components. Finally, case studies using these tools are described<br>Mestrado<br>Ciência da Computação<br>Mestre em Ciência da Computação
9
Fischer, Bernd. "Deduction-based software component retrieval." [S.l.] : [s.n.], 2002. http://deposit.ddb.de/cgi-bin/dokserv?idn=964334488.
Повний текст джерела
10
Wu, Zhengyu Leo. "Software component retrieval by composition." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk2/tape16/PQDD_0001/MQ31009.pdf.
Повний текст джерела
11
Kivijärvi, M. (Marko). "Cross-platform software component design." Master's thesis, University of Oulu, 2013. http://urn.fi/URN:NBN:fi:oulu-201306011427.
Повний текст джерелаАнотація:
The aim of this thesis is to analyze a project to design and implement a new FM Radio application for Symbian OS. The project process and relevant events are discussed when they have an impact on the design work. The goal of the project was to offer an improved user experience with features like favorite stations, song history, RT+ support, and automatic region selection. In order to complete the application within the project schedule, the existing radio modules were to be reused as much as possible. The application was required to be developed using the Qt application framework and to have no dependencies on the old UI framework from the Symbian OS. Platform-independence, testability, and simplicity were other key requirements for the new radio application. A final comprehensive goal was to stick to established design patterns and to follow the design principles and good practices defined earlier in the bachelor’s thesis by the same author. An added challenge was provided by the necessity to develop the application on top of a new UI framework that was still in development itself. Constant changes to the framework put a strain on the already tight project schedule. The discussion focuses on the design of the engine module that was required to house most of the application logic. The engine is disconnected from the Symbian OS by the use of a wrapper module, whose purpose is to hide the platform details. Due to its relevance to the engine, the design of the wrapper is discussed in detail. The application UI and the reused radio modules are discussed briefly and only to the extent that is relevant for the engine design. The resulting design fulfills its requirements and the implemented application performs as designed. All the required features are supported, and the existing radio modules are reused. The lack of dependency on the old UI framework is witnessed by running the application in a system that does not contain the framework. The possibility to run the application on a Windows workstation also affirms that the platform-independence requirement was achieved. The design and implementation adhere to the principles outlined in the bachelor’s thesis and provide a practical use for them. The principles are found to be valid and important for the successful completion of a complex software project. It is discovered that the goal of designing a simple system from complicated beginnings is difficult to achieve and requires many iterations. Gradual refinements to the architecture and implementation are necessary to finally arrive at the optimal design. Constant refactoring is found to be a key element in the successful completion of a software project<br>Tässä työssä analysoidaan projektia, jossa suunniteltiin ja toteutettiin uusi FM Radio -sovellus Symbian-käyttöjärjestelmälle. Projektin prosessi ja oleelliset tapahtumat kuvataan siltä osin kuin ne vaikuttavat suunnittelutyöhön. Projektin tavoite oli tarjota parempi käyttökokemus uusilla ominaisuuksilla kuten suosikkikanavilla, kappalehistorialla, RT+ -tuella, ja automaattisella aluevalinnalla. Olemassa olevia radiomoduuleita oli uudelleenkäytettävä niin paljon kuin mahdollista, jotta projekti saataisiin aikataulun puitteissa valmiiksi. Sovellus tuli suunnitella Qt-sovelluskehystä käyttäen, eikä sillä saanut olla riippuvuuksia vanhaan käyttöliittymäkirjastoon. Alustariippumattomuus, testattavuus ja yksinkertaisuus olivat myös tärkeitä vaatimuksia. Viimeinen kattava tavoite oli pitäytyä vakiintuneissa suunnittelumalleissa ja noudattaa suunnitteluperiaatteita ja hyviä toimintatapoja, jotka olivat saman tekijän kandidaatintyössä aiemmin määritelty. Tarve toteuttaa sovellus keskeneräisen käyttöliittymäkirjaston päälle asetti oman lisähaasteensa. Jatkuvat muutokset kirjastossa rasittivat jo valmiiksi tiukkaa projektiaikataulua. Tämän työn pääpaino on moottorimoduulissa, jonka tuli sisältää suurin osa sovelluksen logiikasta. Moottori on eriytetty Symbian-käyttöjärjestelmästä adapterimoduulilla, jonka tarkoitus on piilottaa ohjelmistoalustan yksityiskohdat. Adapterin suunnitelma kuvataan yksityiskohtaisesti. Sovelluksen käyttöliittymä ja uudelleenkäytetyt radiomoduulit kuvataan lyhyesti ja vain niiltä osin kuin ne ovat moottorin suunnitelmalle oleellisia. Tuloksena syntyvä suunnitelma täyttää vaatimukset, ja toteutettu sovellus toimii kuten oli suunniteltu. Kaikki vaaditut ominaisuudet ovat tuettuja ja olemassa olevat radiomoduulit käytettiin uudelleen. Riippumattomuus vanhasta käyttöliittymäkirjastosta havaitaan suorittamalla sovellusta järjestelmässä, jossa sitä ei ole. Mahdollisuus ajaa sovellusta Windows-työasemassa myös todistaa sen, että alustariippumattomuuden vaatimus täytettiin. Suunnitelma ja toteutus noudattavat kandidaatintyössä määriteltyjä periaatteita ja tarjoavat niille käytännön sovellutuksen. Periaatteet todetaan paikkansapitäviksi ja tärkeiksi monimutkaisen ohjelmistoprojektin onnistuneen valmistumisen kannalta. Työssä havaitaan, että tavoite suunnitella yksinkertainen järjestelmä monimutkaisista lähtökohdista on vaikea saavuttaa ja vaatii useita toistoja. Asteittaiset korjaukset arkkitehtuuriin ja toteutukseen ovat välttämättömiä optimaaliseen suunnitelman saavuttamiseksi. Jatkuvan uudelleenjärjestelyn havaitaan olevan avainasemassa ohjelmistosuunnitteluprosessissa
12
Avkarogullari, Okan. "Representing Design Patterns As Super Components In Component Oriented Software Engineering." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/1305390/index.pdf.
Повний текст джерелаАнотація:
It is widely believed and empirically shown that component reuse improves both the quality and productivity of software development. This brings the necessity of a graphical editor to model the projects by using components. A graphical editor was implemented for the development of Component Oriented software development. The editor facilitates modeling efforts through application of the graphical modeling language COSEML. Both design patterns and software components have come to play important roles in software development. The correlation between software components and design patterns is apparent. In the design phase of the projects design patterns are used widely both in component and object oriented projects. Design patterns can be used as super components in component-based development . Software reuse, software components, design patterns, use of design patterns in component-based development, and component architectures are studied in details to address the need for the approach. COSE modeling activity starts with the decomposition of the target system into building blocks in a top-down order. Next, interfaces between these blocks are defined. If required design patterns can be added to model as super components.
13
Möller, Anders. "Software Component Technologies for Heavy Vehicles." Licentiate thesis, Mälardalen University, Department of Computer Science and Electronics, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-34.
Повний текст джерелаАнотація:
<p>Control-systems for heavy vehicles have advanced from an area where Industrial Requirements on Component Technologies for Embedded Systemsmainly mechanic and hydraulic solutions were used, to a highly computerised domain using distributed embedded real-time computer systems. To cope with the increasing level of end-customer demands on advanced features and functions in future vehicle systems, sophisticated development techniques are needed. The development techniques must support software in numerous configurations and facilitate development of systems with requirements on advanced functionality, timeliness, and safety-criticality. In order to meet these requirements, we propose the use of component-based software engineering. However, the software component-technologies available on the market have not yet been generally accepted by the vehicular industry. In order to better understand why this is the case, we have conduced a survey - identifying the industrial requirements that are deemed decisive for introducing a component technology. We have used these requirements to evaluate a number of existing component technologies, and one of our conclusions is that none of the studied technologies is a perfect match for the industrial requirements. In addition, we have implemented and evaluated the novel component model SaveCCM, which has been designed for safety-critical automotive applications. Our evaluation indicates that SaveCCM is a promising technology which has the potential to fulfil the industrial requirements. However, tools are still immature and incomplete. In the final part of this work, we propose the use of monitored software components, as a general approach for engineering of embedded systems. In our approach, a component's execution is continuously monitored and experience regarding the behaviour is accumulated. As more and more experience is collected the confidence in the component grows. </p>
14
Johannes, Jendrik. "Component-Based Model-Driven Software Development." Doctoral thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2011. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-63986.
Повний текст джерелаАнотація:
Model-driven software development (MDSD) and component-based software development are both paradigms for reducing complexity and for increasing abstraction and reuse in software development. In this thesis, we aim at combining the advantages of each by introducing methods from component-based development into MDSD. In MDSD, all artefacts that describe a software system are regarded as models of the system and are treated as the central development artefacts. To obtain a system implementation from such models, they are transformed and integrated until implementation code can be generated from them. Models in MDSD can have very different forms: they can be documents, diagrams, or textual specifications defined in different modelling languages. Integrating these models of different formats and abstraction in a consistent way is a central challenge in MDSD.
We propose to tackle this challenge by explicitly separating the tasks of defining model components and composing model components, which is also known as distinguishing programming-in-the-small and programming-in-the-large. That is, we promote a separation of models into models for modelling-in-the-small (models that are components) and models for modelling-in-the-large (models that describe compositions of model components). To perform such component-based modelling, we introduce two architectural styles for developing systems with component-based MDSD (CB-MDSD).
For CB-MDSD, we require a universal composition technique that can handle models defined in arbitrary modelling languages. A technique that can handle arbitrary textual languages is universal invasive software composition for code fragment composition. We extend this technique to universal invasive software composition for graph fragments (U-ISC/Graph) which can handle arbitrary models, including graphical and textual ones, as components. Such components are called graph fragments, because we treat each model as a typed graph and support reuse of partial models.
To put the composition technique into practice, we developed the tool Reuseware that implements U-ISC/Graph. The tool is based on the Eclipse Modelling Framework and can therefore be integrated into existing MDSD development environments based on the framework.
To evaluate the applicability of CB-MDSD, we realised for each of our two architectural styles a model-driven architecture with Reuseware. The first style, which we name ModelSoC, is based on the component-based development paradigm of multi-dimensional separation of concerns. The architecture we realised with that style shows how a system that involves multiple modelling languages can be developed with CB-MDSD. The second style, which we name ModelHiC, is based on hierarchical composition. With this style, we developed abstraction and reuse support for a large modelling language for telecommunication networks that implements the Common Information Model industry standard.
15
Georgiadis, Ioannis. "Self-organising distributed component software architectures." Thesis, Imperial College London, 2001. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.396255.
Повний текст джерела
16
Ntalamagkas, Ioannis. "A software component model with concurrency." Thesis, University of Manchester, 2009. http://www.manchester.ac.uk/escholar/uk-ac-man-scw:180466.
Повний текст джерелаАнотація:
Component-Based Software Development (CBSD) represents a paradigm shift in software engineering, where the focus is on building systems out of pre-developed components. In CBSD, components developers are different from component users, where the former concentrate on building reusable components, whereas the latter concentrate on building customised systems out of components. The different roles in component development give rise to the idealised component life cycle which consists of the design, the deployment and the run-time phases. Ideally, component composition should occur in both design and deployment phases and it should be supported by a proper composition theory. Concurrency is an important issue in software engineering and in theoretical computer science. Decades of research have been devoted in finding efficient ways of discovering common concurrency errors, like deadlock, in abstract mathematical models and in software. Existing software component models do not address composition and concurrency completely. In general, component models support composition in either design or deployment phase but not in both. Regarding concurrency, the support provided varies, ranging from complete formal models to leaving the concurrency aspect undefined and dependant on the implementation. More importantly, not all component models support both passive and active components. In this thesis we define a software component model that supports composition of active and passive components using explicit composition operators, in both design and deployment phases of the idealised component life cycle. We also show that our composition connectors are control patterns and we define their composition. This means that composite connectors are composed out of simpler ones. This allows for the hierarchical construction of complex control structures that can be used in further connector and component compositions. Connector composition constitutes a unique feature of our model.
17
Kanetkar, Kavita Vijay. "Formal analysis of component adaptation techniques." Link to electronic thesis, 2002. http://www.wpi.edu/Pubs/ETD/Available/etd-0430102-150305.
Повний текст джерела
18
Ozdogru, Ebru. "A Gis Domain Framework Utilizing Jar Libraries As Components." Master's thesis, METU, 2005. http://etd.lib.metu.edu.tr/upload/12606111/index.pdf.
Повний текст джерелаАнотація:
A Component Oriented Software Engineering (COSE) modeling environment is
enhanced with the capability to import executable components and deliver
applications through their composition. For this purpose, an interface layer that
utilizes JAR libraries as components has been developed. Also, Domain Engineering
process has been applied to Geographical Information Systems (GIS) domain and
utilized towards converting the environment to a development framework. The
interface layer imports JAR libraries into the COSECASE tool, which is a graphical
tool supporting COSE approach and COSE Modeling Language (COSEML). As a
result, systems can be designed using abstractions and then implemented by
corresponding deployed components. Imported code is made available to the
COSECASE environment through this interface layer. Also, Domain Analysis,
Domain Design, and Domain Implementation phases of Domain Engineering process
have been applied to the GIS domain. Components developed in this Domain
Implementation phase have been imported into COSECASE. A simple GIS
application has been designed and generated through the interface layer of
COSECASE for demonstration purposes.
19
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.
Повний текст джерелаАнотація:
Thesis (M.S.)--Worcester Polytechnic Institute.<br>Keywords: component adaptations; active interfaces; blackbox component adaptation; component specification language; software reuse. Includes bibliographical references.
20
CARVALHO, Fernando Ferreira de. "An embedded software component quality evaluation methodology." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2412.
Повний текст джерелаАнотація:
Made available in DSpace on 2014-06-12T15:57:59Z (GMT). No. of bitstreams: 2
arquivo3240_1.pdf: 2429983 bytes, checksum: 9b9eff719ea26a708f6868c5df873358 (MD5)
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2010<br>Universidade de Pernambuco<br>Um dos maiores desafios para a indústria de embarcados é fornecer produtos com
alto nível de qualidade e funcionalidade, a um baixo custo e curto tempo de
desenvolvimento, disponibilizando-o rapidamente ao mercado, aumentando assim,
o retorno dos investimentos. Os requisitos de custo e tempo de desenvolvimento
têm sido abordados com bastante êxito pela engenharia de software baseada em
componentes (CBSE) aliada à técnica de reuso de componentes. No entanto, a
utilização da abordagem CBSE sem as devidas verificações da qualidade dos
componentes utilizados, pode trazer conseqüências catastróficas (Jezequel et al.,
1997). A utilização de mecanismos apropriados de pesquisa, seleção e avaliação da
qualidade de componentes são considerados pontos chave na adoção da abordagem
CBSE. Diante do exposto, esta tese propõe uma Metodologia para Avaliação da
Qualidade de Componentes de Software Embarcados sob diferentes aspectos. A
idéia é solucionar a falta de consistência entre as normas ISO/IEC 9126, 14598 e
2500, incluindo o contexto de componente de software e estendendo-o ao domínio
de sistemas embarcados. Estas normas provêem definições de alto nível para
características e métricas para produtos de software, mas não provêem formas de
usá-las efetivamente, tornando muito difícil aplicá-las sem adquirir mais
informações de outras fontes. A Metodologia é composta de quatro módulos que se
complementam em busca da qualidade, através de um processo de avaliação, um
modelo de qualidade, técnicas de avaliação agrupadas por níveis de qualidade e
uma abordagem de métricas. Desta forma, ela auxilia o desenvolvedor de sistemas
embarcado no processo de seleção de componentes, avaliando qual componente
melhor se enquadra nos requisitos do sistema. É utilizada por avaliadores
terceirizados quando contratados por fornecedores a fim de obter credibilidade em
seus componentes. A metodologia possibilita avaliar a qualidade do componente
embarcado antes do mesmo ser armazenado em um sistema de repositório,
especialmente no contexto do framework robusto para reuso de software, proposto
por Almeida (Almeida, 2004)
21
Mason, David Victor. "Probabilistic program analysis for software component reliability." Waterloo, Ont. : University of Waterloo, 2002. http://etd.uwaterloo.ca/etd/dmason2002.pdf.
Повний текст джерелаАнотація:
Thesis (Ph.D.)--University of Waterloo, 2002.<br>"A thesis presented to the University of Waterloo in fulfilment of the thesis requirement for the degree of Doctor of Philosophy in Computer Science". Includes bibliographical references. Also available in microfiche format.
22
Nguyen, Doan Han. "An architectural model for software component search." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1995. http://handle.dtic.mil/100.2/ADA306133.
Повний текст джерела
23
Salman, Nael. "Amesurement Framework For Component Oriented Software Systems." Phd thesis, METU, 2006. http://etd.lib.metu.edu.tr/upload/3/12607826/index.pdf.
Повний текст джерелаАнотація:
A measurement framework is presented for component oriented (CO) software systems. Fundamental concepts in component orientation are defined. The factors that influence CO systems&rsquo<br>structural complexity are identified. Metrics quantifying and characterizing these factors are defined. A set of properties that a CO complexity metric must satisfy are defined. Metrics are evaluated first using the set of properties defined in this thesis and also using the set of properties defined by Tian and Zelkowitz in [84]. Evaluation results revealed that metrics satisfy all properties in both sets. Empirical validation of metrics is performed using data collected from graduate students&rsquo<br>projects. Validation results revealed that CO complexity metrics can be used as predictors of development effort, Design effort, integration effort (characterizing system integrabiltiy), correction effort (characterizing system maintainability), function points count (characterizing system functionality), and programmer productivity. An Automated metrics collection tool is implemented and integrated with a dedicated CO modeling tool. The metrics collection tool automatically collects complexity metrics from system models and performs prediction estimations accordingly.
24
Mason, Dave. "Probabilistic Program Analysis for Software Component Reliability." Thesis, University of Waterloo, 2002. http://hdl.handle.net/10012/1059.
Повний текст джерелаАнотація:
Components are widely seen by software engineers as an important technology to address the "software crisis''. An important aspect of components in other areas of engineering is that system reliability can be estimated from the reliability of the components. We show how commonly proposed methods of reliability estimation and composition for software are inadequate because of differences between the models and the actual software systems, and we show where the assumptions from system reliability theory cause difficulty when applied to software. This thesis provides an approach to reliability that makes it possible, if not currently plausible, to compose component reliabilities so as to accurately and safely determine system reliability. Firstly, we extend previous work on input sub-domains, or partitions, such that our sub-domains can be sampled in a statistically sound way. We provide an algorithm to generate the most important partitions first, which is particularly important when there are an infinite number of input sub-domains. We combine analysis and testing to provide useful reliabilities for the various input sub-domains of a system, or component. This provides a methodology for calculating true reliability for a software system for any accurate statistical distribution of input values. Secondly, we present a calculus for probability density functions that permits accurately modeling the input distribution seen by each component in the system - a critically important issue in dealing with reliability of software components. Finally, we provide the system structuring calculus that allows a system designer to take components from component suppliers that have been built according to our rules and to determine the resulting system reliability. This can be done without access to the actual components. This work raises many issues, particularly about scalability of the proposed techniques and about the ability of the system designer to know the input profile to the level and kind of accuracy required. There are also large classes of components where the techniques are currently intractable, but we see this work as an important first step.
25
Groenda, Henning [Verfasser]. "Certifying Software Component Performance Specifications / Henning Groenda." Karlsruhe : KIT Scientific Publishing, 2013. http://www.ksp.kit.edu.
Повний текст джерела
26
Owen, Stephen. "Documentation use in component-based software composition." Thesis, Keele University, 2007. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.436199.
Повний текст джерела
27
SILVA, ALEKSANDER MEDELLA CAMPOS DA. "A SOFTWARE COMPONENT LIBRARY FOR RADAR SIMULATORS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2011. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=19241@1.
Повний текст джерелаАнотація:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO<br>Os sistemas radares são amplamente utilizados em aplicações civis e militares,
são sistemas complexos que empregam alta tecnologia. Muitos deles
são constituídos por um conjunto de elementos que necessitam de um
mínimo de coordenação entre as suas funcionalidades. A construção de um
protótipo para validar o projeto de um radar demanda recursos financeiros
e tempo. Por outro lado, existem muitas características em comum entre
os sistemas de diferentes radares. Esta dissertação descreve uma biblioteca
de um simulador capaz de representar vários sistemas de radar e que foi
projetado de acordo com os princípios básicos sobre radar. O simulador foi
desenvolvido baseado em um sistema de componentes
flexíveis onde cinco
diferentes tipos de radar são descritos e simulados utilizando a biblioteca
apresentada. Porém cenários reais são utilizados para comparar e validar
as simulacões.<br>Nowadays Radar systems are becoming complex systems. Many radars are
constituted by an array of elements, where a minimum of coordination
among the elements functionality is need. The task to build a prototype in
order to validate a radar design is an expensive one. On the other hand, there
are many common features shared among different radar architectures. This
dissertation describes the architecture of a simulator that is able to represent
most of the radar systems designed according the basic principles of radars.
The simulator is designed following a
exible component based architecture
and five quite different kind of radars are described and simulated using
the presented architecture. Real scenarios are taken into account in the
validation of the simulations.
28
Leeb, Angelika. "A flexible object architecture for component software." Thesis, Massachusetts Institute of Technology, 1996. http://hdl.handle.net/1721.1/40229.
Повний текст джерела
29
Goulão, Miguel Carlos Pacheco Afonso. "Component-based software engineering: a quantitative approach." Doctoral thesis, FCT - UNL, 2008. http://hdl.handle.net/10362/1883.
Повний текст джерелаАнотація:
Dissertação apresentada para a obtenção do Grau de Doutor em Informática pela Universidade Nova de Lisboa, Faculdade de Ciências e Tecnologia<br>Background: Often, claims in Component-Based Development (CBD) are only supported by qualitative expert opinion, rather than by quantitative data. This contrasts with the normal practice in other sciences, where a sound experimental validation of claims is standard practice. Experimental Software Engineering (ESE) aims to bridge this gap. Unfortunately, it is common to find experimental validation efforts that are
hard to replicate and compare, to build up the body of knowledge in CBD.
Objectives: In this dissertation our goals are (i) to contribute to evolution of ESE, in
what concerns the replicability and comparability of experimental work, and (ii) to apply our proposals to CBD, thus contributing to its deeper and sounder understanding.
Techniques: We propose a process model for ESE, aligned with current experimental
best practices, and combine this model with a measurement technique called
Ontology-Driven Measurement (ODM). ODM is aimed at improving the state of practice
in metrics definition and collection, by making metrics definitions formal and executable,without sacrificing their usability. ODM uses standard technologies that can be well adapted to current integrated development environments.
Results: Our contributions include the definition and preliminary validation of a process model for ESE and the proposal of ODM for supporting metrics definition and
collection in the context of CBD. We use both the process model and ODM to perform
a series experimental works in CBD, including the cross-validation of a component
metrics set for JavaBeans, a case study on the influence of practitioners expertise in
a sub-process of component development (component code inspections), and an observational study on reusability patterns of pluggable components (Eclipse plug-ins).
These experimental works implied proposing, adapting, or selecting adequate ontologies,
as well as the formal definition of metrics upon each of those ontologies.
Limitations: Although our experimental work covers a variety of component models and, orthogonally, both process and product, the plethora of opportunities for using our quantitative approach to CBD is far from exhausted.
Conclusions: The main contribution of this dissertation is the illustration, through
practical examples, of how we can combine our experimental process model with ODM to support the experimental validation of claims in the context of CBD, in a repeatable and comparable way. In addition, the techniques proposed in this dissertation
are generic and can be applied to other software development paradigms.<br>Departamento de Informática of the Faculdade de Ciências e Tecnologia, Universidade Nova de Lisboa (FCT/UNL); Centro de Informática e Tecnologias da Informação of the FCT/UNL; Fundação para a Ciência e Tecnologia through the STACOS project(POSI/CHS/48875/2002); The Experimental Software Engineering Network (ESERNET);Association Internationale pour les Technologies Objets (AITO); Association forComputing Machinery (ACM)
30
Danish, Muhammad Rafique, and Sajjad Ali Khan. "Component Repository Browser." Thesis, Mälardalen University, School of Innovation, Design and Engineering, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-7707.
Повний текст джерелаАнотація:
<p>The main goal of this thesis is to investigate efficient searching mechanisms for searching and retrieving software components across different remote repositories and implement a supporting prototype called “Component Repository Browser” using the plug-in based Eclipse technology for PROGRESS-IDE. The prototype enables users to search the ProCom components and to import the desired components from a remote repository server over different protocols such as HTTP, HTTPS, and/or SVN. Several component searching mechanisms and suggestions were studied and examined such as keyword, facet-based search, folksonomy classification, and signature matching, from which we selected keyword search along with facet-based searching technique to help component searchers to efficiently find the desired components from a remote repository.</p>
31
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/.
Повний текст джерелаАнотація:
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.<br>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.
32
Mateas, Michael Joseph. "A Cognitively Motivated System for Software Component Reuse." PDXScholar, 1993. https://pdxscholar.library.pdx.edu/open_access_etds/4699.
Повний текст джерелаАнотація:
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
33
Lewis, Joshua. "A COMMON COMPONENT-BASED SOFTWARE ARCHITECTURE FOR MILITARY AND COMMERCIAL PC-BASED VIRTUAL SIMULATION." Doctoral diss., University of Central Florida, 2006. http://digital.library.ucf.edu/cdm/ref/collection/ETD/id/2301.
Повний текст джерелаАнотація:
Commercially available military-themed virtual simulations have been developed and sold for entertainment since the beginning of the personal computing era. There exists an intense interest by various branches of the military to leverage the technological advances of the personal computing and video game industries to provide low cost military training. By nature of the content of the commercial military-themed virtual simulations, a large overlap has grown between the interests, resources, standards, and technology of the computer entertainment industry and military training branches. This research attempts to identify these commonalities with the purpose of systematically designing and evaluating a common component-based software architecture that could be used to implement a framework for developing content for both commercial and military virtual simulation software applications.<br>Ph.D.<br>Other<br>Engineering and Computer Science<br>Modeling and Simulation
34
Wood, M. I. "Component Descriptor Frames : A representation to support the storage and retrieval of reusable software components." Thesis, University of Strathclyde, 1988. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.382482.
Повний текст джерела
35
Feng, Yankui. "Generative aspect-oriented component adaptation." Thesis, Edinburgh Napier University, 2008. http://researchrepository.napier.ac.uk/Output/2431.
Повний текст джерелаАнотація:
Due to the availability of components and the diversity of target applications, mismatches between pre-qualified existing components and the particular reuse context in applications are often inevitable and have been a major hurdle of component reusability and successful composition. Although component adaptation has acted as a key solution for eliminating these mismatches, existing practices are either only capable for adaptation at the interface level, or require too much intervention from software engineers. Another weakness of existing approaches is the lack of reuse of component adaptation knowledge. Aspect Oriented Programming (AOP) is a new methodology that provides separation of crosscutting concerns by introducing a new unit of modularization - an Aspect that crosscuts other modules. In this way, all the associated complexity of the crosscutting concerns is isolated into the Aspects, hence the final system becomes easier to design, implement and maintain. The nature of AOP makes it particularly suitable for addressing non-functional mismatches with component-based systems. However, current AOP techniques are not powerful enough for efficient component adaptation due to the weaknesses they have, including the limited reusability of Aspects, platform specific Aspects, and naive weaving processes. Therefore, existing AOP technology needs to be expanded before it can be used for efficient component adaptation. This thesis presents a highly automated approach to component adaptation through product line based Generative Aspect Oriented Component adaptation. In the approach, the adaptation knowledge is captured in Aspects and aims to be reusable in various adaptation circumstances. Automatic generation of adaptation Aspects is developed as a key technology to improve the level of automation of the approach and the reusability of adaptation knowledge. This generation is realised by developing a two dimensional Aspect model, which incorporates the technologies of software product line and generative programming. The adaptability and automation of the approach is achieved in an Aspect oriented component adaptation framework by generating and then applying the adaptation Aspects under a designed weaving process according to specific adaptation requirements. To expand the adaptation power of AOP, advanced Aspect weaving processes have been developed with the support of an enhanced aspect weaver. To promote the reusability of adaptation Aspects, an expandable repository of reusable adaptation Aspects has been developed based on the proposed two-dimensional Aspect model. A prototype tool is built as a leverage of the approach and automates the adaptation process. Case studies have been done to illustrate and evaluate the approach, in terms of its capability of building highly reusable Aspects across various AOP platforms and providing advanced weaving process. In summary, the proposed approach applies Generative Aspect Oriented Adaptation to targeted components to correct the mismatch problem so that the components can be integrated into a target application easily. The automation of the adaptation process, the deep level of the adaptation, and the reusability of adaptation knowledge are the advantages of the approach.
36
Phippen, Andrew David. "Component technologies and their impact upon software development." Thesis, University of Plymouth, 2000. http://hdl.handle.net/10026.1/1723.
Повний текст джерелаАнотація:
Software development is beset with problems relating to development productivity, resulting in projects delivered late and over budget. While the term software engineering was first introduced in the late sixties, its current state reflects no other engineering discipline. Component-orientation has been proposed as a technique to address the problems of development productivity and much industrial literature extols the benefits of a component-oriented approach to software development. This research programme assesses the use of component technologies within industrial software development. From this assessment, consideration is given to how organisations can best adopt such techniques. Initial work focuses upon the nature of component-orientation, drawing from the considerable body of industrial literature in the area. Conventional wisdom regarding componentorientation is identified from the review. Academic literature relevant to the research programme focuses upon knowledge regarding the assessment of software technologies and models for the adoption of emergent technologies. The method pays particular attention to literature concerning practitioner focussed research, in particular case studies. The application of the case study method is demonstrated. The study of two industrial software development projects enables an examination of specific propositions related to the effect of using component technologies. Each case study is presented, and the impact of component-orientation is each case is demonstrated. Theories regarding the impact of component technologies upon software development are drawn from case study results. These theories are validated through a survey of practitioners. This enabled further examination of experience in component-based development and also understanding how developers learn about the techniques. A strategy for the transfer of research findings into organisational knowledge focuses upon the packaging of previous experience in the use of component-orientation in such a way that it was usable by other developers. This strategy returns to adoption theories in light of the research findings and identifies a pattern-based approach as the most suitable for the research aims. A pattern language, placed in the context of the research programme, is developed from this strategy. Research demonstrates that component-orientation undoubtedly does affect the development process, and it is necessary to challenge conventional wisdom regarding their use. While component-orientation provides the mechanisms for increased productivity in software development, these benefits cannot be exploited without a sound knowledge base around the domain.
37
Mulugeta, Dinku Mesfin. "QoS Contract Negotiation in Distributed Component-Based Software." Doctoral thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2007. http://nbn-resolving.de/urn:nbn:de:swb:14-1185279327735-87696.
Повний текст джерелаАнотація:
Currently, several mature and commercial component models (for e.g. EJB, .NET, COM+) exist on the market. These technologies were designed largely for applications with business-oriented non-functional requirements such as data persistence, confidentiality, and transactional support. They provide only limited support for the development of components and applications with non-functional properties (NFPs) like QoS (e.g. throughput, response time). The integration of QoS into component infrastructure requires among other things the support of components’ QoS contract specification, negotiation, adaptation, etc. This thesis focuses on contract negotiation. For applications in which the consideration of non-functional properties (NFPs) is essential (e.g. Video-on-Demand, eCommerce), a component-based solution demands the appropriate composition of the QoS contracts specified at the different ports of the collaborating components. The ports must be properly connected so that the QoS level required by one is matched by the QoS level provided by the other. Generally, QoS contracts of components depend on run-time resources (e.g. network bandwidth, CPU time) or quality attributes to be established dynamically and are usually specified in multiple QoS-Profiles. QoS contract negotiation enables the selection of appropriate concrete QoS contracts between collaborating components. In our approach, the component containers perform the contract negotiation at run-time. This thesis addresses the QoS contract negotiation problem by first modelling it as a constraint satisfaction optimization problem (CSOP). As a basis for this modelling, the provided and required QoS as well as resource demand are specified at the component level. The notion of utility is applied to select a good solution according to some negotiation goal (e.g. user’s satisfaction). We argue that performing QoS contract negotiation in multiple phases simplifies the negotiation process and makes it more efficient. Based on such classification, the thesis presents heuristic algorithms that comprise coarse-grained and fine-grained negotiations for collaborating components deployed in distributed nodes in the following scenarios: (i) single-client - single-server, (ii) multiple-clients, and (iii) multi-tier scenarios. To motivate the problem as well as to validate the proposed approach, we have examined three componentized distributed applications. These are: (i) video streaming, (ii) stock quote, and (iii) billing (to evaluate certain security properties). An experiment has been conducted to specify the QoS contracts of the collaborating components in one of the applications we studied. In a run-time system that implements our algorithm, we simulated different behaviors concerning: (i) user’s QoS requirements and preferences, (ii) resource availability conditions concerning the client, server, and network bandwidth, and (iii) the specified QoS-Profiles of the collaborating components. Under various conditions, the outcome of the negotiation confirms the claim we made with regard to obtaining a good solution.
38
Larsson, Magnus. "Predicting Quality Attributes in Component-based Software Systems." Doctoral thesis, Västerås : Mälardalen University, 2004. http://www.mrtc.mdh.se/publications/0696.pdf.
Повний текст джерела
39
Steigerwald, Robert Allen. "Reusable software component retrieval via normalized algebraic specifications." Thesis, Monterey, California. Naval Postgraduate School, 1991. http://hdl.handle.net/10945/26733.
Повний текст джерела
40
CERQUEIRA, RENATO FONTOURA DE GUSMAO. "A DYNAMIC INTEGRATION MODEL FOR SOFTWARE COMPONENT SYSTEMS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2000. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=2792@1.
Повний текст джерелаАнотація:
CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO<br>Diferentes sistemas de componentes de software, tais como CORBA, COM e JavaBeans, apresentam
diferentes modelos de objetos e sistemas de tipos. Essas diferenças dificultam a integração de componentes oriundos de sistemas distintos e, conseqüentemente, são uma barreira para o reuso desses
componentes.
Neste trabalho, defendemos a tese de que uma linguagem interpretada com um determinado conjunto de mecanismos reflexivos, aliada à compatibilidade estrutural de tipos, oferece um mecanismo
de composição adequado tanto para a conexão dinâmica de componentes, quanto para a interoperabilidade entre diferentes sistemas de componentes. Esse mecanismo de composição realiza em tempo
de execução as tarefas de conexão, adaptação, implementação e verificação de tipos de componentes,
e trata de uma maneira uniforme componentes de diferentes sistemas, permitindo que estes sejam
conectados de uma forma transparente.
O mecanismo de composição que propomos se baseia em um modelo que privilegia a flexibilidade
em tempo de execução. Esse modelo de composição é composto por dois elementos principais. O
primeiro elemento é um modelo de objetos que definimos com a finalidade de poder representar
componentes dos diferentes sistemas tratados neste trabalho. Assim, esse modelo de objetos faz o
papel de um modelo integrador, isto é, um modelo sob o qual objetos de diferentes sistemas podem
ser representados e interagir de forma transparente.
O segundo elemento de nosso modelo de composição é um padrão de projeto (design pattern) para
a implementação de bindings entre linguagens interpretadas e sistemas de componentes. Esse padrão
de projeto, chamado Dynamic Language Binding, não utiliza a técnica tradicional de stubs. Ao invés
disso, ele utiliza mecanismos de reflexividade e tipagem dinâmica para implementar tanto proxies
genéricos, que podem representar qualquer componente de um determinado sistema, quanto adaptadores genéricos, que permitem a implementação de componentes utilizando a própria linguagem de
composição.
Como instrumento de validação da nossa proposta, descrevemos uma implementação do modelo
de composição denominada LuaOrb. LuaOrb utiliza a linguagem interpretada Lua como linguagem
de composição dinâmica, e integra os sistemas CORBA, COM e Java.<br>Different component systems, such as CORBA, COM, and Java,
have different object models and
type systems. Such differences make the interoperability
between components of distinct systems
more difficult, and thus are an obstacle for component
reuse.
In this dissertation, we argue that an interpreted
language with a specific set of reflexive mechanisms,
together with a type system with structural compatibility,
offers a composition mechanism
suitable for dynamic component connection and for
interoperability between different component
systems. This composition mechanism performs at runtime
the tasks of verifying types, connecting,
adapting and implementing components, and handles
components of different systems in a uniform
way, allowing them to be connected transparently.
The proposed composition mechanism is based on a model
that favors flexibility at runtime. This
composition model is composed of two major elements. The
first one is an object model, defined in
order to represent components of the different systems
addressed in this dissertation. Thus, this object
model performs the role of a unifying model, that is, a
model in which objects from different systems
can interact and be represented transparently.
The second element of our composition model is a design
pattern to implement bindings between
interpreted languages and component systems. This design
pattern, named Dynamic Language Binding,
does not use the traditional stubs technique. Instead of
this, it uses reflection and dynamic typing
to implement generic proxies, which can represent any
component of a specific system, and generic
adapters, which allow component implementations using the
composition language itself.
In order to validate our proposal, we describe the LuaOrb
system, which is an implementation
of our composition model. LuaOrb uses the interpreted
language Lua as its dynamic composition
language, and integrates the systems CORBA, COM and Java.
41
AFONSO, LUIZ MARQUES. "A STUDY ABOUT CONTRACTS IN SOFTWARE COMPONENT SYSTEMS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2008. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=13071@1.
Повний текст джерелаАнотація:
A programação por contratos é uma das técnicas voltadas
para a melhoria
da qualidade de software, sendo baseada no aumento do
formalismo da
especificação das interfaces. No contexto de componentes de
software distribuídos,
o uso de contratos envolve alguns desafios que o
diferenciam do
seu uso mais tradicional. O objetivo deste trabalho é a
avaliaação do uso de
contratos no desenvolvimento de sistemas distribuídos
baseados em componentes
de software, identificando as abordagens existentes e
analisando as
vantagens e desvantagens do seu uso. São também avaliadas
características
como robustez, desempenho, flexibilidade, facilidade de uso
e limitações.
Como estudo de caso, foi desenvolvido um subsistema de
suporte a contratos
sobre um middleware CORBA implementado em Lua, servindo de
base para experimentos realizados durante a pesquisa.<br>Contract-based programming is one of the techniques used to
improve the
quality of software by enhancing the formalism of interface
specifications.
In the context of distributed software components, the use
of contracts
presents new challenges that make it di*erent from its
traditional use.
This work intends to evaluate the use of contracts in the
development of
component-based distributed systems, identifying the
current approaches
and analyzing its advantages and disadvantages. It also
covers topics like
robustness, performance, flexibility, ease of use and
limitations. As a case
study, a contract subsystem was developed over a CORBA
middleware using
Lua, serving as the basis for experiments in our study.
42
Yusof, Yuhanis. "Functional and structural descriptors for software component retrieval." Thesis, Cardiff University, 2007. http://orca.cf.ac.uk/54611/.
Повний текст джерелаАнотація:
Identifying appropriate software components in a repository is an important task in software reuse after all, components must be found before they can be reused. Program source code documents written in a computer programming language has the possibility to be a software component. Program source code is a form of data, containing both structure and function it is therefore important to make use of this information in representing programs in a software repository. Existing approaches in software component retrieval systems focus on retrieving a component based on either its function or structure. Such an approach may not be suitable to users that require examples of programs that illustrate a particular function and structure, there is therefore a need for combining this information together. The objective of this research is to build a software repository of Java programs, to facilitate the search and selection of programs using the information about a program's function and structure. The hypothesis is that retrieval of program source code is better undertaken using a combination of functional and structural descriptors rather than using functional descriptors on their own. This thesis presents a program retrieval and indexing model which can be used in developing a source code retrieval system. The model reveals on how functional and structural descriptors are identified and combined into a single representation. The functional descriptors are identified by extracting selected terms from program source code and a weighting scheme is adopted to differentiate the importance of terms. As programs in the repository are from open-source applications, extracting information that does not rely on semantic terms would be beneficial, as these programs are written by various developers with different programming background and experience. Structural descriptors that comprise of information generated based on structural relationships, such as design patterns and software metrics, are extracted from a program to be added as the program descriptor. The functional and structural descriptors are combined into a single index, known as a compound index, which is used as a program descriptor. The degree of similarity between a given query and programs in a repository is identified using measurements undertaken based on vector model and data distribution based approaches. Lessons learned from the experiments undertaken reveals that programs retrieved using the proposed method are less complex and easy to maintain. Furthermore, it is suggested that programs from different application domains contain different trends in their software metrics.
43
Yin, Hang. "Introducing Mode Switch in Component-Based Software Development." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-28755.
Повний текст джерелаАнотація:
Self-adaptivity, characterized by the ability to dynamically adjust behavior at runtime, is a growing trend in the evolution of modern embedded systems. While self-adaptive systems tend to be flexible and autonomous, self-adaptivity may inevitably complicate software design, test and analysis. A strategy for taming the growing software complexity of self-adaptive systems is to partition system behaviors into different operational modes specified at design time. Such a multi-mode system can change behavior by switching between modes at runtime under certain circumstances. Multi-mode systems can benefit from a complementary approach to the software development of complex systems: Component-Based Software Engineering (CBSE), which fosters reuse of independently developed software components. However, the state-of-the-art component-based development of multi-mode systems does not take full advantage of CBSE, as reuse of modes at component level is barely addressed. Modes are often treated as system properties, while mode switches are handled by a global mode manager. This centralized mode management entails global information of all components, whereas the global information may be inaccessible in component-based systems. Another potential problem is that a single mode manager does not scale well, particularly at design time, for a large number of components and modes. In this thesis we propose a distributed solution to the component-based development of multi-mode systems, aiming for a more efficient and scalable mode management. Our goal is to fully incorporate modes in software component reuse, supporting reuse of multi-mode components, i.e., components able to run in multiple modes. We have developed a generic framework, the Mode-Switch Logic (MSL), which not only supports reuse of multi-mode components but also provides runtime mechanisms for handling mode switch. MSL includes three fundamental elements: (1) a mode-aware component model with the formal specification of reusable multi-mode software components; (2) a mode mapping mechanism for the seamless composition of multi-mode components; and (3) a mode-switch runtime mechanism which is executed by each component in isolation from its functional execution and coordinates the mode switches of different components without the need of global mode information. The mode-switch runtime mechanism has been verified by model checking in conjunction with mathematical proofs. We also provide a mode-switch timing analysis for the runtime mechanism to respect real-time requirements. MSL is dedicated to the mode aspect of a system irrespective of component execution semantics, thus independent of the choice of component models. We have integrated MSL in the ProCom component model with the extension of support for reuse of multi-mode components and distributed mode-switch handling. Although the distributed mode-switch handling of MSL is more flexible and scalable than the conventional centralized approach, when components are deployed on a single hardware platform and global mode information is available, centralized mode-switch handling is more efficient in terms of runtime overhead and mode-switch time. Hence, MSL is supplemented with a mode transformation technique to enhance runtime mode-switch efficiency by converting the distributed mechanism to a centralized mechanism. MSL together with the mode transformation technique has been implemented in a prototype tool where one can build multi-mode systems by reusing multi-mode components. The applicability of MSL is demonstrated in two proof-of-concept case studies.<br>ARROWS - Design Techniques for Adaptive Embedded Systems
44
Alves, André Nunes Gomes. "Healing replicas in a software component replication system." Master's thesis, Faculdade de Ciências e Tecnologia, 2013. http://hdl.handle.net/10362/11353.
Повний текст джерелаАнотація:
Dissertação para obtenção do Grau de Mestre em
Engenharia Informática<br>Replication is a key technique for improving performance, availability and faulttolerance
of systems. Replicated systems exist in different settings – from large georeplicated
cloud systems, to replicated databases running in multi-core machines. One
feature that it is often important is a mechanism to verify that replica contents continue in-sync, despite any problem that may occur – e.g. silent bugs that corrupt service state.
Traditional techniques for summarizing service state require that the internal service state is exactly the same after executing the same set of operation. However, for many applications this does not occur, especially if operations are allowed to execute in different orders or if different implementations are used in different replicas.
In this work we propose a new approach for summarizing and recovering the state of
a replicated service. Our approach is based on a novel data structure, Scalable Counting
Bloom Filter. This data structure combines the ideas in Counting Bloom Filters and Scalable Bloom Filters to create a Bloom Filter variant that allow both delete operation and the size of the structure to grow, thus adapting to size of any service state.
We propose an approach to use this data structure to summarize the state of a replicated service, while allowing concurrent operations to execute. We further propose a strategy to recover replicas in a replicated system and describe how to implement our proposed solution in two in-memory databases: H2 and HSQL. The results of evaluation show that our approach can compute the same summary when executing the same set of operation in both databases, thus allowing our solution to be used in diverse replication scenarios. Results also show that additional work on performance optimization is necessary to make our solution practical.
45
Reis, João Gabriel. "A framework for predictable hardware/software component reconfiguration." reponame:Repositório Institucional da UFSC, 2016. https://repositorio.ufsc.br/xmlui/handle/123456789/173819.
Повний текст джерелаАнотація:
Dissertação (mestrado) - Universidade Federal de Santa Catarina, Centro Tecnológico, Programa de Pós-Graduação em Engenharia Elétrica, Florianópolis, 2016.<br>Made available in DSpace on 2017-02-28T04:10:39Z (GMT). No. of bitstreams: 1
344671.pdf: 991636 bytes, checksum: 2e9b1460f30d38b6d198a17b08fe6d42 (MD5)
Previous issue date: 2016<br>Abstract : Rigid partitions of components or modules in a hardware/software co-design flow can lead to suboptimal choices in embedded systems with dynamic or unpredictable runtime requirements. Field-Programmable Gate Array (FPGA) reconfiguration can help systems cope with dynamic non-functional requirements such as performance and power, hardware defects due to Negative-Bias Temperature Instability (NBTI) and Process, Voltage and Temperature (PVT) variations, or application requirements unforeseen at design time. This work proposes a framework for reconfigurable components whereby the reconfiguration of a component implementation is performed transparently without user intervention. The reconfiguration process is confined in system?s idle time without interfering with or being interfered by other activities occurring in the system or even peripherals performing I/O. For components with multiple implementations, our approach opportunistically and speculatively monitors system load and performance parameters to check when the reconfiguration can start. The framework differs from previous approaches in its syntax and semantics for reconfigurable components which are preserved across the multiple implementations in different substrates and the reconfiguration process that can be split into multiple steps. To quantify the impact of I/O interference on FPGA reconfiguration, we measured the execution time when loading bitstreams containing hardware components implementations from memory to the FPGA reconfiguration interface with multiple peripherals performing I/O in parallel. Moreover, a Private Automatic Branch Exchange (PABX) case study investigated the deployment of reconfigurable components in a scenario with timing constraints. A reconfiguration policy for the PABX components was proposed to deal with the unpredictable number of calls it receives by using reconfigurable hardware resources without degrading voice quality due to reconfiguration. Furthermore, we explored trade-offs between power consumption, execution time, and accuracy in a set of reconfigurable mathematical components.<br><br>O particionamento estático de componentes ou módulos ao realizar o co-design hardware/software pode levar a escolhas insatisfatórias em sistemas embarcados com requisitos dinâmicos e imprevisíveis durante tempo de execução. A reconfiguração dinâmica de Field-Programmable Gate Arrays {FPGAs) pode ajudar sistemas a se adaptar em requisitos dinâmicos e não funcionais como desempenho e consumo de energia, defeitos de hardware devido ao fenômeno Negative-Bias Temperature Instability (NBTI) e variações de Processo, Tensão e Temperatura ou ainda requisitos da aplicação que não foram levados em consideração em tempo de projeto. Esse trabalho propõe um framework para componentes reconfiguráveis onde a reconfiguração da implementação de um componente é realizada de maneira transparente e sem a intervenção do usuário. O processo de reconfiguração é confinado no tempo ocioso do sistema sem interferir ou sofrer interferência de outras atividades ou mesmo periféricos realizando operações de entrada/saída. Para componentes com múltiplas implementações, nossa abordagem monitora de maneira especulativa a carga do sistema e contadores de desempenho para escolher o momento em que a reconfiguração deve se iniciar. O framework se difere de trabalhos anteriores devido à sintaxe e semântica para componentes reconfiguráveis que são preservadas nas múltiplas implementações e em diferentes substratos e no processo de reconfiguração que pode ser dividido em diversos passos. Para quantificar o impacto da interferência de entrada/saída na reconfiguração de FPGAs, foi medido o tempo de execução para carregar bitstreams contendo implementações de componentes em hardware da memória para a interface de reconfiguração de FPGA com diversos periféricos realizando operações de entrada/saída em paralelo. Além disso, o estudo de caso de um Private Automatic Branch Exchange (PABX) investigou o uso de componentes reconfiguráveis num cenário com requisitos temporais. Uma política de reconfiguração para os componentes do (PABX) foi proposta para lidar o número imprevisível de chamadas recebidas através de recursos reconfiguráveis sem degradar a qualidade da reprodução da voz devido à reconfiguração. Foram também explorados os trade-offs entre consumo de energia, tempo de execução e exatidão dos resultados num conjunto de componentes implementando operações matemáticas.
46
Parry, Dominic Charles. "CREWS : a Component-driven, Run-time Extensible Web Service framework." Thesis, Rhodes University, 2004. http://eprints.ru.ac.za/74/.
Повний текст джерела
47
Mehta, Alok. "Evolving legacy system's features into fine-grained components using regression test-cases." Link to electronic thesis, 2002. http://www.wpi.edu/Pubs/ETD/Available/etd-1211102-163800.
Повний текст джерелаАнотація:
Dissertatio (Ph. D.)--Worcester Polytechnic Institute.<br>Keywords: software maintenance; software evolution; regression test-cases; components; legacy system; incremental software evolution methodology; fine-grained components. Includes bibliographical references (p. 283-294).
48
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.
Повний текст джерелаАнотація:
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: 2008<br>A 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
49
Tuncel, Mehmet Burhan. "Using Collaboration Diagrams In Component Oriented Modeling." Master's thesis, METU, 2006. http://etd.lib.metu.edu.tr/upload/12607042/index.pdf.
Повний текст джерелаАнотація:
Component Oriented Software Engineering (COSE) seems to be the future of software engineering. Currently, COSEML is the only modeling language that completely supports the COSE approach. Abstract decomposition of the system and their representing components are shown in a hierarchy diagram to support the COSE process model. In COSEML, only static modeling is supported through this single diagram. However, software is about behavior and static modeling is not sufficient to describe the system. The aim of this thesis is providing the benefits of dynamic modeling to COSEML by adopting collaboration diagrams. For this purpose, first, specification of modified collaboration diagrams is made for COSEML. Then software is developed for supporting collaboration diagrams in COSECASE. Also, an e-store application is modeled with COSEML using the collaboration diagrams. With this work, modeling the dynamic behavior of the system in both abstract and component levels is made possible. Furthermore, use case realization is enabled in the COSE modeling. More important, modeling the sequential interactions among components is made possible. Consequently, a suitable environment is provided for automated testing and application generation from the model.
50
Reid, Stuart Christopher. "Software component testing : a standard and the effectiveness of techniques." Thesis, University of South Wales, 1997. https://pure.southwales.ac.uk/en/studentthesis/software-component-testing(14d22b70-809b-44e4-8240-12a5ead3fdd6).html.
Повний текст джерелаАнотація:
This portfolio comprises two projects linked by the theme of software component testing, which is also often referred to as module or unit testing. One project covers its standardisation, while the other considers the analysis and evaluation of the application of selected testing techniques to an existing avionics system. The evaluation is based on empirical data obtained from fault reports relating to the avionics system. The standardisation project is based on the development of the BC BSI Software Component Testing Standard and the BCS/BSI Glossary of terms used in software testing, which are both included in the portfolio. The papers included for this project consider both those issues concerned with the adopted development process and the resolution of technical matters concerning the definition of the testing techniques and their associated measures. The test effectiveness project documents a retrospective analysis of an operational avionics system to determine the relative effectiveness of several software component testing techniques. The methodology differs from that used in other test effectiveness experiments in that it considers every possible set of inputs that are required to satisfy a testing technique rather than arbitrarily chosen values from within this set. The three papers present the experimental methodology used, intermediate results from a failure analysis of the studied system, and the test effectiveness results for ten testing techniques, definitions for which were taken from the BCS BSI Software Component Testing Standard. The creation of the two standards has filled a gap in both the national and international software testing standards arenas. Their production required an in-depth knowledge of software component testing techniques, the identification and use of a development process, and the negotiation of the standardisation process at a national level. The knowledge gained during this process has been disseminated by the author in the papers included as part of this portfolio. The investigation of test effectiveness has introduced a new methodology for determining the test effectiveness of software component testing techniques by means of a retrospective analysis and so provided a new set of data that can be added to the body of empirical data on software component testing effectiveness.