|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Edward F. Weller, "Lessons from Three Years of Inspection Data," IEEE Software, vol. 10, no. 5, pp. 38-45, September/October, 1993. | |||
| BibTex | x | ||
| @article{ 10.1109/52.232397, author = {Edward F. Weller}, title = {Lessons from Three Years of Inspection Data}, journal ={IEEE Software}, volume = {10}, number = {5}, issn = {0740-7459}, year = {1993}, pages = {38-45}, doi = {http://doi.ieeecomputersociety.org/10.1109/52.232397}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Lessons from Three Years of Inspection Data IS - 5 SN - 0740-7459 SP38 EP45 EPD - 38-45 A1 - Edward F. Weller, PY - 1993 KW - software development; inspection program; standard development process; operating system; development staff; operating systems (computers); project management; software engineering VL - 10 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/52.232397
The implementation of an inspection program as part of a standard development process for an operating system at Bull HN Information Systems Major Systems Division is reviewed. The methods used to collect and analyze the data and provide feedback to the development staff are described. The data are examined from the point of view of the entire organization and as they apply in individual case studies of particular project types.
Index Terms:
software development; inspection program; standard development process; operating system; development staff; operating systems (computers); project management; software engineering
Citation:
Edward F. Weller, "Lessons from Three Years of Inspection Data," IEEE Software, vol. 10, no. 5, pp. 38-45, Sept.-Oct. 1993, doi:10.1109/52.232397
Usage of this product signifies your acceptance of the Terms of Use.

