{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,2,28]],"date-time":"2026-02-28T10:23:17Z","timestamp":1772274197166,"version":"3.50.1"},"reference-count":10,"publisher":"Association for Computing Machinery (ACM)","issue":"5","license":[{"start":{"date-parts":[[2005,9,1]],"date-time":"2005-09-01T00:00:00Z","timestamp":1125532800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[2005,9]]},"abstract":"<jats:p>\n            This paper identifies the\n            <jats:italic>minimum<\/jats:italic>\n            subset required for a truly universal safety-critical software standard. This universal software standard could be used in but is not limited to the following application domains: commercial, military and space aviation; medical diagnostic and therapeutic instruments; automotive and transportation systems; industrial process control and robotics; nuclear power plants and weapons control; commercial appliances and ride electronics. The standard takes into account that safety is a system attribute but focuses on software as the critical component. Its roots are based in MoD 00-55, 56, DO-178B, ARP 4754 and 4761, Mil-Std-882 and Software Safety Handbook, IEC 61508, IEC 60880, ANSI\/ISA-S84.01, ANSI\/AAMI SW68:2001, NASA-STD-8719.13, UL 1998, EN 50128, MISRA Automotive Standard, and IEEE 1228.\n            <jats:italic>This minimum subset uses existing system and software technology and can be adapted to future applications.<\/jats:italic>\n            A universal software safety standard would benefit the entire safety-critical industry by lowering the cost and improving the quality of software by having common processes and tools. As an additional benefit, various application sectors could share data on the efficacy of each technique used in the development and verification of safety-critical software. This in turn could improve the overall safety of systems in the future.\n          <\/jats:p>","DOI":"10.1145\/1095430.1095440","type":"journal-article","created":{"date-parts":[[2005,11,7]],"date-time":"2005-11-07T19:28:32Z","timestamp":1131391712000},"page":"1-4","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":4,"title":["Universal software safety standard"],"prefix":"10.1145","volume":"30","author":[{"given":"P. V.","family":"Bhansali","sequence":"first","affiliation":[]}],"member":"320","published-online":{"date-parts":[[2005,9]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"crossref","unstructured":"Bhansali P. V. \"Universal safety standard is infeasible \" IEEE Software 1996.   Bhansali P. V. \"Universal safety standard is infeasible \" IEEE Software 1996.","DOI":"10.1109\/52.506456"},{"key":"e_1_2_1_2_1","doi-asserted-by":"crossref","unstructured":"Bhansali P. V. \"Survey of software safety standards shows diversity \" IEEE Computer January 1993.  Bhansali P. V. \"Survey of software safety standards shows diversity \" IEEE Computer January 1993.","DOI":"10.1109\/2.179168"},{"key":"e_1_2_1_3_1","doi-asserted-by":"publisher","DOI":"10.1145\/1039174.1039193"},{"key":"e_1_2_1_4_1","first-page":"Q3","author":"Bhansali P. V.","year":"2003","journal-title":"Journal of System Safety"},{"key":"e_1_2_1_5_1","doi-asserted-by":"publisher","DOI":"10.1145\/1039174.1039192"},{"key":"e_1_2_1_6_1","doi-asserted-by":"publisher","DOI":"10.1145\/882240.882252"},{"key":"e_1_2_1_7_1","doi-asserted-by":"publisher","DOI":"10.1145\/358396.358402"},{"key":"e_1_2_1_8_1","unstructured":"The Embedded C++ Website: www.caravan.net\/ec2plus  The Embedded C++ Website: www.caravan.net\/ec2plus"},{"key":"e_1_2_1_9_1","unstructured":"Myers G. J \"The Art of Software Testing \" John Wiley & Sons 1979.   Myers G. J \"The Art of Software Testing \" John Wiley & Sons 1979."},{"key":"e_1_2_1_10_1","doi-asserted-by":"publisher","DOI":"10.1145\/1039174.1039191"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1095430.1095440","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1095430.1095440","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T22:29:46Z","timestamp":1750285786000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1095430.1095440"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2005,9]]},"references-count":10,"journal-issue":{"issue":"5","published-print":{"date-parts":[[2005,9]]}},"alternative-id":["10.1145\/1095430.1095440"],"URL":"https:\/\/doi.org\/10.1145\/1095430.1095440","relation":{},"ISSN":["0163-5948"],"issn-type":[{"value":"0163-5948","type":"print"}],"subject":[],"published":{"date-parts":[[2005,9]]},"assertion":[{"value":"2005-09-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}