A case study of distributed, asynchronous software inspection

Stein, Michael; Riedl, John; Harner, Sören J.; Mashayekhi, Vahid

doi:10.1145/253228.253250

Cited by 29 publications

(23 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The tool supported private reviewing by allowing users to dynamically uncouple their windows from the moderator's window. To support asynchronous addition of new faults, the tool was extended to permit asynchronous voting and to provide discussion threads allowing parallel groups to discuss unrelated faults (Stein, 1997).…”

Section: 6mentioning

confidence: 99%

External Requirements of Groupware Development Tools

Graham

Grundy

1999

Engineering for Human-Computer Interaction

View full text Add to dashboard Cite

show abstract

Section: 6mentioning

confidence: 99%

External Requirements of Groupware Development Tools

Graham

Grundy

1999

Engineering for Human-Computer Interaction

View full text Add to dashboard Cite

show abstract

“…Many experiments have been conducted to study the effect of various factors on the effectiveness of inspections ( e.g. [Joh97,Por95,Por95a,Por97,Sea97,Ste97] ). Different variations of the inspection process have been proposed to make inspection more effective (e.g.…”

Section: Introductionmentioning

confidence: 99%

“…Different variations of the inspection process have been proposed to make inspection more effective (e.g. [Kni93,Mas93,Ste97,Vot93]). Experiments have also been conducted to study the use of the Web technology for inspections [Per97].…”

Section: Introductionmentioning

confidence: 99%

Overcoming the NAH syndrome for inspection deployment

Jalote¹,

Haragopal²

Proceedings of the 20th International Conference on Software Engineering

View full text Add to dashboard Cite

ABSTRACT:Despite considerable evidence to show that inspections can help reduce costs and improve quality, inspections are not widely deployed in the software industry. One of the likely reasons for this is the "not applicable here (NAH)" syndrome -developers and managers believe that in their environment, inspections will not provide the benefits seen by other organizations. One of the big challenges for deploying inspections is to overcome this syndrome. In this report, we describe two experiments that can be conducted, with little effort, in an organization to obtain data from the organization to build a case for inspections. By conducting one of these experiments, we were able to effectively overcome the NAH syndrome in our organizationmany developers and managers are now ready to try inspections in their projects. Though the purpose of the experiment was to overcome the syndrome, the data from the experiment also shows how code inspections compare with unit testing in terms of defect detection capability, and the effect of inspections on the overall cost of development.

show abstract

“…Since the HTML document format is supported by all of the most popular word processors, and web browsers can be enhanced to handle a variety of document types, virtually all written material becomes available for inspection. AISA (Stein et al 1997) pioneered reviews of more expressive document types than plain text. In addition to AISA, WWW-based inspections were demonstrated with WiP (Harjumaa & Tervonen 2000) and XATI (Hedberg 2004), for example.…”

Section: Computer-supported Inspectionsmentioning

confidence: 99%

“…Automatic defect-detection, computer-supported meetings and other types of inspection software have been a field of active research during the last ten years. ( Stein et al 1997) The WWW provides a feasible framework for arranging place-independent, asynchronous inspections.…”

Section: Support With Computer Toolsmentioning

confidence: 99%

Improving software inspection process with patterns

Harjumaa

Tervonen

Vuorio³

Fourth International Conference onQuality Software, 2004. QSIC 2004. Proceedings.

View full text Add to dashboard Cite

The quality of a software product depends largely on the quality of the process that is used to develop it. In small software companies, the development process may be informal or even ad hoc, which causes uncertainty and variation in the product quality. However, quality issues are as important in small companies as in their larger counterparts. To sustain their dynamics and competitiveness, small organizations need to concentrate on the most effective quality assurance methods.Software inspection is a proven method for improving product quality and it provides a very costeffective way for small companies to improve their development processes. This study introduces a framework for adjusting the inspection process for the organization's specific needs and evaluating its capabilities. The main focus of this work, however, is on refining and improving the inspection process. The improvement is guided by concrete instructions that are documented as process patterns. The pattern approach has already been used successfully in several other areas of software engineering. Patterns aim at capturing the best practices of software development and transferring this knowledge between people or organizations.The framework for inspection process capability originates from the literature relating to different types of peer review methods and experiments with flexible and tool-supported inspections in small companies. Furthermore, generic process improvement models are studied to find a feasible structure for the framework. As a result of the analysis, the i3 capability model is introduced. The feasibility of the model has been investigated in real-life software organizations carrying out inspections.After the capability evaluation, the inspection process can be upgraded with the aid of improvement patterns, which provide structured and easy-to-follow guidelines for implementing improvements. An initial list of patterns, describing solutions to the most common problems confronted in the establishment of inspections, is extracted from related inspection research and an industrial experiment.The contributions of this study are, first, the new view of the inspection process, based on the fundamental activities that are performed during an inspection instead of a series of stages, as it is usually presented. An activity-based process description enables tailoring of the process for organization-specific needs and its targeted improvement. Second, the study introduces a practical, lightweight method for implementing the improvement. Patterns are especially suitable in companies where resources are limited and full-scale improvement programmes cannot be initiated. Furthermore, the generic process improvement models do not provide detailed information on how improvements should be carried out, and the pattern approach represents a promising method for that. Third, the inspection process currently does not have a very significant role in generic software process improvement models; this study helps in outlining the importance ...

show abstract

A case study of distributed, asynchronous software inspection

Cited by 29 publications

References 13 publications

External Requirements of Groupware Development Tools

External Requirements of Groupware Development Tools

Overcoming the NAH syndrome for inspection deployment

Improving software inspection process with patterns

Contact Info

Product

Resources

About