Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
An Investigation of How Quality Requirements are Specified in Industrial Practice
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering. Dept. of Computer Science, Lund University, SWE.
Dept. of Computer Science, Lund.
Dept. of Computer Science, Lund.
2013 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 55, no 7, p. 1224-1236Article in journal (Refereed) Published
Abstract [en]

Context: This paper analyses a sub-contractor specification in the mobile handset domain. Objective: The objective is to understand how quality requirements are specified and which types of requirements exist in a requirements specification from industry. Method: The case study is performed in the mobile handset domain, where a requirements specification was analyzed by categorizing and characterizing the pertaining requirements. Results: The requirements specification is written in structured natural language with unique identifiers for the requirements. Of the 2178 requirements, 827 (38%) are quality requirements. Of the quality requirements, 56% are quantified, i.e., having a direct metric in the requirement. The variation across the different sub-domains within the requirements specification is large. Conclusion: The findings from this study suggest that methods for quality requirements need to encompass many aspects to comprehensively support working with quality requirements. Solely focusing on, for example, quantification of quality requirements might overlook important requirements since there are many quality requirements in the studied specification where quantification is not appropriate.

Place, publisher, year, edition, pages
Elsevier, 2013. Vol. 55, no 7, p. 1224-1236
Keywords [en]
Quality requirements, Requirements specifications, Industrial practices, Specifications
National Category
Software Engineering
Research subject
Software Engineering
Identifiers
URN: urn:nbn:se:bth-21203DOI: 10.1016/j.infsof.2013.01.006OAI: oai:DiVA.org:bth-21203DiVA, id: diva2:1535184
Funder
VinnovaAvailable from: 2021-03-08 Created: 2021-03-08 Last updated: 2024-04-11Bibliographically approved
In thesis
1. Understanding and Supporting Quality Requirements Engineering in Software-intensive Product Development
Open this publication in new window or tab >>Understanding and Supporting Quality Requirements Engineering in Software-intensive Product Development
2020 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

[Background] Quality requirements deal with how well a product should perform the intended functionality. Failure to meet essential quality requirements can result in customer dissatisfaction, unusable products, or extra costs. [Objective] The aim is to identify challenges and needs in practice and design solutions for quality requirements engineering which can be applied in practice. [Results] In the two exploratory studies quality requirements engineering practices are investigated. I confirm that some quality requirements fulfillment is not simply being implemented or not, rather evaluated on a scale. Furthermore, some quality requirements are cross-functional. Also, the product lifecycle phase seems to influence both the prevalence and acceptance of quality requirements in the scope decision process. Lastly, relying on external stakeholders and upfront analysis seems to lead to long lead-times and an insufficient quality requirements scope. QREME is a conceptual quality requirements engineering model with a lifecycle perspective. It is built upon a construct with a strategic and tactical level, a product and data dimension to include data in the scope decision process, and a forward- and a feedback-loop to enable a data-driven scope decision process. QREME is validated with five companies in a multi-case study. QREME was able to capture the companies' ways of working and provide relevant improvement recommendations. Also, the presence of the underlying constructs was confirmed. [Conclusions] Quality requirements engineering should be integrated with the overall requirements process. The awareness of quality requirements on a strategic level and catering for the product and portfolio lifecycle are important for success. I conclude that there is potential in sources such as usage data, customer service data, and continuous experimentation to complement stakeholder analysis, expert input, and focus groups. However, there is a need to better understand challenges and needs in practice, especially from a lifecycle perspective. Furthermore, longitudinal studies are needed to evaluate quality requirements solutions over time -- to understand the impact, costs, and benefits.

Place, publisher, year, edition, pages
Karlskrona: Blekinge Tekniska Högskola, 2020. p. 258
Series
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 8
Keywords
Quality requirements, Requirements engineering
National Category
Software Engineering
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-20248 (URN)978-91-7295-407-6 (ISBN)
Public defence
2020-09-25, 13:00
Supervisors
Available from: 2020-08-07 Created: 2020-08-07 Last updated: 2021-03-08Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full text

Authority records

Olsson, Thomas

Search in DiVA

By author/editor
Olsson, Thomas
By organisation
Department of Software Engineering
In the same journal
Information and Software Technology
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 25 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf