|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Exactly How Are Requirements Written?
January/February 2012 (vol. 29 no. 1)
pp. 26-27
| ASCII Text | x | ||
| Neil Maiden, "Exactly How Are Requirements Written?," IEEE Software, vol. 29, no. 1, pp. 26-27, January/February, 2012. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2012.6, author = {Neil Maiden}, title = {Exactly How Are Requirements Written?}, journal ={IEEE Software}, volume = {29}, number = {1}, issn = {0740-7459}, year = {2012}, pages = {26-27}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2012.6}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Exactly How Are Requirements Written? IS - 1 SN - 0740-7459 SP26 EP27 EPD - 26-27 A1 - Neil Maiden, PY - 2012 KW - requirements KW - software engineering KW - cognitive process KW - analysis KW - analyst VL - 29 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2012.6
Few studies of actual requirements practices exist compared to the number of studies on how people program. Thus, we know relatively little about how people actually do requirements work. By considering a simple user story, we can begin to inform our understanding of the cognitive processes that good requirements work requires.
1. J. Rooksby and N. Ikeya, "Collaboration in Formative Design: Working Together at a Whiteboard," IEEE Software, vol. 29, no. 1, 2012, pp. 56–60.
2. A. Dilmaghani and J. Dibble, "Strategies for Early-Stage Collaborative Design," IEEE Software, vol. 29, no. 1, 2012, pp. 39–45.
3. D. Damian, S. Marczak, and I. Kwan, "Collaboration Patterns and the Impact of Distance on Awareness in Requirements-Centred Social Networks," Proc. IEEE Requirements Eng. Conf. (RE 07), IEEE CS Press, 2007, pp. 59–68.
4. L. Cao and B. Ramesh, "Agile Requirements Engineering Practices: An Empirical Study," IEEE Software, vol. 25, no. 1, 2008, pp. 60–67.
Index Terms:
requirements, software engineering, cognitive process, analysis, analyst
Citation:
Neil Maiden, "Exactly How Are Requirements Written?," IEEE Software, vol. 29, no. 1, pp. 26-27, Jan.-Feb. 2012, doi:10.1109/MS.2012.6
Usage of this product signifies your acceptance of the Terms of Use.