Search For:

Displaying 1-22 out of 22 total
The Generational Impact of Software
Found in: IEEE Software
By Anne-Francoise Rutkowski,Carol Saunders,Les Hatton
Issue Date:May 2013
pp. 87-89
Eighteen Impact columns to date have talked only about growing software. Les Hatton, Anne Rutkowski, and Carol Saunders indicate that there are also limits to growth in our field.
 
Point/Counterpoint
Found in: IEEE Software
By Les Hatton, Michiel van Genuchten
Issue Date:May 2009
pp. 66-69
Les Hatton (
 
Metrics with Impact
Found in: IEEE Software
By Michiel van Genuchten,Les Hatton
Issue Date:July 2013
pp. 99-101
Over the past few years, metrics proposed in Impact columns such as Compound Average Growth Rate (CAGR) and software mileage have been applied in real life in organizations around the world. This issue's installment provides some examples and discusses the...
 
Compound Annual Growth Rate for Software
Found in: IEEE Software
By Michiel van Genuchten,Les Hatton
Issue Date:July 2012
pp. 19-21
Six Impact columns published over the last three years and a couple of precisely measured products provide the opportunity to calculate a compound annual growth rate.
 
Early Design Decisions
Found in: IEEE Software
By Les Hatton,Michiel van Genuchten
Issue Date:January 2012
pp. 87-89
An online survey with experienced managers and architects, all authors of previous Impact columns, compliments the special issue on studying professional software design. The practitioner's view on the topic discusses who should be involved in early design...
 
Software Mileage
Found in: IEEE Software
By Michiel van Genuchten,Les Hatton
Issue Date:September 2011
pp. 24-26
Looking back on the first seven Impact columns for IEEE Software, the editors propose a new metric called software mileage, defined as the number of new customers per year per line of code.
 
Software: What's In It and What's It In?
Found in: IEEE Software
By Michiel van Genuchten, Les Hatton
Issue Date:January 2010
pp. 14-16
IEEE Software's new series of Impact columns intends to get a better quantitative insight into the impact of software on various businesses. This introduction describes the reasoning behind the columns. All contributors will be asked to quantify the size (...
 
Invited Talk: The Role of Empiricism in Improving the Reliability of Future Software
Found in: Practice And Research Techniques, Testing: Academic & Industrial Conference on
By Les Hatton
Issue Date:August 2008
pp. x
No summary available.
   
Static Inspection: Tapping the Wheels of Software
Found in: IEEE Software
By Les Hatton
Issue Date:May 1995
pp. 85-87
Les Hatton, director of research and engineering for Programming Research Ltd.in the UK and a member of the British Standards Institute's C++ committee, has spent many years looking at how languages and their compilers can support software quality. Here, t...
 
Conservation of Information: Software’sHidden Clockwork?
Found in: IEEE Transactions on Software Engineering
By Les Hatton
Issue Date:May 2014
pp. 450-460
In this paper it is proposed that the Conservation of Hartley-Shannon Information (hereafter contracted to H-S Information) plays the same role in discrete systems as the Conservation of Energy does in physical systems. In particular, using a variational a...
 
Quantifying Software's Impact
Found in: Computer
By Michiel van Genuchten,Les Hatton
Issue Date:October 2013
pp. 66-72
Software's impact on various industries is the topic of 15 columns published in IEEE Software since 2010. This article describes how to quantify software's impact using metrics such as compound average growth rate and software mileage.
 
Power-Law Distributions of Component Size in General Software Systems
Found in: IEEE Transactions on Software Engineering
By Les Hatton
Issue Date:July 2009
pp. 566-572
This paper begins by modeling general software systems using concepts from statistical mechanics which provide a framework for linking microscopic and macroscopic features of any complex system. This analysis provides a way of linking two features of parti...
 
Testing the Value of Checklists in Code Inspections
Found in: IEEE Software
By Les Hatton
Issue Date:July 2008
pp. 82-88
Checklists are an important part of code and design inspections. Ideally, they aim to increase the number of faults found per inspection hour by highlighting known areas of previous failure. In practice, although some researchers have quantified checklists...
 
The Chimera of Software Quality
Found in: Computer
By Les Hatton
Issue Date:August 2007
pp. 104, 102-103
Most software failures and disasters could have been avoided using techniques we already know.
 
Empirical Test Observations in Client-Server Systems
Found in: Computer
By Les Hatton
Issue Date:May 2007
pp. 24-29
Formal statistical analysis of defect databases for two commercial client-server products tests the hypothesis that defects in the graphical client mask more important underlying defects in the computational server. The analysis also quantifies the benefit...
 
How Accurately Do Engineers Predict Software Maintenance Tasks?
Found in: Computer
By Les Hatton
Issue Date:February 2007
pp. 64-69
Previous research shows considerable overlap among perfective, corrective, and adaptive maintenance tasks in software development projects. A case study involving two recent products provides further empirical evidence of this distribution and sheds light ...
 
Exploring the Role of Diagnosis in Software Engineering
Found in: IEEE Software
By Les Hatton
Issue Date:July 2001
pp. 34-39
Software engineers, encouraged to believe that their capability to remove defects matches their ambition to do so, rarely contemplate the possibility of software failure during design. Changing this attitude-and improving diagnostics- could reverse softwar...
 
Does OO Sync with How We Think?
Found in: IEEE Software
By Les Hatton
Issue Date:May 1998
pp. 46-54
Given that corrective-maintenance costs already dominate the software life cycle and look set to increase significantly, reliability in the form of reducing such costs should be the most important software improvement goal. Yet the results are not promisin...
 
N-Version Design Versus One Good Version
Found in: IEEE Software
By Les Hatton
Issue Date:November 1997
pp. 71-76
Evidence indicates that n-version development techniques are more reliable than producing one
 
The T Experiments: Errors In Scientific Software
Found in: Computing in Science and Engineering
By Les Hatton
Issue Date:April 1997
pp. 27-38
<p>Presented (in preliminary form) at the IEEE Computer Society Workshop on Computational Science & Engineering, Oct. 1996, Purdue University, by John Rice. </p> <p>Extensive tests showed that many software codes widely used in scienc...
 
Reexamining the Fault Density-Component Size Connection
Found in: IEEE Software
By Les Hatton
Issue Date:March 1997
pp. 89-97
Conventional wisdom, that smaller components contain proportionately fewer faults, may be wrong. This author found that medium-sized components were proportionately more reliable than large or small ones. Moreover, he says, there may be limits on the fault...
 
Investigating the Influence of Formal Methods
Found in: Computer
By Shari Lawrence Pfleeger, Les Hatton
Issue Date:February 1997
pp. 33-43
<p>Formal methods promise much, but can they deliver? In this project, results are inconclusive, but careful data gathering and analysis helped establish influences on product quality. </p> <p>Practitioners and researchers continue to see...
 
 1