Abstract
To understand the requirements process we need some knowledge about our own processes of understanding problems and communicating with people. Requirements analysis is a cognitive process in which we understand problems, learn about domains and negotiate to achieve what we want. We have to understand details describing the real world and then abstract these to create models of the domain. The process of abstraction, in cognitive terms, involves perception and comprehension (making sense of what we hear and see) and learning. Requirements analysis can be seen as discovery-based learning. We start with a vague understanding of what is required and of the domain in which the new system is to be designed. By gathering information and requirements we gradually learn about the goals the new system should fulfil. Requirements is also a form of problem solving. Once the desired state of the world has been understood, i.e. the requirements for a new system, the designer has to solve the problem of achieving them. The inevitable intertwining of requirements and design is a problem-solving process in which the designer uses memory of previous successful solutions, software engineering methods and creative thought to achieve a new design.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2002 Springer-Verlag London
About this chapter
Cite this chapter
Sutcliffe, A. (2002). Understanding People. In: User-Centred Requirements Engineering. Springer, London. https://doi.org/10.1007/978-1-4471-0217-5_2
Download citation
DOI: https://doi.org/10.1007/978-1-4471-0217-5_2
Publisher Name: Springer, London
Print ISBN: 978-1-85233-517-5
Online ISBN: 978-1-4471-0217-5
eBook Packages: Springer Book Archive