{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:27:38Z","timestamp":1750307258288,"version":"3.41.0"},"reference-count":6,"publisher":"Association for Computing Machinery (ACM)","issue":"8","license":[{"start":{"date-parts":[[2011,8,1]],"date-time":"2011-08-01T00:00:00Z","timestamp":1312156800000},"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":["Queue"],"published-print":{"date-parts":[[2011,8]]},"abstract":"<jats:p>Avionics software has become a keystone in today\u2019s aircraft design. Advances in avionics systems have reduced aircraft weight thereby reducing fuel consumption, enabled precision navigation, improved engine performance, and provided a host of other benefits. These advances have turned modern aircraft into flying data centers with computers controlling or monitoring many of the critical systems onboard. The software that runs these aircraft systems must be as safe as we can make it.<\/jats:p>","DOI":"10.1145\/2016036.2024356","type":"journal-article","created":{"date-parts":[[2012,10,16]],"date-time":"2012-10-16T12:50:57Z","timestamp":1350391857000},"page":"50-59","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":2,"title":["Verification of Safety-critical Software"],"prefix":"10.1145","volume":"9","author":[{"given":"B. Scott","family":"Andersen","sequence":"first","affiliation":[{"name":"Verocel, Inc."}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"George","family":"Romanski","sequence":"additional","affiliation":[{"name":"Verocel, Inc."}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2011,8,29]]},"reference":[{"key":"e_1_2_1_1_1","first-page":"1309","article-title":"System Design and Analysis","volume":"25","author":"Federal Aviation Administration","year":"1998","journal-title":"Advisory Circular AC"},{"key":"e_1_2_1_2_1","unstructured":"Federal Aviation Administration. 2011. Reverse Engineering Software and Digital Systems April 2011{Draft Report}. To be published by the FAA William J. Hughes Technical Center.  Federal Aviation Administration. 2011. Reverse Engineering Software and Digital Systems April 2011{Draft Report}. To be published by the FAA William J. Hughes Technical Center."},{"key":"e_1_2_1_3_1","unstructured":"Humphrey W. S. 1990. Managing the Software Process. SEI Series in Software Engineering. Reading MA: Addison-Wesley Publishing Company.   Humphrey W. S. 1990. Managing the Software Process. SEI Series in Software Engineering. Reading MA: Addison-Wesley Publishing Company."},{"key":"e_1_2_1_4_1","doi-asserted-by":"publisher","DOI":"10.1145\/202709"},{"key":"e_1_2_1_5_1","unstructured":"Rakitin S. R. 2001. Software Verification and Validation for Practitioners and Managers secondedition. Norwood MA: Artech House.   Rakitin S. R. 2001. Software Verification and Validation for Practitioners and Managers secondedition. Norwood MA: Artech House."},{"key":"e_1_2_1_6_1","unstructured":"RTCA. 1992. Software Considerations in Airborne Systems and Equipment Certification (DO-178B).  RTCA. 1992. Software Considerations in Airborne Systems and Equipment Certification (DO-178B)."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2016036.2024356","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/2016036.2024356","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T10:52:31Z","timestamp":1750243951000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2016036.2024356"}},"subtitle":["Avionics software safety certification is achieved through objective-based standards."],"short-title":[],"issued":{"date-parts":[[2011,8]]},"references-count":6,"journal-issue":{"issue":"8","published-print":{"date-parts":[[2011,8]]}},"alternative-id":["10.1145\/2016036.2024356"],"URL":"https:\/\/doi.org\/10.1145\/2016036.2024356","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2011,8]]},"assertion":[{"value":"2011-08-29","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}