A direct path to dependable software
What would it take to make software more dependable? Until now, most approaches have been indirect: some practices – processes, tools or techniques – are used that are believed to yield dependable software, and the argument for dependability rests on the extent to which the developers have adhered t...
| Main Author: | |
|---|---|
| Other Authors: | |
| Format: | Article |
| Language: | en_US |
| Published: |
Association for Computing Machinery
2010
|
| Online Access: | http://hdl.handle.net/1721.1/51683 https://orcid.org/0000-0003-4864-078X |
| _version_ | 1826190786008449024 |
|---|---|
| author | Jackson, Daniel |
| author2 | Massachusetts Institute of Technology. Computer Science and Artificial Intelligence Laboratory |
| author_facet | Massachusetts Institute of Technology. Computer Science and Artificial Intelligence Laboratory Jackson, Daniel |
| author_sort | Jackson, Daniel |
| collection | MIT |
| description | What would it take to make software more dependable? Until now, most approaches have been indirect: some practices – processes, tools or techniques – are used that are believed to yield dependable software, and the argument for dependability rests on the extent to which the developers have adhered to them. This article argues instead that developers should produce direct evidence that the software satisfies its dependability claims. The potential advantages of this approach are greater credibility (since the argument is not contingent on the effectiveness of the practices) and reduced cost (since development resources can be focused where they have the most impact). |
| first_indexed | 2024-09-23T08:45:38Z |
| format | Article |
| id | mit-1721.1/51683 |
| institution | Massachusetts Institute of Technology |
| language | en_US |
| last_indexed | 2024-09-23T08:45:38Z |
| publishDate | 2010 |
| publisher | Association for Computing Machinery |
| record_format | dspace |
| spelling | mit-1721.1/516832022-09-30T11:02:13Z A direct path to dependable software Jackson, Daniel Massachusetts Institute of Technology. Computer Science and Artificial Intelligence Laboratory Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science Jackson, Daniel Jackson, Daniel What would it take to make software more dependable? Until now, most approaches have been indirect: some practices – processes, tools or techniques – are used that are believed to yield dependable software, and the argument for dependability rests on the extent to which the developers have adhered to them. This article argues instead that developers should produce direct evidence that the software satisfies its dependability claims. The potential advantages of this approach are greater credibility (since the argument is not contingent on the effectiveness of the practices) and reduced cost (since development resources can be focused where they have the most impact). 2010-02-10T18:50:59Z 2010-02-10T18:50:59Z 2009 Article http://purl.org/eprint/type/SubmittedJournalArticle 0001-0782 http://hdl.handle.net/1721.1/51683 Jackson, Daniel. “A direct path to dependable software.” Commun. ACM 52.4 (2009): 78-88. https://orcid.org/0000-0003-4864-078X en_US http://dx.doi.org/10.1145/1498765.1498787 Communications of the ACM Attribution-Noncommercial-Share Alike 3.0 Unported http://creativecommons.org/licenses/by-nc-sa/3.0/ application/pdf Association for Computing Machinery Amy Stout / webpage |
| spellingShingle | Jackson, Daniel A direct path to dependable software |
| title | A direct path to dependable software |
| title_full | A direct path to dependable software |
| title_fullStr | A direct path to dependable software |
| title_full_unstemmed | A direct path to dependable software |
| title_short | A direct path to dependable software |
| title_sort | direct path to dependable software |
| url | http://hdl.handle.net/1721.1/51683 https://orcid.org/0000-0003-4864-078X |
| work_keys_str_mv | AT jacksondaniel adirectpathtodependablesoftware AT jacksondaniel directpathtodependablesoftware |