IEEE Xplore - Login

Cart | Sitemap | Help

Login


	BROWSE	SEARCH	IEEE XPLORE GUIDE	SUPPORT


Article Information

Reducing inspection interval in large-scale software development Perry, D.E.; Porter, A.; Wade, M.W.; Votta, L.G.; Perpich, J. Software Engineering, IEEE Transactions on Volume 28, Issue 7, Jul 2002 Page(s): 695 - 705 Digital Object Identifier 10.1109/TSE.2002.1019483 Summary: We have found that, when software is developed by multiple, geographically separated teams, the cost-benefit trade-offs of software inspection change. In particular, this situation can significantly lengthen the inspection interval (calendar time needed to complete an inspection). Our research goal was to find a way to reduce the inspection interval without reducing inspection effectiveness. We believed that Internet technology offered some potential solutions, but we were not sure which technology to use nor what effects it would have on effectiveness. To conduct this research, we drew on the results of several empirical studies we had previously performed. These results clarified the role that meetings and individuals play in inspection effectiveness and interval. We conducted further studies showing that manual inspections without meetings were just as effective as manual inspections with them. On the basis of these and other findings and our understanding of Internet technology, we built an economical and effective tool that reduced the interval without reducing effectiveness. This tool, Hypercode, supports meetingless software inspections with geographically distributed reviewers. HyperCode is a platform-independent tool, developed on top of an Internet browser, that integrates seamlessly into the current development process. By seamless, we mean the tool produces a paper flow that is almost identical to the current inspection process. HyperCode's acceptance by its user community has been excellent. Moreover, we estimate that using HyperCode has reduced the inspection interval by 20 to 25 percent. We believe that, had we focused solely on technology (without considering the information our studies had uncovered), we would have created a more complex, but not necessarily more effective tool. We probably would have supported group meetings, restricted each participant's access to review comments, and supported a wider variety of inspection methods. In other words, the principles derived from our empirical studies dramatically and successfully directed our search for a technological solution. » View citation and abstract



IEEE Members

Log in by entering your IEEE Web Account Username and Password. IEEE Communications Society members: If you subscribe to the IEEE Electronic Periodicals Package or IEEE Electronic Periodicals Package Plus, you must access your subscription at www.comsoc.org.



Users at Subscribing Institutions

Check with your librarian, information professional, or system manager to determine if you need to log in. Please complete the online Technical Support Form if you need assistance.



Already Purchased This Article?

Select the Purchase History link to access the document. You will have 5 Days after purchase to access the Full Text PDF. Please complete the online Technical Support Form if you need assistance.



Guests

• Search and access Abstract records free of charge • Register for table of contents alerts • Purchase Full Text PDF documents » Learn more about subscription options or how to become an IEEE Member.

You are not logged in.

Username

Password

» Forgot your password?

Please remember to log out when you have finished your session.

You must log in to access:
• Advanced or Author Search
• CrossRef Search
• AbstractPlus Records
• Full Text PDF
• Full Text HTML

Access this document

» Buy this document now

» Learn more about

subscription options

» Learn more about

purchasing articles

and standards

Learn more about IEEE Subscriptions

Help Contact Us Privacy & Security IEEE.org