Abstract
This chapter discusses requirements in the solution domain – the domain in which engineers use their ingenuity to solve problems. The primary characteristic that differentiates the solution domain from the problem domain is that, invariably requirements engineering in the solution domain starts with a given set of requirements. In the problem domain requirements engineering starts with a vague objective or wish list. The extent to which the input requirements for the solution domain are “well formed” depends upon the quality of the people within the customer organisation that developed them. In an ideal world, all the requirements would be clearly articulated, individual test able requirements.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2017 Springer International Publishing Switzerland
About this chapter
Cite this chapter
Dick, J., Hull, E., Jackson, K. (2017). Requirements Engineering in the Solution Domain. In: Requirements Engineering. Springer, Cham. https://doi.org/10.1007/978-3-319-61073-3_6
Download citation
DOI: https://doi.org/10.1007/978-3-319-61073-3_6
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-61072-6
Online ISBN: 978-3-319-61073-3
eBook Packages: Computer ScienceComputer Science (R0)