<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-18T23:36:46Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/28367" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/28367</identifier><datestamp>2022-02-03T03:12:52Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131022</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">Michael W. Golay.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Zhang, Yi</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Dept. of Nuclear Engineering.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Massachusetts Institute of Technology. Department of Nuclear Engineering</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Nuclear Science and Engineering</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2005-09-26T20:04:09Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-09-26T20:04:09Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2004</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2004</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/28367</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">56204497</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Nuclear Engineering, 2004.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Page 242 blank.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 238-241).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The objective of this study is to improve quality and reliability of safety-critical software in the nuclear industry. It is accomplished by focusing on the following two areas: Formulation of a standard extensive integrated software testing strategy for safety-critical software, and Development of systematic test-based statistical software reliability quantification methodologies. The first step to improving the overall performance of software is to develop a comprehensive testing strategy, the gray box testing method. It has incorporated favorable aspects of white box and black box testing techniques. The safety-critical features of the software and feasibility of the methodology are the key drivers in determining the architecture for the testing strategy. Monte Carlo technique is applied to randomly sample inputs based on the probability density function derived from the specification of the given software. Software flowpaths accessed during testing are identified and recorded. Complete nodal coverage testing is achieved by automatic coverage checking. It is guaranteed that the most popular flowpaths of the software are tested.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The second part of the methodology is the quantification of software performance. Two Bayesian based white box reliability estimation methodologies, nodal coverage- based and flowpath coverage-based, are developed. The number of detected errors and the failure-free operations, the objective and subjective knowledge of the given software, and the testing and software structure information are systematically incorporated into both reliability estimation approaches. The concept of two error groups in terms of testability is initiated to better capture reliability features of the given software. The reliability of the tested flowpaths of the software and that of the untested flowpaths can be updated at any point during testing. Overall software reliability is calculated as a weighted average of the tested and untested parts of the software, with the probability of being visited upon next execution as the weight of each part. All of the designed testing and reliability estimation strategies are successfully implemented and automated via various software tools and demonstrated on a typical safety-critical software application.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Yi Zhang.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">Ph.D.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">242 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">10293487 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">10293285 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso">en_US</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Nuclear Engineering.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Reliability quantification of nuclear safety-related software</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="ff06241b-b36d-40d1-acf7-f34978fbd7ff">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>en_US&lt;/Language>
   	&lt;Title>Reliability quantification of nuclear safety-related software&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2004&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Zhang, Yi&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>Nuclear Engineering.&lt;/Keyword>
   	&lt;Abstract>The objective of this study is to improve quality and reliability of safety-critical software in the nuclear industry. It is accomplished by focusing on the following two areas: Formulation of a standard extensive integrated software testing strategy for safety-critical software, and Development of systematic test-based statistical software reliability quantification methodologies. The first step to improving the overall performance of software is to develop a comprehensive testing strategy, the gray box testing method. It has incorporated favorable aspects of white box and black box testing techniques. The safety-critical features of the software and feasibility of the methodology are the key drivers in determining the architecture for the testing strategy. Monte Carlo technique is applied to randomly sample inputs based on the probability density function derived from the specification of the given software. Software flowpaths accessed during testing are identified and recorded. Complete nodal coverage testing is achieved by automatic coverage checking. It is guaranteed that the most popular flowpaths of the software are tested.&lt;/Abstract>
   	&lt;Abstract>The second part of the methodology is the quantification of software performance. Two Bayesian based white box reliability estimation methodologies, nodal coverage- based and flowpath coverage-based, are developed. The number of detected errors and the failure-free operations, the objective and subjective knowledge of the given software, and the testing and software structure information are systematically incorporated into both reliability estimation approaches. The concept of two error groups in terms of testability is initiated to better capture reliability features of the given software. The reliability of the tested flowpaths of the software and that of the untested flowpaths can be updated at any point during testing. Overall software reliability is calculated as a weighted average of the tested and untested parts of the software, with the probability of being visited upon next execution as the weight of each part. All of the designed testing and reliability estimation strategies are successfully implemented and automated via various software tools and demonstrated on a typical safety-critical software application.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>