|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Putting Software Terminology to the Test
May/June 2002 (vol. 19 no. 3)
pp. 88-89
| ASCII Text | x | ||
| John Steven, "Putting Software Terminology to the Test," IEEE Software, vol. 19, no. 3, pp. 88-89, May/June, 2002. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2002.1003462, author = {John Steven}, title = {Putting Software Terminology to the Test}, journal ={IEEE Software}, volume = {19}, number = {3}, issn = {0740-7459}, year = {2002}, pages = {88-89}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2002.1003462}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Putting Software Terminology to the Test IS - 3 SN - 0740-7459 SP88 EP89 EPD - 88-89 A1 - John Steven, PY - 2002 VL - 19 JA - IEEE Software ER - | |||
Project management relies on testing personnel?s expertise to ensure software quality. However, contractual and management issues also determine a project's quality. Such issues might even control testing itself.
Citation:
John Steven, "Putting Software Terminology to the Test," IEEE Software, vol. 19, no. 3, pp. 88-89, May-June 2002, doi:10.1109/MS.2002.1003462
Usage of this product signifies your acceptance of the Terms of Use.