The title field is colour coded. Books are coded in red and chapters are colour coded in orange. Everything else is simply black.
My work in computer science has primarily been in the field of software failure. Much of it has involved the design and execution of experiments to attempt to determine the cause and hence to reduce the occurrence of failure in software systems.
I have also spent a great deal of time studying failures within programming languages notably those based on C,(C++, Perl, Tcl/Tk, Javascript, Java, PHP and no doubt more to come). I do not hold any great hope that languages will improve whilst they keep getting bigger. You can't fight entropy and I wish we would stop trying. I have collected language works separately under the overall title of 'Safer Subsets' at the top level.
| Author(s)
| Year
| Title
| Reference
| Category
| More details
|
Les Hatton | 2008i | Good practice in software | First draft of commissioned paper for journal | CS | good_software_practice_Jun2008.html |
Les Hatton | 2008h | A method for spam blocking | WEB | CS | spam_blocking_Dec2007.html |
Tim Hopkins , Les Hatton | 2008b | Exploring defect correlations in a major Fortran numerical library | Submitted for publication | CS | NAG01_01-08.html |
Les Hatton | 2007x8 | Forensic Software Engineering: Taking the guesswork out of testing | Accompanying short paper to talk at EuroStar 2007 | CS | LH_EuroStar07.html |
Les Hatton | 2007x5 | Software Forensics | The Wiley Software Engineering Encyclopaedia | CS | Encyc_907.html |
Les Hatton | 2007x3 | On Professionalism in IT | Safety Critical Systems Club, 17 (2), January 2008 | CS | On_Professionalism_in_IT_2007.html |
Les Hatton | 2007x1 | On the conservation of software defect | Submitted for publication | CS | statmech_0707.html |
Les Hatton | 2007k | Unsorting: an easy way of generating random permutations of an array | WEB | CS | unsorting_an_array_Apr2007.html |
Les Hatton | 2007e | Persistence correlation analysis as an aid in searching for rare but significant textual relationships | WEB | CS | chance_20070301.html |
Les Hatton | 2007d | Testing the value of checklists in code inspections | To appear in IEEE Software 2008 | CS | checklists_in_code_inspections.html |
Les Hatton | 2006s | The Chimera of Software Quality | IEEE Software, August, 2007 | CS | Chimera_Sep2006.html |
Les Hatton | 2006q | An implementation of a suffix stripping algorithm for English | WEB | CS | wordstem_2006.html |
Les Hatton | 2005z | How accurately do software engineers predict maintenance tasks ? | IEEE Computer 40 (2), p64-69, February 2007 | CS | Maint_Dec2005.html |
Les Hatton | 2005o | Predicting the total number of faults using parallel code inspections | WEB | CS | Inspect2005.html |
Les Hatton | 2005n | Estimating source lines of code from object code: Windows and Embedded Control Systems | WEB | CS | LOC2005.html |
Les Hatton | 2004o | Forensic Software Engineering: an overview | Submitted for publication | CS | fse_Dec2004.html |
Les Hatton | 2004n | A case study in complex systems evolution: consumer price obfuscation and mobile/cell phone tariff charging | Submitted for publication | CS | global_Sep05.html |
Les Hatton | 2004h | Some empirical test observations in client / server systems | IEEE Computer, 40(5), p.24-29, May 2007 | CS | GUI_blind.html |
Les Hatton | 2004g | A portable GKS interface to Thomas Boutell's GD graphics library | WEB | CS | OSGKS2004.html |
Tim Hopkins , Les Hatton | 2004b | The implementation and organisation of work arrays in numerical algorithms | WEB | CS | Malloc04.html |
Les Hatton | 2003t | Failure Aware Programming: An introduction and some predictions | Submitted for publication | CS | pred_1103.html |
Les Hatton | 2003g | Some things to watch out for when using PHP and Javascript to build websites | WEB | CS | phpuse_903.html |
Les Hatton | 2003d | A proposed grand challenge | WEB | CS | GC_403.html |
Les Hatton | 2003 | Building your own Linux PC backup server | LinuxFormat (37), February | CS | lxf37_pc.html |
Les Hatton | 2002a | "Static Analysis" in The Testing Practitioner, ed. Erik van Veenendaal | ISBN 90-72194-65-9 | CS | TP_802.html |
Les Hatton | 2002 | Software Safety | The Wiley Software Engineering Encyclopaedia | CS | Encyc_902.html |
Shari Pfleeger , Les Hatton, Chuck Howell | 2001b | Solid Software | ISBN 0-13-091298-0 | CS | SolidSoftware.html |
Les Hatton | 2001b | Some notes on software failure | WEB | CS | RS_1001.html |
Les Hatton | 2001a | The devil and the deep blue sea: moving from Windows to Linux | WEB | CS | devil_801.html |
Les Hatton | 2001 | Characterising the Diagnosis of Software Failure | IEEE Software, July/August 18(4), p. 34-39 | CS | IEEE_Soft_01a.html |
Les Hatton | 1999j | Salutary lessons in software engineering | Aviation MRO industry, September 1999 | CS | MRO_9-99.html |
Les Hatton | 1999c | Linux and the CMM | WEB | CS | WEB_1199.html |
Les Hatton | 1999b | Repetitive failure, feedback and the lost art of diagnosis | Journal of Systems and Software, (10) | CS | JSS_1099.html |
Les Hatton | 1999a | Ariane 5: a smashing success | Software Testing and Quality Engineering 1(2) | CS | STQE_Ariane99.html |
Les Hatton | 1998a | Progamming Technology, Reliability, Safety and Measurement | IEE Computing and Control Engineering, 9(1), p.23-27 | CS | IEE_CCE_298.html |
Les Hatton | 1998 | Does OO sync with the way we think ? | IEEE Software, 15(3), p.46-54 | CS | IEEE_Soft_98a.html |
Les Hatton | 1997e | What is a formal method, (and what is an informal method) ? | Proceedings of 12th annual conference on Computer Assurance, Gai | CS | formal_COMPASS97.html |
Shari Pfleeger , Les Hatton | 1997d | Do formal methods really work ? | IEEE Computer, January | CS | IEEE_197.html |
Les Hatton | 1997c | The T experiments: errors in scientific software | IEEE Computational Science and Engineering, 4(2), p.27-38 | CS | IEEE_CSE_297.html |
Les Hatton | 1997b | Re-examining the fault density - component size connection | IEEE Software, 14(2), p.89-97 | CS | IEEE_Soft_97b.html |
Les Hatton | 1997a | Are N average software versions better than 1 good version ? | IEEE Software, 14, p.71-76 | CS | IEEE_Soft_97c.html |
Les Hatton | 1997 | Software Failures, follies and fallacies | IEE Review, 43(2), p.49-54 | CS | IEE_397.html |
Les Hatton | 1996m | C and portability | WEB | CS | CPORT_96.html |
Les Hatton | 1996b | Is modularisation always a good idea ? | Information and Software Technology, 38 | CS | IST_896.html |
Les Hatton | 1996a | Software faults: the avoidable and the unavoidable: lessons from real systems | Proc. Product Assurance Workshop, ESA SP-377 | CS | ESA_696.html |
Les Hatton | 1995f | Unexpected (and sometimes unpleasant) Lessons from Data in Real Software Systems | Proceedings of 12th annual CSR workshop, Bruges, September 1995 | CS | CSR_Sept1995.html |
Les Hatton | 1995e | Static inspection - tapping the wheels of software | IEEE Software, May 1995 | CS | IEEE_Software_May1995.html |
Les Hatton | 1994a | A case history of automated improvement of software product quality | Software Quality Assurance and Measurement | CS | SQAN_594.html |
Les Hatton , Andy Roberts | 1994 | How accurate is scientific software ? | IEEE Transactions on Software Engineering, October 1994 | CS | IEEE_TSE_94.html |
Les Hatton , Tim Hopkins | 1989b | Experiences with Flint - a software metric tool for Fortran 77 | Symposium on Software Tools, Napier Polytechnic | CS | Flint_0489.html |
Les Hatton , Andy Wright, Stuart Smith, Gregg Parkes, Paddy Bennett, Robert Laws | 1988 | SKS: A large scale exercise in Fortran 77 portability | Software Practice and Experience, 18(4) | CS | SPE_488.html |
Summary: number of books 1, number of invited chapters 5, number of other articles 45