|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
10 Small Steps to Better Requirements
March/April 2006 (vol. 23 no. 2)
pp. 19-21
| ASCII Text | x | ||
| Ian Alexander, "10 Small Steps to Better Requirements," IEEE Software, vol. 23, no. 2, pp. 19-21, March/April, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2006.34, author = {Ian Alexander}, title = {10 Small Steps to Better Requirements}, journal ={IEEE Software}, volume = {23}, number = {2}, issn = {0740-7459}, year = {2006}, pages = {19-21}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.34}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - 10 Small Steps to Better Requirements IS - 2 SN - 0740-7459 SP19 EP21 EPD - 19-21 A1 - Ian Alexander, PY - 2006 KW - requirements KW - projects KW - mission KW - scope KW - stakeholders KW - goals KW - conflicts KW - scenarios KW - justifications KW - assumptions KW - priorities KW - acceptance criteria VL - 23 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2006.34
Project teams can improve requirements just by making several easy steps, including defining mission and scope; identifying stakeholders, goals, and goal conflicts; describing scenarios, requirements, justifications, and assumptions; and agreeing on priorities and acceptance criteria.
Index Terms:
requirements, projects, mission, scope, stakeholders, goals, conflicts, scenarios, justifications, assumptions, priorities, acceptance criteria
Citation:
Ian Alexander, "10 Small Steps to Better Requirements," IEEE Software, vol. 23, no. 2, pp. 19-21, March-April 2006, doi:10.1109/MS.2006.34
Usage of this product signifies your acceptance of the Terms of Use.