The solution domain is where 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.
CITATION STYLE
Dick, J., Hull, E., & Jackson, K. (2017). Requirements Engineering in the Solution Domain. In Requirements Engineering (pp. 135–158). Springer International Publishing. https://doi.org/10.1007/978-3-319-61073-3_6
Mendeley helps you to discover research relevant for your work.