This Article 
 Bibliographic References 
 Add to: 
User Requirements and System Requirements
March/April 2008 (vol. 25 no. 2)
pp. 90-91
Neil Maiden, City University, London
Stakeholders, analysts, and designers often fail to differentiate the roles of user and system requirements. Unfortunately, treating them as the same thing can create problems for projects. Here are three strategies for managing user and system requirements more effectively.

1. A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-Directed Requirements Acquisition," Science of Computing Programming, vol. 20, nos. 1–2, 1993, pp. 3–50.
2. E. Yu and J.M. Mylopoulos, "Understanding 'Why' in Software Process Modeling, Analysis, and Design," Proc. 16th Int'l Conf. Software Eng., IEEE CS Press, 1994, pp. 159–168.
3. A. Vickers, "Satisfying Business Problems," IEEE Software, vol. 24, no. 3, 2007, pp. 18–20.
4. N. Maiden, A. Gizikis, and S. Robertson, "Provoking Creativity: Imagine What Your Requirements Could Be Like," IEEE Software, vol. 21, no. 5, 2004, pp. 68–75.

Index Terms:
requirements, user requirements, system requirements
Neil Maiden, "User Requirements and System Requirements," IEEE Software, vol. 25, no. 2, pp. 90-91, March-April 2008, doi:10.1109/MS.2008.54
Usage of this product signifies your acceptance of the Terms of Use.