|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Requirements and the Business Case
September/October 2004 (vol. 21 no. 5)
pp. 93-95
| ASCII Text | x | ||
| Suzanne Robertson, "Requirements and the Business Case," IEEE Software, vol. 21, no. 5, pp. 93-95, September/October, 2004. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2004.1331310, author = {Suzanne Robertson}, title = {Requirements and the Business Case}, journal ={IEEE Software}, volume = {21}, number = {5}, issn = {0740-7459}, year = {2004}, pages = {93-95}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2004.1331310}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Requirements and the Business Case IS - 5 SN - 0740-7459 SP93 EP95 EPD - 93-95 A1 - Suzanne Robertson, PY - 2004 KW - business case KW - software engineering VL - 21 JA - IEEE Software ER - | |||
We hear a lot about the necessity of finding the right requirements. But how do you know which requirements are the right ones? You must have a well-understood reason for doing a project along with quantified expectations of its costs and benefits. We often refer to this collection of knowledge as the business case.
Index Terms:
business case, software engineering
Citation:
Suzanne Robertson, "Requirements and the Business Case," IEEE Software, vol. 21, no. 5, pp. 93-95, Sept.-Oct. 2004, doi:10.1109/MS.2004.1331310
Usage of this product signifies your acceptance of the Terms of Use.