|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Jason Remillard, "Source Code Review Systems," IEEE Software, vol. 22, no. 1, pp. 74-77, January/February, 2005. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2005.20, author = {Jason Remillard}, title = {Source Code Review Systems}, journal ={IEEE Software}, volume = {22}, number = {1}, issn = {0740-7459}, year = {2005}, pages = {74-77}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2005.20}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Source Code Review Systems IS - 1 SN - 0740-7459 SP74 EP77 EPD - 74-77 A1 - Jason Remillard, PY - 2005 KW - inspection KW - inspection tool KW - inspections process KW - open source tool VL - 22 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2005.20
When the software engineering group at Soluris decided to relaunch its inspection process, it needed to select a software tool to automate its inspections process and thus eliminate the paper forms they?d otherwise need. This article compares two open source tools-Bugzilla and Codestriker-and three commercial tools-the CodeReview add-on for Visual Studio .Net, CodeReviewer, and ReviewPro.
Index Terms:
inspection, inspection tool, inspections process, open source tool
Citation:
Jason Remillard, "Source Code Review Systems," IEEE Software, vol. 22, no. 1, pp. 74-77, Jan.-Feb. 2005, doi:10.1109/MS.2005.20
Usage of this product signifies your acceptance of the Terms of Use.

