This paper examines some deficiencies in structured systems development met
hods that have the effect of overlooking non-functional requirements. Evide
nce from four case studies shows that non-functional requirements arc often
overlooked, questioning users is insufficient, methodologies do not help i
n the elicitation of non-functional requirements and there is a lack of con
sensus about the meaning and utility of non-functional requirements. Some l
essons are drawn from the domain of real time systems development. Finally
a framework is advanced for taking a stakeholder approach to the conflict a
nd organisational change issues associated with the elicitation stage of re
quirements analysis. (C) 2001 Elsevier Science B.V. All rights reserved.