Thesis (M.S.)--Worcester Polytechnic Institute. / Keywords: formal analysis; active interfaces; Z notations; EJ. Includes bibliographical references (p. 97-99).

Thesis (Ph. D.)--University of Washington, 2004. / Vita. Includes bibliographical references (leaves 95-101).

This thesis is devoted to a component model for Web application and the corresponding tools for its development. The model is described after the review of various existing Web application development methods and models. A case study is also provided to support the analysis. -- abstract / Thesis (PhD)--University of South Australia, 2003.

Thesis (Ph. D.)--University of Alabama at Birmingham, 2007. / Additional advisors: Gary J. Grimes, Chittoor V. Ramamoorthy, Murat N. Tanju, Gregg L. Vaughn, B. Earl Wells. Description based on contents viewed Feb. 12, 2009; title from PDF t.p. Includes bibliographical references (p. 150-158).

Dissertatio (Ph. D.)--Worcester Polytechnic Institute. / Keywords: software maintenance; software evolution; regression test-cases; components; legacy system; incremental software evolution methodology; fine-grained components. Includes bibliographical references (p. 283-294).

Thesis (doctoral)--University of Oulu, 2000. / Includes bibliographical references. Also available on the World Wide Web.

Thesis (Ph. D.)--University of Texas at Dallas, 2007. / Includes vita. Includes bibliographical references (leaves 201-214)

Thesis (Ph.D.)--University of Nebraska-Lincoln, 2008. / Title from title screen (site viewed Jan. 13, 2009). PDF text: 121 p. : ill. (some col.) ; 2 Mb. UMI publication number: AAT 3315322. Includes bibliographical references. Also available in microfilm and microfiche formats.

Finally, we formulate the relationship between code coverage and fault detection. Although our two current models are in simple mathematical formats, they can predict the percentage of fault detected by the code coverage achieved for a certain test set. We further incorporate such formulation into traditional reliability growth models, not only for fault-tolerant software, but also for general software system. Our empirical evaluations show that our new reliability model can achieve more accurate reliability assessment than the traditional Non-homogenous Poisson model. / Furthermore, to investigate some "variants" as well as "invariants" of fault-tolerant software, we perform an empirical investigation on evaluating reliability features by a comprehensive comparison between two projects: our project and NASA 4-University project. Based on the same specification for program development, these two projects encounter some common as well as different features. The testing results of two comprehensive operational testing procedures involving hundreds of thousands test cases are collected and compared. Similar as well as dissimilar faults are observed and analyzed, indicating common problems related to the same application in both projects. The small number of coincident failures in the two projects, nevertheless, provide a supportive evidence for N-version programming, while the observed reliability improvement implies some trends in the software development in the past twenty years. / Motivated by the lack of real-world project data for investigation on software testing and fault tolerance techniques together, we conduct a real-world project and engage multiple programming teams to independently develop program versions based on an industry-scale avionics application. Detailed experimentations are conducted to study the nature, source, type, detectability, and effect of faults uncovered in the program versions, and to learn the relationship among these faults and the correlation of their resulting failures. Coverage-based testing as well as mutation testing techniques are adopted to reproduce mutants with real faults, which facilitate the investigation on the effectiveness of data flow coverage, mutation coverage, and fault coverage for design diversity. / Next, we investigate the effect of code coverage on fault detection which is the underlying intuition of coverage-based testing strategies. From our experimental data, we find that code coverage is a moderate indicator for the capability of fault detection on the whole test set. But the effect of code coverage on fault detection varies under different testing profiles. The correlation between the two measures is high with exceptional test cases, but weak in normal testing. Moreover, our study shows that code coverage can be used as a good filter to reduce the size of the effective test set, although it is more evident for exceptional test cases. / Software permeates our modern society, and its complexity and criticality is ever increasing. Thus the capability to tolerate software faults, particularly for critical applications, is evident. While fault-tolerant software is seen as a necessity, it also remains as a controversial technique and there is a lack of conclusive assessment about its effectiveness. / Then, based on the preliminary experimental data, further experimentation and detailed analyses on the correlations among these faults and the relation to their resulting failures are studied. The results are further applied to the current reliability modeling techniques for fault-tolerant software to examine their effectiveness and accuracy. / This thesis aims at providing a quantitative assessment scheme for a comprehensive evaluation of fault-tolerant software including reliability model comparisons and trade-off studies with software testing techniques. First of all, we propose a comprehensive procedure in assessing fault-tolerant software for software reliability engineering, which is composed of four tasks: modeling, experimentation, evaluation and economics. Our ultimate objective is to construct a systematic approach to predicting the achievable reliability based on the software architecture and testing evidences, through an investigation of testing and modeling techniques for fault-tolerant software. / Cai Xia. / "September 2006." / Adviser: Rung Tsong Michael Lyu. / Source: Dissertation Abstracts International, Volume: 68-03, Section: B, page: 1715. / Thesis (Ph.D.)--Chinese University of Hong Kong, 2006. / Includes bibliographical references (p. 165-181). / Electronic reproduction. Hong Kong : Chinese University of Hong Kong, [2012] System requirements: Adobe Acrobat Reader. Available via World Wide Web. / Electronic reproduction. [Ann Arbor, MI] : ProQuest Information and Learning, [200-] System requirements: Adobe Acrobat Reader. Available via World Wide Web. / Abstracts in English and Chinese. / School code: 1307.

Building software systems from previously existing components can save time and effort while increasing productivity. The key to a successful Component-Based Development (CBD) is to get the required components. However, components obtained from other developers often show different behaviours than what are required. Thus adapting the components into the system being developed becomes an extra development and maintenance cost. This cost often offsets the benefits of CBD. Our research goal is to maximise the possibility of finding components that have the required behaviours, so that the component adaptation cost can be minimised. Imprecise component specifications and user requirements are the main reasons that cause the difficulty of finding the required components. Furthermore, there is little support for component users and developers to collaborate and clear the misunderstanding when selecting components, as CBD has two separate development processes for them. In this thesis, we aim at building a framework in which component users and developers can collaborate to select components with tools support, by exchanging component and requirement specifications. These specifications should be precise enough so that behavioural mismatches can be detected. We have defined Simple Component Interface Language (SCIL) as the communication and specification language to capture component behaviours. A combined SCIL specification of component and requirement can be translated to various existing modelling languages. Thus various properties that are supported by those languages can be checked by the related model checking tools. If all the user-required properties are satisfied, then the component is compatible to the user requirement at the behavioural level. Thus the component can be selected. Based on SCIL, we have developed a prototype component selection system and used it in two case studies: finding a spell checker component and searching for the components for a generic e-commerce application. The results of the case studies indicate that our approach can indeed find components that have the required behaviours. Compared to the traditional way of searching by keywords, our approach is able to get more relevant results, so the cost of component adaptation can be reduced. Furthermore, with a collaborative selection process this cost can be minimised. However, our approach has not achieved complete automation due to the modelling inconsistency from different people. Some manual work to adjust user requirements is needed when using our system. The future work will focus on solving this remaining problem of inconsistent modelling, providing an automatic trigger to select proper tools, etc.