|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Monitoring Our Requirements
Jan.-Feb. 2013 (vol. 30 no. 1)
pp. 16-17
| ASCII Text | x | ||
| Neil Maiden, "Monitoring Our Requirements," IEEE Software, vol. 30, no. 1, pp. 16-17, Jan.-Feb., 2013. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2013.10, author = {Neil Maiden}, title = {Monitoring Our Requirements}, journal ={IEEE Software}, volume = {30}, number = {1}, issn = {0740-7459}, year = {2013}, pages = {16-17}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2013.10}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Monitoring Our Requirements IS - 1 SN - 0740-7459 SP16 EP17 EPD - 16-17 A1 - Neil Maiden, PY - 2013 KW - Project design KW - Project management KW - Contracts KW - Systems engineering and theory KW - satisfaction arguments KW - requirements KW - compliance VL - 30 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2013.10
Most people think of requirements as things to manipulate at the start of a project. Others, more enlightened, recognize that requirements also have a role toward the end of projects to test compliance. But few people have recognized an active role for requirements during their system's use—to monitor whether the system continues to comply with its requirements during its lifetime.
Index Terms:
Project design,Project management,Contracts,Systems engineering and theory,satisfaction arguments,requirements,compliance
Citation:
Neil Maiden, "Monitoring Our Requirements," IEEE Software, vol. 30, no. 1, pp. 16-17, Jan.-Feb. 2013, doi:10.1109/MS.2013.10
Usage of this product signifies your acceptance of the Terms of Use.