| dc.date.accessioned | 2008-04-28T14:11:29Z | |
| dc.date.accessioned | 2018-11-26T22:24:51Z | |
| dc.date.available | 2008-04-28T14:11:29Z | |
| dc.date.available | 2018-11-26T22:24:51Z | |
| dc.date.issued | 1985-05 | |
| dc.identifier.uri | http://hdl.handle.net/1721.1/41477 | |
| dc.identifier.uri | http://repository.aust.edu.ng/xmlui/handle/1721.1/41477 | |
| dc.description.abstract | Several approaches to the meaning and uses of errors in software development are discussed. An experiment involving a strong type-checking language, CLU, is described, and the results discussed in terms of the state of the art language for bug description. This method of bug description is found to be lacking sufficient detail to model the progress of software through its entire lifetime. A new method of bug description is proposed, which can describe bug types encountered not only in the current experiment but also in previous experiments. It is expected that this method is robust enough to be independent of the various factors of a software project that influence the realms in which bugs will occur. | en |
| dc.language.iso | en_US | en |
| dc.publisher | MIT Artificial Intelligence Laboratory | en |
| dc.title | Toward a Richer Language for Describing Software Errors | en |
| dc.type | Working Paper | en |
