On the distinction of functional and quality requirements in practice

dc.contributor.authorEckhardt, Jonas
dc.contributor.authorVogelsang, Andreas
dc.contributor.authorMéndez Fernández, Daniel
dc.date.accessioned2018-05-04T14:51:28Z
dc.date.available2018-05-04T14:51:28Z
dc.date.issued2016
dc.description.abstractRequirements 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.isbn978-3-319-49094-6
dc.identifier.urihttps://depositonce.tu-berlin.de//handle/11303/7748
dc.identifier.urihttp://dx.doi.org/10.14279/depositonce-6926
dc.language.isoenen
dc.rights.urihttp://rightsstatements.org/vocab/InC/1.0/en
dc.subject.ddc004 Datenverarbeitung; Informatikde
dc.subject.otherquality requirementsen
dc.subject.otherfunctional requirementsen
dc.subject.othersurveyen
dc.titleOn the distinction of functional and quality requirements in practiceen
dc.typeConference Objecten
dc.type.versionacceptedVersionen
dcterms.bibliographicCitation.doi10.1007/978-3-319-49094-6_3en
dcterms.bibliographicCitation.editorAbrahamsson, Pekka
dcterms.bibliographicCitation.editorJedlitschka, Andreas
dcterms.bibliographicCitation.editorNguyen Duc, Anh
dcterms.bibliographicCitation.editorFelderer, Michel
dcterms.bibliographicCitation.editorAmasaki, Sousuke
dcterms.bibliographicCitation.editorMikkonen, Tommi
dcterms.bibliographicCitation.originalpublishernameSpringeren
dcterms.bibliographicCitation.originalpublisherplaceChamen
dcterms.bibliographicCitation.pageend47en
dcterms.bibliographicCitation.pagestart31en
dcterms.bibliographicCitation.proceedingstitleProduct-Focused Software Process Improvement. PROFES 2016en
dcterms.bibliographicCitation.volume2016en
tub.accessrights.dnbfreeen
tub.affiliationFak. 4 Elektrotechnik und Informatik>Inst. Telekommunikationssysteme>FG IT-basierte Fahrzeuginnovationende
tub.affiliation.facultyFak. 4 Elektrotechnik und Informatikde
tub.affiliation.groupFG IT-basierte Fahrzeuginnovationende
tub.affiliation.instituteInst. Telekommunikationssystemede
tub.publisher.universityorinstitutionTechnische Universität Berlinen
tub.series.issuenumber10027en
tub.series.nameLecture Notes in Computer Scienceen
Files
Original bundle
Now showing 1 - 1 of 1
Loading…
Thumbnail Image
Name:
2016_eckhardt_et-al_pp_final.pdf
Size:
1.05 MB
Format:
Adobe Portable Document Format
Description:
Collections