J. Drake, V. Mashayekhi, J. Riedl, and W. Tsai. A Distributed Collaborative Software Inspection Tool: Design, Prototype, and Early Trial. Technical report, TR-91-30, University of Minnesota, August 1991.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....of the defects by type, class and severity is also generated. The scribe can also prepare a report detailing the total time spent in preparation and in meeting, the inspectors present and other such process information. 3. 2 Collaborative Software Inspection Collaborative Software Inspection (CSI) [15] is designed to support inspection of all software development products. The tool is described as applied to the Humphrey model of inspection [8] In this variation, each inspector creates a list of faults during individual inspection, which are then given to the author of the document before the ....

V. Mashayekhi, J. M. Drake, W. T. Tsai and J. Reidl, "Distributed, Collaborative Software Inspection," IEEE Software, Vol. 10, No. 5, pp. 66-75, September 1993. Department of Computer Science RR-95-187 [EFoCS-13-95]

....models of coupling can be used to support flexible coupling in existing collaborative applications. For instance, it can be implemented in (a) the ICICLE code inspector [4] to support both synchronous and asynchronous software inspection in the manner supported by the Suite code inspector [15], b) the GROVE outline editor [16] to support transmission of changes on completion of a word, a sentence, a paragraph, or a section, and (c) the PREP document editor [24] to allow users to make both private and public annotations. Not all aspects of our approach are applicable to an existing ....

Janet Drake, Vahid Mashayekhi, John Riedl, and Wei-Tek Tsai, "A Distributed Collaborative Software Inspection Tool: Design, Prototype, and Early Trial," Proceedings of the 30th Aerospace Sciences Conference, January 92.

....be called upon to make a decision anyway. Giving the moderator this power earlier on achieves the same goal and removes the extra overhead incurred by the meeting. 4. 2 Mashayekhi et al. Another strand of work dealing with asynchronous software inspection is that pursued by Mashayekhi et al. [21, 22, 23]. Unlike the previously reported work, this work makes use of an existing inspection model, suggested by Humphrey [9] This model differs from those described previously, in that the purpose of the meeting is to discuss a list of faults generated by the author from individual fault lists submitted ....

V. Mashayekhi, J. Drake, W. T. Tsai, and J. Riedl. Distributed collaborative software inspection. IEEE Software, 10(5):66--75, September 1993.

.... multi user query based interface to a database management system [39] a multi user debugger; a multi user RCS tool , which allows users to view and edit the state of a version control system, a multi user C Tool , which allows users to browse and test C programs; and a multi user code inspector [18], which allows users to annotate documents. 12 Our experience with building some initial versions of the earlier multi user applications helped us identify issues in the design of multi user Suite and choose approaches for addressing them. We motivated our design using a specific example of a ....

....over the last one year and so far used only in demonstrations. The code inspector has been used in initial pilot studies by researchers at the University of Minnesota. Their initial experience with it suggests some advantages of collaborative code inspection over traditional manual inspection [18]. We intend to integrate the software engineering tools mentioned above into a FLexible Environment for Collaborative Software Engineering (FLECSE) which we intend to use for promoting the distributed, collaborative development of Suite tools between researchers at Purdue and the University of ....

Janet Drake, Vahid Mashayekhi, John Riedl, and Wei-Tek Tsai, "A Distributed Collaborative Software Inspection Tool: Design, Prototype, and Early Trial," Proceedings of the 30th Aerospace Sciences Conference, January 92. P. Dewan and R. Choudhary Implementing Multi-User Interfaces d40

....in Suite. Adding digital audio to Suite enhances distributed collaboration by helping participants work together more naturally. Since SuiteSound is integrated with Suite, applications can use sound in the way that is most natural for them. For instance, Collaborative Software Inspection (CSI) DMRT91] is a tool that supports distributed software inspection, using Suite for the software modules being inspected, and SuiteSound for audio ( section 4.3. CSI offers audio teleconferencing for participants to discuss the documents during the distributed inspection meeting, and audio annotations ....

....inspection, relaxing the requirement that all the participants be in the same room, providing automated support, and adding structure to the process. CSI allows geographically distributed participants to collaborate in the inspection and provides automated support for all inspection activities [DMRT91] Participants communicate through CSI dialog managers, Teleconf, and voice annotation. The asynchronous activities of software inspection include the distribution of target material and the creation of reviewer s fault lists. The target material is on line and accessible by reviewers who can use ....

J. Drake, V. Mashayekhi, J. Riedl, and W. Tsai. A Distributed Collaborative Software Inspection Tool: Design, Prototype, and Early Trial. Technical report, TR-91-30, University of Minnesota, August 1991.

....sound annotation. These include: Play, Loop (replay) Sort, and Length. The CSI tool (see section 3.3) relies heavily on the Annotator. 3. 3 Collaborative Software Inspection The Collaborative Software Inspection tool (CSI) supports software inspection in a distributed, collaborative environment [18]. Software inspection activities can be thought of as asynchronous and synchronous. Preliminary results suggest, that given the proper audio support, distributed collaborative software inspection can be as effective as traditional software inspection. The asynchronous activities are those that ....

Janet Drake, Vahid Mashayekhi, John Riedl, and Wei-Tek Tsai. A distributed collaborative software inspection tool: Design, prototype, and early trial. IEEE Software, 1993. To appear.

....in Suite. Adding digital audio to Suite enhances distributed collaboration by helping participants work together more naturally. Since SuiteSound is integrated with Suite, applications can use sound in the way that is most natural for them. For instance, Collaborative Software Inspection (CSI) DMRT91] is a tool that supports distributed software inspections, using Suite for the software objects being inspected, and SuiteSound for audio ( section 4.3. CSI offers audio teleconferencing for participants to discuss the the documents during distributed inspection meeting, and audio annotations ....

....inspection, relaxing the requirement that all the participants be in the same room, providing automated support, and adding structure to the process. CSI allows geographically distributed participants to collaborate in the inspection and provides automated support for all inspection activities [DMRT91] Participants communicate through CSI dialog managers, teleconf, and voice annotation. Figure 5 depicts the screen of a participant in software inspection using the CSI and Teleconf tools. The asynchronous activities of software inspection include the distribution Figure 5: The CSI and ....

J. Drake, V. Mashayekhi, J. Riedl, and W. Tsai. A Distributed Collaborative Software Inspection Tool: Design, Prototype, and Early Trial. Technical report, TR-91-30, University of Minnesota, August 1991.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC