On the distinction of functional and quality requirements in practice
| dc.contributor.author | Eckhardt, Jonas | |
| dc.contributor.author | Vogelsang, Andreas | |
| dc.contributor.author | Méndez Fernández, Daniel | |
| dc.date.accessioned | 2018-05-04T14:51:28Z | |
| dc.date.available | 2018-05-04T14:51:28Z | |
| dc.date.issued | 2016 | |
| dc.description.abstract | Requirements are often divided into functional requirements (FRs) and quality requirements (QRs). However, we still have little knowledge about to which extent this distinction makes sense from a practical perspective. In this paper, we report on a survey we conducted with 103 practitioners to explore whether and, if so, why they handle requirements labeled as FRs differently from those labeled as QRs. We additionally asked for consequences of this distinction w.r.t. the development process. Our results indicate that the development process for requirements of the two classes strongly differs (e.g., in testing). We identified a number of reasons why practitioners do (or do not) distinguish between QRs and FRs in their documentation and we analyzed both problems and benefits that arise from that. We found, for instance, that many reasons are based on expectations rather than on evidence. Those expectations are, in fact, not reflected in specific negative or positive consequences per se. It therefore seems more important that the decision whether to make an explicit distinction or not should be made consciously such that people are also aware of the risks that this distinction bears so that they may take appropriate countermeasures. | en |
| dc.identifier.isbn | 978-3-319-49094-6 | |
| dc.identifier.uri | https://depositonce.tu-berlin.de/handle/11303/7748 | |
| dc.identifier.uri | http://dx.doi.org/10.14279/depositonce-6926 | |
| dc.language.iso | en | en |
| dc.rights.uri | http://rightsstatements.org/vocab/InC/1.0/ | en |
| dc.subject.ddc | 004 Datenverarbeitung; Informatik | de |
| dc.subject.other | quality requirements | en |
| dc.subject.other | functional requirements | en |
| dc.subject.other | survey | en |
| dc.title | On the distinction of functional and quality requirements in practice | en |
| dc.type | Conference Object | en |
| dc.type.version | acceptedVersion | en |
| dcterms.bibliographicCitation.doi | 10.1007/978-3-319-49094-6_3 | en |
| dcterms.bibliographicCitation.editor | Abrahamsson, Pekka | |
| dcterms.bibliographicCitation.editor | Jedlitschka, Andreas | |
| dcterms.bibliographicCitation.editor | Nguyen Duc, Anh | |
| dcterms.bibliographicCitation.editor | Felderer, Michel | |
| dcterms.bibliographicCitation.editor | Amasaki, Sousuke | |
| dcterms.bibliographicCitation.editor | Mikkonen, Tommi | |
| dcterms.bibliographicCitation.originalpublishername | Springer | en |
| dcterms.bibliographicCitation.originalpublisherplace | Cham | en |
| dcterms.bibliographicCitation.pageend | 47 | en |
| dcterms.bibliographicCitation.pagestart | 31 | en |
| dcterms.bibliographicCitation.proceedingstitle | Product-Focused Software Process Improvement. PROFES 2016 | en |
| dcterms.bibliographicCitation.volume | 2016 | en |
| tub.accessrights.dnb | free | en |
| tub.affiliation | Fak. 4 Elektrotechnik und Informatik::Inst. Telekommunikationssysteme::FG IT-basierte Fahrzeuginnovationen | de |
| tub.affiliation.faculty | Fak. 4 Elektrotechnik und Informatik | de |
| tub.affiliation.group | FG IT-basierte Fahrzeuginnovationen | de |
| tub.affiliation.institute | Inst. Telekommunikationssysteme | de |
| tub.publisher.universityorinstitution | Technische Universität Berlin | en |
| tub.series.issuenumber | 10027 | en |
| tub.series.name | Lecture Notes in Computer Science | en |