Software safety
The author considers four issues that prevent software safety from sometimes getting the attention it deserves: safety is often confused with security and reliability; safety is viewed as a system-level problem; software failures are subtle; and safety cannot be proven. He presents his software safe...
Gespeichert in:
| Veröffentlicht in: | IEEE software 2002-07, Vol.19 (4), p.84-85 |
|---|---|
| 1. Verfasser: | |
| Format: | Artikel |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext bestellen |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 85 |
|---|---|
| container_issue | 4 |
| container_start_page | 84 |
| container_title | IEEE software |
| container_volume | 19 |
| creator | Tribble, A.C. |
| description | The author considers four issues that prevent software safety from sometimes getting the attention it deserves: safety is often confused with security and reliability; safety is viewed as a system-level problem; software failures are subtle; and safety cannot be proven. He presents his software safety predictions. |
| doi_str_mv | 10.1109/MS.2002.1020292 |
| format | Article |
| fullrecord | <record><control><sourceid>proquest_RIE</sourceid><recordid>TN_cdi_crossref_primary_10_1109_MS_2002_1020292</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>1020292</ieee_id><sourcerecordid>138713611</sourcerecordid><originalsourceid>FETCH-LOGICAL-c380t-a7512c66b458e4bc1dfcd61579b435d7287ee6fe8fea57328dc776ecd4e6454e3</originalsourceid><addsrcrecordid>eNqF0D1LA0EQBuBFFIxRLC1sxEKrS2Y_Z7eU4BckWETrZbM3CwlJLt5ekPx7L1wKsdBqinlmhnkZu-Iw4BzccDIdCAAx4CBAOHHEetxJLBR36pj1ABUUqLQ7ZWc5LwBAcwk9djmtUvMVarrJIVGzO2cnKSwzXRxqn308Pb6PXorx2_Pr6GFcRGmhKQJqLqIxM6UtqVnkZYql4RrdTEldorBIZBLZREGjFLaMiIZiqcgorUj22X23d1NXn1vKjV_Nc6TlMqyp2mbvAJ0Cq3Ur7_6U7SmruYH_ISI4IbGFt7_gotrW6_ZdL7i2wiptWjTsUKyrnGtKflPPV6HeeQ5-H7ifTP0-cH8IvJ247ibmRPRDd91vKLd4dQ</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>215828456</pqid></control><display><type>article</type><title>Software safety</title><source>IEEE Electronic Library (IEL)</source><creator>Tribble, A.C.</creator><creatorcontrib>Tribble, A.C.</creatorcontrib><description>The author considers four issues that prevent software safety from sometimes getting the attention it deserves: safety is often confused with security and reliability; safety is viewed as a system-level problem; software failures are subtle; and safety cannot be proven. He presents his software safety predictions.</description><identifier>ISSN: 0740-7459</identifier><identifier>EISSN: 1937-4194</identifier><identifier>DOI: 10.1109/MS.2002.1020292</identifier><identifier>CODEN: IESOEG</identifier><language>eng</language><publisher>Los Alamitos: IEEE</publisher><subject>Accidents ; Aircraft ; Compliance ; Computer programs ; Design ; Designers ; Failure ; Failure analysis ; Fellows ; Hardware ; Logic design ; Medical robotics ; Safety ; Security ; Software ; Software design ; Software quality ; Software safety ; Testing</subject><ispartof>IEEE software, 2002-07, Vol.19 (4), p.84-85</ispartof><rights>Copyright Institute of Electrical and Electronics Engineers, Inc. (IEEE) Jul/Aug 2002</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c380t-a7512c66b458e4bc1dfcd61579b435d7287ee6fe8fea57328dc776ecd4e6454e3</citedby></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/1020292$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>314,780,784,796,27924,27925,54758</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/1020292$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Tribble, A.C.</creatorcontrib><title>Software safety</title><title>IEEE software</title><addtitle>S-M</addtitle><description>The author considers four issues that prevent software safety from sometimes getting the attention it deserves: safety is often confused with security and reliability; safety is viewed as a system-level problem; software failures are subtle; and safety cannot be proven. He presents his software safety predictions.</description><subject>Accidents</subject><subject>Aircraft</subject><subject>Compliance</subject><subject>Computer programs</subject><subject>Design</subject><subject>Designers</subject><subject>Failure</subject><subject>Failure analysis</subject><subject>Fellows</subject><subject>Hardware</subject><subject>Logic design</subject><subject>Medical robotics</subject><subject>Safety</subject><subject>Security</subject><subject>Software</subject><subject>Software design</subject><subject>Software quality</subject><subject>Software safety</subject><subject>Testing</subject><issn>0740-7459</issn><issn>1937-4194</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2002</creationdate><recordtype>article</recordtype><sourceid>RIE</sourceid><sourceid>8G5</sourceid><sourceid>ABUWG</sourceid><sourceid>AFKRA</sourceid><sourceid>AZQEC</sourceid><sourceid>BENPR</sourceid><sourceid>CCPQU</sourceid><sourceid>DWQXO</sourceid><sourceid>GNUQQ</sourceid><sourceid>GUQSH</sourceid><sourceid>M2O</sourceid><recordid>eNqF0D1LA0EQBuBFFIxRLC1sxEKrS2Y_Z7eU4BckWETrZbM3CwlJLt5ekPx7L1wKsdBqinlmhnkZu-Iw4BzccDIdCAAx4CBAOHHEetxJLBR36pj1ABUUqLQ7ZWc5LwBAcwk9djmtUvMVarrJIVGzO2cnKSwzXRxqn308Pb6PXorx2_Pr6GFcRGmhKQJqLqIxM6UtqVnkZYql4RrdTEldorBIZBLZREGjFLaMiIZiqcgorUj22X23d1NXn1vKjV_Nc6TlMqyp2mbvAJ0Cq3Ur7_6U7SmruYH_ISI4IbGFt7_gotrW6_ZdL7i2wiptWjTsUKyrnGtKflPPV6HeeQ5-H7ifTP0-cH8IvJ247ibmRPRDd91vKLd4dQ</recordid><startdate>20020701</startdate><enddate>20020701</enddate><creator>Tribble, A.C.</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7XB</scope><scope>87Z</scope><scope>88F</scope><scope>88I</scope><scope>88K</scope><scope>8AL</scope><scope>8FE</scope><scope>8FG</scope><scope>8FK</scope><scope>8FL</scope><scope>8G5</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>ARAPS</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BEZIV</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>FRNLG</scope><scope>F~G</scope><scope>GNUQQ</scope><scope>GUQSH</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K60</scope><scope>K6~</scope><scope>K7-</scope><scope>L.-</scope><scope>L6V</scope><scope>M0C</scope><scope>M0N</scope><scope>M1Q</scope><scope>M2O</scope><scope>M2P</scope><scope>M2T</scope><scope>M7S</scope><scope>MBDVC</scope><scope>P5Z</scope><scope>P62</scope><scope>PQBIZ</scope><scope>PQBZA</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PTHSS</scope><scope>Q9U</scope><scope>7SC</scope><scope>8FD</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><scope>7SP</scope><scope>F28</scope><scope>FR3</scope></search><sort><creationdate>20020701</creationdate><title>Software safety</title><author>Tribble, A.C.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c380t-a7512c66b458e4bc1dfcd61579b435d7287ee6fe8fea57328dc776ecd4e6454e3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2002</creationdate><topic>Accidents</topic><topic>Aircraft</topic><topic>Compliance</topic><topic>Computer programs</topic><topic>Design</topic><topic>Designers</topic><topic>Failure</topic><topic>Failure analysis</topic><topic>Fellows</topic><topic>Hardware</topic><topic>Logic design</topic><topic>Medical robotics</topic><topic>Safety</topic><topic>Security</topic><topic>Software</topic><topic>Software design</topic><topic>Software quality</topic><topic>Software safety</topic><topic>Testing</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Tribble, A.C.</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>Access via ABI/INFORM (ProQuest)</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Global (Alumni Edition)</collection><collection>Military Database (Alumni Edition)</collection><collection>Science Database (Alumni Edition)</collection><collection>Telecommunications (Alumni Edition)</collection><collection>Computing Database (Alumni Edition)</collection><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection (Alumni Edition)</collection><collection>Research Library (Alumni Edition)</collection><collection>Materials Science & Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>Advanced Technologies & Aerospace Collection</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Business Premium Collection</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>Business Premium Collection (Alumni)</collection><collection>ABI/INFORM Global (Corporate)</collection><collection>ProQuest Central Student</collection><collection>Research Library Prep</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Computer Science Collection</collection><collection>ProQuest Business Collection (Alumni Edition)</collection><collection>ProQuest Business Collection</collection><collection>Computer Science Database</collection><collection>ABI/INFORM Professional Advanced</collection><collection>ProQuest Engineering Collection</collection><collection>ABI/INFORM Global</collection><collection>Computing Database</collection><collection>Military Database</collection><collection>Research Library</collection><collection>Science Database</collection><collection>Telecommunications Database</collection><collection>Engineering Database</collection><collection>Research Library (Corporate)</collection><collection>Advanced Technologies & Aerospace Database</collection><collection>ProQuest Advanced Technologies & Aerospace Collection</collection><collection>ProQuest One Business</collection><collection>ProQuest One Business (Alumni)</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>Engineering Collection</collection><collection>ProQuest Central Basic</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><collection>Electronics & Communications Abstracts</collection><collection>ANTE: Abstracts in New Technology & Engineering</collection><collection>Engineering Research Database</collection><jtitle>IEEE software</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Tribble, A.C.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Software safety</atitle><jtitle>IEEE software</jtitle><stitle>S-M</stitle><date>2002-07-01</date><risdate>2002</risdate><volume>19</volume><issue>4</issue><spage>84</spage><epage>85</epage><pages>84-85</pages><issn>0740-7459</issn><eissn>1937-4194</eissn><coden>IESOEG</coden><abstract>The author considers four issues that prevent software safety from sometimes getting the attention it deserves: safety is often confused with security and reliability; safety is viewed as a system-level problem; software failures are subtle; and safety cannot be proven. He presents his software safety predictions.</abstract><cop>Los Alamitos</cop><pub>IEEE</pub><doi>10.1109/MS.2002.1020292</doi><tpages>2</tpages></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | ISSN: 0740-7459 |
| ispartof | IEEE software, 2002-07, Vol.19 (4), p.84-85 |
| issn | 0740-7459 1937-4194 |
| language | eng |
| recordid | cdi_crossref_primary_10_1109_MS_2002_1020292 |
| source | IEEE Electronic Library (IEL) |
| subjects | Accidents Aircraft Compliance Computer programs Design Designers Failure Failure analysis Fellows Hardware Logic design Medical robotics Safety Security Software Software design Software quality Software safety Testing |
| title | Software safety |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-19T11%3A17%3A56IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_RIE&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Software%20safety&rft.jtitle=IEEE%20software&rft.au=Tribble,%20A.C.&rft.date=2002-07-01&rft.volume=19&rft.issue=4&rft.spage=84&rft.epage=85&rft.pages=84-85&rft.issn=0740-7459&rft.eissn=1937-4194&rft.coden=IESOEG&rft_id=info:doi/10.1109/MS.2002.1020292&rft_dat=%3Cproquest_RIE%3E138713611%3C/proquest_RIE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=215828456&rft_id=info:pmid/&rft_ieee_id=1020292&rfr_iscdi=true |