IEEE Software · 2008 · 45 citations · 3 references
EngineeringDesignRequirements EngineeringSoftware EngineeringSystems DesignRequirements AnalysisRequirements ElicitationRequirements ManagementSystem RequirementsUser Needs AnalysisUser RequirementsRequirements Engineering ProcessUser Requirement AnalysisUser Requirements Analysis
In software, we often talk about user requirements and system requirements. Most people know the terms: users give you user requirements, designers work from system requirements. The terms have entered our lingua franca. However, in my experience, people - stakeholders, analysts, and designers - often fail to differentiate the roles of these two kinds of requirements. Unfortunately, treating user and system requirements as the same thing can create problems for projects. In this column I unpack some problems I've observed with user requirements and system requirements and explore what we can do about them.
3
Goal-directed requirements acquisition
Anne Dardenne, Axel van Lamsweerde, Stephen Fickas · Science of Computer Programming · 1993 · 2K citations
Understanding "why" in software process modelling, analysis, and design
Eric Yu, John Mylopoulos · 2002 · 167 citations
Computing, Design, Process Design +10