Knowledge mediation in software quality engineering

The risk of failure of the software development process remains high despite many attempts to improve the quality of software engineering. Contemporary approaches to process assurance, such as the capability maturity model have not prevented systemic failures, nor have project management methodologies provided guarantees of software quality. The paper proposes an approach to software quality assurance based on a knowledge mediated concurrent audit, which incorporates essential feedback processes. Through a tightly integrated approach to quality audit, programmers would be empowered to use any chosen methodology to advantage, supported by intelligent monitoring of the essential interactions which occur in the development process. An experimental application implementing some aspects of the proposal is described.

[1]  Robert L. Glass Practical programmer: buzzwordism and the epic $150 million software debacle , 1999, CACM.

[2]  David Bicknell,et al.  Crash: Learning From The World's Worst Computer Disasters , 1997 .

[3]  Christopher Fry Programming on an already full brain , 1997, CACM.

[4]  Leon J. Osterweil,et al.  Software Processes Are Software Too, Revisited: An Invited Talk on the Most Influential Paper of ICSE 9 , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[5]  Marc Eisenstadt,et al.  My hairiest bug war stories , 1997, CACM.

[6]  John F. Sowa,et al.  Knowledge representation: logical, philosophical, and computational foundations , 2000 .

[7]  Mark C. Paulk,et al.  The Capability Maturity Model: Guidelines for Improving the Software Process , 1994 .

[8]  Meir M. Lehman,et al.  Feedback, evolution and software technology , 1996, Proceedings 10th International Software Process Workshop.

[9]  David Boundy A taxonomy of programmers. , 1991, SOEN.

[10]  John F. Sowa,et al.  Knowledge Representation Logical, Philosophical, and Computational Foundations A Review , 2000 .

[11]  Tom Gilb,et al.  Principles of software engineering management , 1988 .

[12]  Doug Cooper,et al.  Oh! Pascal! , 1982 .

[13]  Henry Lieberman,et al.  The Debugging Scandal and What to Do About It (Introduction to the Special Section) , 1997, Commun. ACM.

[14]  John R. Anderson,et al.  Debugging: An Analysis of Bug-Location Strategies , 1987, Hum. Comput. Interact..

[15]  Meir M. Lehman,et al.  Laws of Software Evolution Revisited , 1996, EWSPT.

[16]  Lewis Gray Gray Rebuts Bach: No Cowboy Programmers! , 1998, Computer.

[17]  Donald E. Knuth,et al.  Literate Programming , 1984, Comput. J..

[18]  Chris DiBona,et al.  Open Sources: Voices from the Open Source Revolution , 1999 .

[19]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[20]  Ware Myers Why Software Developers Refuse to Improve , 1998, Computer.

[21]  Thomas W. Reps,et al.  Undecidability of context-sensitive data-dependence analysis , 2000, TOPL.

[22]  Edsger W. Dijkstra,et al.  Formal Development of Programs and Proofs , 1990 .

[23]  B. R. Williams Why do software projects fail , 1995 .