|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| H. Dieter Rombach, "Design Measurement: Some Lessons Learned," IEEE Software, vol. 7, no. 2, pp. 17-25, March/April, 1990. | |||
| BibTex | x | ||
| @article{ 10.1109/52.50770, author = {H. Dieter Rombach}, title = {Design Measurement: Some Lessons Learned}, journal ={IEEE Software}, volume = {7}, number = {2}, issn = {0740-7459}, year = {1990}, pages = {17-25}, doi = {http://doi.ieeecomputersociety.org/10.1109/52.50770}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Design Measurement: Some Lessons Learned IS - 2 SN - 0740-7459 SP17 EP25 EPD - 17-25 A1 - H. Dieter Rombach, PY - 1990 KW - measurement projects; design measurement; software engineers; software engineering VL - 7 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/52.50770
The author extracts from several measurement projects some of the important lessons he has learned about measurement in general and design measurement in particular. He synthesizes from these lessons a design-measurement framework in an attempt to communicate his personal measurement experience to other software engineers. The lessons he has learned fall into three areas: (1) how measurement must be applied in individual experiments or case studies; (2) how measurement can help continuously improve an organization's state of the practice; and (3) why measurement requires automated support.
Index Terms:
measurement projects; design measurement; software engineers; software engineering
Citation:
H. Dieter Rombach, "Design Measurement: Some Lessons Learned," IEEE Software, vol. 7, no. 2, pp. 17-25, March-April 1990, doi:10.1109/52.50770
Usage of this product signifies your acceptance of the Terms of Use.

