Ändra sökning
RefereraExporteraLänk till posten
Permanent länk

Direktlänk
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annat format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annat språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
Non-functional requirements in industry: Three case studies adopting an experience-based NFR method
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik. Fraunhofer Institute for Experimental Software Engineering, DEU.
Fraunhofer Institute for Experimental Software Engineering, DEU.
Fraunhofer Institute for Experimental Software Engineering, DEU.
Fraunhofer Institute for Experimental Software Engineering, DEU.
Visa övriga samt affilieringar
2005 (Engelska)Ingår i: Proceedings of the IEEE International Conference on Requirements Engineering 2005, IEEE Computer Society, 2005, s. 373-382Konferensbidrag, Publicerat paper (Refereegranskat)
Abstract [en]

Non-functional characteristics of products can be essential for business success and are a key differentiator between a company and its competitors. This paper presents the application of a systematic, experience-based method to elicit, document, and analyze non-functional requirements. The objective of the method is to achieve a minimal and sufficient set of measurable and traceable non-functional requirements. The method gives clear guidance for the requirements elicitation, using workshops for capturing the important quality aspects and eliciting the non-functional requirements. This paper shows its application in three different settings, reporting the experience and lessons learned from industrial case studies that applied our NFR method. As the case studies were applied in different domains and performed with companies of various maturity, and since different quality attributes were considered, a set of interesting results has emerged. Therefore, each case study tells its own story about how the elicitation of NFR in industry can work. The paper discusses the different settings and gives a comparison of the different lessons we learned from the case studies.

Ort, förlag, år, upplaga, sidor
IEEE Computer Society, 2005. s. 373-382
Nyckelord [en]
Requirements engineering, Information retrieval systems, Quality of service
Nationell ämneskategori
Programvaruteknik
Forskningsämne
Programvaruteknik
Identifikatorer
URN: urn:nbn:se:bth-21197DOI: 10.1109/re.2005.47OAI: oai:DiVA.org:bth-21197DiVA, id: diva2:1535171
Konferens
13th IEEE International Conference on Requirements Engineering, RE 2005, Paris, France, 29 August 2005 through 2 September 2005
Tillgänglig från: 2021-03-08 Skapad: 2021-03-08 Senast uppdaterad: 2021-03-11Bibliografiskt granskad
Ingår i avhandling
1. Understanding and Supporting Quality Requirements Engineering in Software-intensive Product Development
Öppna denna publikation i ny flik eller fönster >>Understanding and Supporting Quality Requirements Engineering in Software-intensive Product Development
2020 (Engelska)Doktorsavhandling, sammanläggning (Övrigt vetenskapligt)
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.

Ort, förlag, år, upplaga, sidor
Karlskrona: Blekinge Tekniska Högskola, 2020. s. 258
Serie
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 8
Nyckelord
Quality requirements, Requirements engineering
Nationell ämneskategori
Programvaruteknik
Forskningsämne
Programvaruteknik
Identifikatorer
urn:nbn:se:bth-20248 (URN)978-91-7295-407-6 (ISBN)
Disputation
2020-09-25, 13:00
Handledare
Tillgänglig från: 2020-08-07 Skapad: 2020-08-07 Senast uppdaterad: 2021-03-08Bibliografiskt granskad

Open Access i DiVA

Fulltext saknas i DiVA

Övriga länkar

Förlagets fulltext

Person

Olsson, Thomas

Sök vidare i DiVA

Av författaren/redaktören
Olsson, Thomas
Av organisationen
Institutionen för programvaruteknik
Programvaruteknik

Sök vidare utanför DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetricpoäng

doi
urn-nbn
Totalt: 100 träffar
RefereraExporteraLänk till posten
Permanent länk

Direktlänk
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annat format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annat språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf