A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf
.
Requirements Engineering: Best Practice
[chapter]
2014
Requirements Engineering for Digital Health
Many software solutions have failed because they did not meet stakeholder needs. In response to this problem a massive amount of techniques were developed to elicit stakeholder needs, to analyze the implications of these needs on the software, to specify proposed software products, and to check acceptance of these proposals. However, many of these techniques did not become industrial practice because they were not practicable or ineffective when used in real-world projects. To obtain an
doi:10.1007/978-3-319-09798-5_2
fatcat:ot2l6hvrorbsloe6d3cmmbrci4