Traditional software engineering is not really a branch of engineering at all as it lacks any kind of systematic measurement framework on which to base improvement, [16]. There are many dierent facets to the notion of software improvement but here, the focus will be on just one, that of the prevention of defect. In this context, Forensic Software Engineering is an amalgam of techniques specifically aimed at extracting patterns of failure associated with software controlled systems, categorising them and using the information to prevent future failures of the same kind. This is in fact a classic engineering paradigm but there is a particular need in the software community to isolate it from the unusually creative but generally measurement-free mainstream. This article introduces some of the ideas and hopes.
[1]
Les Hatton,et al.
Embedded System Paranoia: a tool for testing embedded system arithmetic
,
2005,
Inf. Softw. Technol..
[2]
Andy Roberts,et al.
How Accurate Is Scientific Software?
,
1994,
IEEE Trans. Software Eng..
[3]
Walter F. Tichy,et al.
Should Computer Scientists Experiment More?
,
1998,
Computer.
[4]
Peter van der Linden.
Expert C programming - deep C secrets
,
1994
.
[5]
Leslie Hatton.
Safer C: Developing for High-Integrity and Safety-Critical Systems
,
1995
.
[6]
Peter Van der Linden.
Expert C Programming
,
1994
.
[7]
Les Hatton.
Repetitive failure, feedback and the lost art of diagnosis
,
1999,
J. Syst. Softw..