Scrutiny: A Collaborative Inspection and Review System

  title={Scrutiny: A Collaborative Inspection and Review System},
  author={John Gintell and J. E. Arnold and Michael Houde and Jacek Kruszelnicki and Roland McKenney and G{\'e}rard Memmi},
This paper describes a Bull US Applied Research Laboratory project to build a collaborative inspection and review system called Scrutiny using ConversationBuilder from the University of Illinois at Urbana-Champaign. The project has several distinct aspects: technology oriented research, prototype building, experimentation, and tool deployment/technology transfer. Described are the design of the current operational version of Scrutiny for inspection-only, the evolutionary design of Scrutiny to… 

Integrating a Distributed Inspection Tool Within an Artefact Management System

The inspection tool has been integrated within an artefact management system, thus allowing the planning, scheduling, and enactment of the inspection within the development process and integrating the review phase within the overall artefact lifecycle.

Experiences with CSRS: An Instrumented Software Review Environment

Initial experiments using CSRS, an instrumented, computer-supported cooperative work environment for software review that reduces the manual, labor-intensive nature of review activities and supports quantitative study of the process and products of review, indicate that CSRS increases both the breadth and depth of information captured per person-hour of review time.

Lessons learned with ACME an environment integration experiment

The components and conceptual design of ACME and the effect that ACME has on the operation of Scrutiny are described and the lessons learned during this project are described.

Tool Support for Geographically Dispersed Inspection Teams Research Section

A web-based tool, called the Internet-Based Inspection System (IBIS), that aims to support geographically dispersed inspection teams and adopts a reengineered inspection process to minimize synchronous activities and coordination problems.

Tool support for geographically dispersed inspection teams

A web-based tool, called the Internet-Based Inspection System (IBIS), that aims to support geographically dispersed inspection teams and adopts a reengineered inspection process to minimize synchronous activities and coordination problems.

Assessing the Effectiveness of a Distributed Method for Code Inspection: A Controlled Experiment

A distributed inspection method that tries to minimise the synchronous collaboration among team members to identify defects in software artefacts by resolving conflicts using an asynchronous discussion before performing a traditional synchronous meeting.

Exploring Group Size on Software Inspection Performance: Report From 2 Controlled Experiments

The process of software inspection is described and the issues in the process are discussed.

A Comparison of Computer Support Systems for Software Inspection

The authors have been working to develop a second generation tool which tackles some fundamental weaknesses still exist in software inspection, and a brief description of this tool is also included in the paper.

The Evolution of Code Review Research: A Systematic Mapping Study

From a collection of 7,266 papers from the top software engineering venues, visual maps provide evidence that CR research does cover more than quality assurance, and will continue to evolve with the availability of datasets and emerging technologies within the CR domain.

An instrumented approach to improving software quality through formal technical review

  • Philip M. Johnson
  • Computer Science
    Proceedings of 16th International Conference on Software Engineering
  • 1994
CSRS is an instrumented, computer-supported cooperative work environment for formal technical review that addresses problems in the practice of FTR by providing computer support for both the process and products of F TR.



Improving Software Quality through Computer Supported Collaborative Review

CSRS, a computer-supported cooperative work environment for software review that improves the efficiency of review activities and supports empirical investigation of the appropriate parameters for review is introduced.

Phased inspections and their implementation

Software reviews are not a new idea, but in the 1950's and 1960's, large software projects often included some sort of software reviews, and in the 1970's these review mechanisms began appearing in publications.

ICICLE: groupware for code inspection

The implementation of ICICLE and GroupWare issues encountered during testing are reported, directed towards an audience interested in the implementation of GroupWare as well as those concerned with usability of software systems for computer-supported cooperative work (CSCW).

N-Fold inspection: a requirements analysis technique

A comparison of N-fold inspection with other development techniques reveals that N- fold inspection is a cost-effective method for finding faults in the URD and may be a valid technique in the development of mission-critical software systems.

Intelligent assistance for software development and maintenance

An environment is described, called Professor Marvel, that provides early error checking and answers questions about the program under development. The environment has a certain understanding of the

Managing the software process

  • W. Humphrey
  • Computer Science
    The SEI series in software engineering
  • 1989
This work describes the development of a Software Maturity Framework and the Principles of Software Process Change, and describes the management of this framework.

Flexible, active support for collaborative work with ConversationBuilder

The ConversationBuilder is reviewed, a support tool intended to provide flexible, active support for (collaborative) work activities, and both the kinds of support it provides and its architecture are discussed, and its use is illustrated through an example.

Experience with inspection in ultralarge-scale development

The use of code inspection to detect errors in ultralarge software projects is discussed. In particular, quantitative results based on a 1988 study of inspection of 2.5 million lines of high-level

Interacting with the field environment

  • S. Reiss
  • Computer Science
    Softw. Pract. Exp.
  • 1990
The key concepts behind FIELD are an integration mechanism based on a simple, central message server, an annotation editor for integrating access to the source file with the other tools, and the use of a high‐level user interface toolset.

Understanding computers and cognition