| dc.contributor.author | Glinz, Martin | |
| dc.date.accessioned | 2023-03-03T11:25:15Z | |
| dc.date.available | 2023-03-03T11:25:15Z | |
| dc.date.issued | 2016 | |
| dc.identifier.issn | 0720-8928 | |
| dc.identifier.uri | http://dl.gi.de/handle/20.500.12116/40692 | |
| dc.description.abstract | As unambiguous and complete requirements specifications are not feasible in most cases, we investigate the question how much Requirements Engineering (RE) we actually need for the development of successful systems and products. Based on the notion of value of requirements, we discuss risk, shared understanding and customersupplier relationship as major influencing factors. | en |
| dc.language.iso | en | |
| dc.publisher | Geselllschaft für Informatik e.V. | |
| dc.relation.ispartof | Softwaretechnik-Trends Band 36, Heft 3 | |
| dc.title | How much Requirements Engineering do we need? | en |
| dc.type | Journal Articles | |
| dc.pubPlace | Bonn | |
| mci.conference.sessiontitle | Berichte aus den Fachgruppen und Arbeitskreisen | |
