Remember Me
Or use your Academic/Social account:


Or use your Academic/Social account:


You have just completed your registration at OpenAire.

Before you can login to the site, you will need to activate your account. An e-mail will be sent to you with the proper instructions.


Please note that this site is currently undergoing Beta testing.
Any new content you create is not guaranteed to be present to the final version of the site upon release.

Thank you for your patience,
OpenAire Dev Team.

Close This Message


Verify Password:
Verify E-mail:
*All Fields Are Required.
Please Verify You Are Human:
fbtwitterlinkedinvimeoflicker grey 14rssslideshare1
Jeary, Sherry; Phalp, Keith T.; Milsom, Frank; Hughes, Lisa; Webster, S.; Holroyd, J.
Languages: English
Types: Unknown
Subjects: csi
In this paper, we explore why Fagan Inspections have become obsolete in the software industry, given the body of evidence which supports their use to improve the quality of software artefacts and the software development process. \ud Since the late 1970’s, much has been written about how Fagan Inspections improve the quality of both processes and outputs of the software development process. The literature indicates that the Fagan Inspection technique can improve quality of software (or other software development artefacts) by a reduction in defects of 60 – 90%. However, recent literature suggests that inspection techniques in general and Fagan Inspections in particular, are no longer used. A study in 1998 found that respondents used inspections either irregularly or not at all. Teams often review artefacts informally, but believe that they are performing an inspection or formal review. The lack of rigour in the review process results in reduced benefits and more defects in the artefacts.\ud To explore this situation, we conducted a case study with a local enterprise and we report on the early findings. These suggest that the introduction of Fagan Inspections may have a number of benefits before they have even been introduced fully, including recognition of flaws in the current development process, development of technical knowledge relating to the software process domain, and improved team relations and a ‘quality’ culture. In addition, the personnel using Fagan Inspection gain experience in the production of ‘quality’ artefacts. \ud
  • The results below are discovered through our pilot algorithms. Let us know how we are doing!

    • 1. Fagan, M.E., Design and code inspections to reduce errors in program development. IBM Systems Journal 15 (1976) 2. Gilb, T., Graham, D., Software Inspection. Addison Wesley, Harlow, England (1993) 3. Fagan, M.E., A History of Software Inspections. In: Broy, M., Denert, E. (eds.): sd&m 2001. Springer (2002) 4. Fagan, M.E., Advances in Software Inspections. IEEE Transactions on Software Engineering 12 (1986) 5. Barnard, E., One Person Getting Started. In: Gilb, T., Graham, D., Finzi, S. (eds.): Software Inspections.
    • Proceedings of INCOSE Conference, Rochester NY, USA (2005) 20. Yin, R.K., Case Study Research: Design and Methods, Vol. 5. Sage, Los Angeles (2009) 21. Bush, M., Improving Software Quality: The Use of Formal Inspections at the Jet Propulsion Laboratory.
    • Software Engineering, Nice, France (1990) 22. RSG, (2011). Six Simple Rules for Writing An Effective Business Requirement, [online]. Available from: http://www.requirementssolutions.com/WhitePapers/RulesForEffectiveRequirements.pdf [Accessed: 17 January 2011 23. Selby, R.W., Software Engineering: Barry W. Boehm's Lifetime Contributions to Software Development, Management, and Research. Wiley-IEEE Computer Society Press (2007)
  • No related research data.
  • No similar publications.

Share - Bookmark

Cite this article