Using certification trails to achieve software fault tolerance
A technique for achieving fault tolerance in hardware and software systems is introduced. When used for software fault tolerance, this technique uses time and software redundancy and can be outlined as follows. In the initial phase, a program is run to solve a problem and store the results. In addit...
Gespeichert in:
| Hauptverfasser: | , |
|---|---|
| Format: | Tagungsbericht |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext bestellen |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 431 |
|---|---|
| container_issue | |
| container_start_page | 423 |
| container_title | |
| container_volume | |
| creator | Sullivan, G.F. Masson, G.M. |
| description | A technique for achieving fault tolerance in hardware and software systems is introduced. When used for software fault tolerance, this technique uses time and software redundancy and can be outlined as follows. In the initial phase, a program is run to solve a problem and store the results. In addition, this program leaves behind a trail of data, called a certification trail. In the second phase, another program is run, and it solves the original problem again. This program, however, has access to the certification trail left by the first program. Because of the availability of the certification trail, the second phase can be performed by a less complex program and can execute more quickly. In the final phase, the two results are compared, and if they agree, the results are accepted as correct; otherwise, an error is indicated. Cases in which the second phase can be run concurrently with the first and act as a monitor are discussed.< > |
| doi_str_mv | 10.1109/FTCS.1990.89397 |
| format | Conference Proceeding |
| fullrecord | <record><control><sourceid>ieee_6IE</sourceid><recordid>TN_cdi_ieee_primary_89397</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>89397</ieee_id><sourcerecordid>89397</sourcerecordid><originalsourceid>FETCH-LOGICAL-i1277-7177cb0839525589d25037ed8ff7e31eae86a06420ca56dff93461790f615f7c3</originalsourceid><addsrcrecordid>eNotj01LxDAURQMiKGPX4i5_oPW9ZPK1EaQ4Kgy4cGY9xPRFI7WVJCr-e4t6N3dx4B4uY-cIHSK4y82uf-zQOeisk84cscYZCxatFqBQnbCmlFdYopSVKE7Z1b6k6ZkHyjXFFHxN88Rr9mksvM7ch5dEn8TLHOuXz8Sj_xjrQkbKfgp0xo6jHws1_71i-83Nrr9rtw-39_31tk0ojGkNGhOewEqnxGJ2g1AgDQ02RkMSyZPVHvRaQPBKDzE6udZoHESNKpogV-zibzcR0eE9pzefvw-_H-UPCBJGeA</addsrcrecordid><sourcetype>Publisher</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>Using certification trails to achieve software fault tolerance</title><source>IEEE Electronic Library (IEL) Conference Proceedings</source><creator>Sullivan, G.F. ; Masson, G.M.</creator><creatorcontrib>Sullivan, G.F. ; Masson, G.M.</creatorcontrib><description>A technique for achieving fault tolerance in hardware and software systems is introduced. When used for software fault tolerance, this technique uses time and software redundancy and can be outlined as follows. In the initial phase, a program is run to solve a problem and store the results. In addition, this program leaves behind a trail of data, called a certification trail. In the second phase, another program is run, and it solves the original problem again. This program, however, has access to the certification trail left by the first program. Because of the availability of the certification trail, the second phase can be performed by a less complex program and can execute more quickly. In the final phase, the two results are compared, and if they agree, the results are accepted as correct; otherwise, an error is indicated. Cases in which the second phase can be run concurrently with the first and act as a monitor are discussed.< ></description><identifier>ISBN: 9780818620515</identifier><identifier>ISBN: 081862051X</identifier><identifier>DOI: 10.1109/FTCS.1990.89397</identifier><language>eng</language><publisher>IEEE Comput. Soc. Press</publisher><subject>Availability ; Certification ; Computer science ; Error correction ; Fault detection ; Fault tolerance ; Fault tolerant systems ; Hardware ; Monitoring ; Redundancy</subject><ispartof>[1990] Digest of Papers. Fault-Tolerant Computing: 20th International Symposium, 1990, p.423-431</ispartof><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/89397$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>309,310,780,784,789,790,2058,4050,4051,27925,54920</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/89397$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Sullivan, G.F.</creatorcontrib><creatorcontrib>Masson, G.M.</creatorcontrib><title>Using certification trails to achieve software fault tolerance</title><title>[1990] Digest of Papers. Fault-Tolerant Computing: 20th International Symposium</title><addtitle>FTCS</addtitle><description>A technique for achieving fault tolerance in hardware and software systems is introduced. When used for software fault tolerance, this technique uses time and software redundancy and can be outlined as follows. In the initial phase, a program is run to solve a problem and store the results. In addition, this program leaves behind a trail of data, called a certification trail. In the second phase, another program is run, and it solves the original problem again. This program, however, has access to the certification trail left by the first program. Because of the availability of the certification trail, the second phase can be performed by a less complex program and can execute more quickly. In the final phase, the two results are compared, and if they agree, the results are accepted as correct; otherwise, an error is indicated. Cases in which the second phase can be run concurrently with the first and act as a monitor are discussed.< ></description><subject>Availability</subject><subject>Certification</subject><subject>Computer science</subject><subject>Error correction</subject><subject>Fault detection</subject><subject>Fault tolerance</subject><subject>Fault tolerant systems</subject><subject>Hardware</subject><subject>Monitoring</subject><subject>Redundancy</subject><isbn>9780818620515</isbn><isbn>081862051X</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>1990</creationdate><recordtype>conference_proceeding</recordtype><sourceid>6IE</sourceid><sourceid>RIE</sourceid><recordid>eNotj01LxDAURQMiKGPX4i5_oPW9ZPK1EaQ4Kgy4cGY9xPRFI7WVJCr-e4t6N3dx4B4uY-cIHSK4y82uf-zQOeisk84cscYZCxatFqBQnbCmlFdYopSVKE7Z1b6k6ZkHyjXFFHxN88Rr9mksvM7ch5dEn8TLHOuXz8Sj_xjrQkbKfgp0xo6jHws1_71i-83Nrr9rtw-39_31tk0ojGkNGhOewEqnxGJ2g1AgDQ02RkMSyZPVHvRaQPBKDzE6udZoHESNKpogV-zibzcR0eE9pzefvw-_H-UPCBJGeA</recordid><startdate>1990</startdate><enddate>1990</enddate><creator>Sullivan, G.F.</creator><creator>Masson, G.M.</creator><general>IEEE Comput. Soc. Press</general><scope>6IE</scope><scope>6IL</scope><scope>CBEJK</scope><scope>RIE</scope><scope>RIL</scope></search><sort><creationdate>1990</creationdate><title>Using certification trails to achieve software fault tolerance</title><author>Sullivan, G.F. ; Masson, G.M.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-i1277-7177cb0839525589d25037ed8ff7e31eae86a06420ca56dff93461790f615f7c3</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>1990</creationdate><topic>Availability</topic><topic>Certification</topic><topic>Computer science</topic><topic>Error correction</topic><topic>Fault detection</topic><topic>Fault tolerance</topic><topic>Fault tolerant systems</topic><topic>Hardware</topic><topic>Monitoring</topic><topic>Redundancy</topic><toplevel>online_resources</toplevel><creatorcontrib>Sullivan, G.F.</creatorcontrib><creatorcontrib>Masson, G.M.</creatorcontrib><collection>IEEE Electronic Library (IEL) Conference Proceedings</collection><collection>IEEE Proceedings Order Plan All Online (POP All Online) 1998-present by volume</collection><collection>IEEE Xplore All Conference Proceedings</collection><collection>IEEE Electronic Library (IEL)</collection><collection>IEEE Proceedings Order Plans (POP All) 1998-Present</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Sullivan, G.F.</au><au>Masson, G.M.</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>Using certification trails to achieve software fault tolerance</atitle><btitle>[1990] Digest of Papers. Fault-Tolerant Computing: 20th International Symposium</btitle><stitle>FTCS</stitle><date>1990</date><risdate>1990</risdate><spage>423</spage><epage>431</epage><pages>423-431</pages><isbn>9780818620515</isbn><isbn>081862051X</isbn><abstract>A technique for achieving fault tolerance in hardware and software systems is introduced. When used for software fault tolerance, this technique uses time and software redundancy and can be outlined as follows. In the initial phase, a program is run to solve a problem and store the results. In addition, this program leaves behind a trail of data, called a certification trail. In the second phase, another program is run, and it solves the original problem again. This program, however, has access to the certification trail left by the first program. Because of the availability of the certification trail, the second phase can be performed by a less complex program and can execute more quickly. In the final phase, the two results are compared, and if they agree, the results are accepted as correct; otherwise, an error is indicated. Cases in which the second phase can be run concurrently with the first and act as a monitor are discussed.< ></abstract><pub>IEEE Comput. Soc. Press</pub><doi>10.1109/FTCS.1990.89397</doi><tpages>9</tpages><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | ISBN: 9780818620515 |
| ispartof | [1990] Digest of Papers. Fault-Tolerant Computing: 20th International Symposium, 1990, p.423-431 |
| issn | |
| language | eng |
| recordid | cdi_ieee_primary_89397 |
| source | IEEE Electronic Library (IEL) Conference Proceedings |
| subjects | Availability Certification Computer science Error correction Fault detection Fault tolerance Fault tolerant systems Hardware Monitoring Redundancy |
| title | Using certification trails to achieve software fault tolerance |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-25T03%3A59%3A36IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-ieee_6IE&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=Using%20certification%20trails%20to%20achieve%20software%20fault%20tolerance&rft.btitle=%5B1990%5D%20Digest%20of%20Papers.%20Fault-Tolerant%20Computing:%2020th%20International%20Symposium&rft.au=Sullivan,%20G.F.&rft.date=1990&rft.spage=423&rft.epage=431&rft.pages=423-431&rft.isbn=9780818620515&rft.isbn_list=081862051X&rft_id=info:doi/10.1109/FTCS.1990.89397&rft_dat=%3Cieee_6IE%3E89397%3C/ieee_6IE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=89397&rfr_iscdi=true |