Abstract
According to Pohl’s definition of Requirements Engineering (RE):
Requirements Engineering can be defined as the systematic process of developing requirements through an iterative co-operative process of analysing the problem, documenting the resulting observations in a variety of representation formats, and checking the accuracy of the understanding gained. (Pohl, 1993)
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Notes
The word ‘techniques’ means a method of performing or executing some specialised activity (Penguin English Dictionary) and is used throughout this book as a generic term for methods, tools, models, etc.
‘Agreed requirements’ means agreed between those people who have to’ sign off’ the requirements before design commences, people such as those mentioned in paragraph 3 of the Project Manager’s remit.
The cost of the project was around $1M; the elapsed time to completion of the project was 5 years; more than 30 people were involved; the cost and elapsed time allocated to RE process was less than 5% of the total project.
The sum of percentages is greater than 100% because more than one option could be chosen.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 1996 Springer-Verlag London Limited
About this chapter
Cite this chapter
Macaulay, L.A. (1996). The Role of Requirements Engineering Techniques. In: Requirements Engineering. Applied Computing. Springer, London. https://doi.org/10.1007/978-1-4471-1005-7_2
Download citation
DOI: https://doi.org/10.1007/978-1-4471-1005-7_2
Publisher Name: Springer, London
Print ISBN: 978-3-540-76006-1
Online ISBN: 978-1-4471-1005-7
eBook Packages: Springer Book Archive