Abstract
The use of software products in today's world has increased dramatically making quality an important aspect of software development. There is a continuous need to develop processes to control and increase software quality. Software code inspection is one way to pursue this goal. This paper presents a collaborative code inspection process that was designed during an action research study using Collaboration Engineering principles and techniques, our inspection process was implemented as a sequence of thinkLets, chunks of facilitation skill, that were subsequently field tested in a traditional paper-based and Group Support System (GSS)-based environment. Four inspections were performed on four different pieces of software code in two different organizations. Results show that regardless of the implementation, the process was found to be successful in uncovering many major, minor, and false-positive defects in inspected pieces of code. Overall observations and feedback suggest that the collaborative inspection process was considered to be productive and satisfactory. GSS inspections were more effective, especially in terms of major defects. GSS inspections were also found to be more efficient. Finally, the GSS inspections outperformed the paper inspections from a practical perspective: logging and managing defects in a GSS was far superior.
Original language | English (US) |
---|---|
Pages (from-to) | 205-228 |
Number of pages | 24 |
Journal | International Journal of Cooperative Information Systems |
Volume | 15 |
Issue number | 2 |
DOIs | |
State | Published - Jun 2006 |
Keywords
- Action research
- Code inspection
- Collaboration
- Collaboration Engineering
- Fagan inspection
- Group Support Systems
- Thinklets
ASJC Scopus subject areas
- Information Systems
- Computer Science Applications