|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Managing Requirements for Medical IT Products
January/February 2003 (vol. 20 no. 1)
pp. 26-33
| ASCII Text | x | ||
| Stewart A. Higgins, Maurice de Laat, Paul M.C. Gieles, Emilienne M. Geurts, "Managing Requirements for Medical IT Products," IEEE Software, vol. 20, no. 1, pp. 26-33, January/February, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2003.1159026, author = {Stewart A. Higgins and Maurice de Laat and Paul M.C. Gieles and Emilienne M. Geurts}, title = {Managing Requirements for Medical IT Products}, journal ={IEEE Software}, volume = {20}, number = {1}, issn = {0740-7459}, year = {2003}, pages = {26-33}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1159026}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Managing Requirements for Medical IT Products IS - 1 SN - 0740-7459 SP26 EP33 EPD - 26-33 A1 - Stewart A. Higgins, A1 - Maurice de Laat, A1 - Paul M.C. Gieles, A1 - Emilienne M. Geurts, PY - 2003 VL - 20 JA - IEEE Software ER - | |||
The authors have built a process, supported by tools, in which they capture and refine requirements as they come in. In this way, they pool requirements ready for allocation to release projects. They publish requirements valid for the next release project in a document for that release. In this process, requirements analysts work closely with requirements stakeholders.
Citation:
Stewart A. Higgins, Maurice de Laat, Paul M.C. Gieles, Emilienne M. Geurts, "Managing Requirements for Medical IT Products," IEEE Software, vol. 20, no. 1, pp. 26-33, Jan.-Feb. 2003, doi:10.1109/MS.2003.1159026
Usage of this product signifies your acceptance of the Terms of Use.