Year-end Sale % OFF 
Abstract
This paper examines some deficiencies in structured systems development methods that have the effect of overlooking non-functional requirements. Evidence from four case studies shows that non-functional requirements are often overlooked, questioning users is insufficient, methodologies do not help in the elicitation of non-functional requirements and there is a lack of consensus about the meaning and utility of non-functional requirements. Some lessons are drawn from the domain of real time systems development. Finally a framework is advanced for taking a stakeholder approach to the conflict and organisational change issues associated with the elicitation stage of requirements analysis.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
