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: | Jackson, Daniel |
---|---|
Other Authors: | Massachusetts Institute of Technology. Computer Science and Artificial Intelligence Laboratory |
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 |
Similar Items
Software development for prediction of projectiles' flight path
by: Chu, Chor Kiat
Published: (2019)
by: Chu, Chor Kiat
Published: (2019)
Similar Items
-
Separation of concerns for dependable software design
by: Jackson, Daniel, et al.
Published: (2011) -
Dependency-Directed Localization of Software Bugs
by: Kuper, Ron I.
Published: (2004) -
Property-part diagrams: A dependence notation for software systems
by: Jackson, Daniel, et al.
Published: (2011) -
End-user software customization by direct manipulation of tabular data
by: Litt, Geoffrey, et al.
Published: (2022) -
Persistence and path dependence: A primer
by: Allen, Treb, et al.
Published: (2022)