This Article 
 Bibliographic References 
 Add to: 
Exactly How Are Requirements Written?
January/February 2012 (vol. 29 no. 1)
pp. 26-27
Neil Maiden, City University London
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
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.