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 approach for performance requirements verification and test environments generation
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0001-8142-9631
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-1181-9049
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-4118-0952
2023 (English)In: Requirements Engineering, ISSN 0947-3602, E-ISSN 1432-010X, Vol. 28, no 1, p. 117-144Article in journal (Refereed) Published
Abstract [en]

Model-based testing (MBT) is a method that supports the design and execution of test cases by models that specify theintended behaviors of a system under test. While systematic literature reviews on MBT in general exist, the state of the arton modeling and testing performance requirements has seen much less attention. Therefore, we conducted a systematic map-ping study on model-based performance testing. Then, we studied natural language software requirements specificationsin order to understand which and how performance requirements are typically specified. Since none of the identified MBTtechniques supported a major benefit of modeling, namely identifying faults in requirements specifications, we developed thePerformance Requirements verificatiOn and Test EnvironmentS generaTion approach (PRO-TEST). Finally, we evaluatedPRO-TEST on 149 requirements specifications. We found and analyzed 57 primary studies from the systematic mappingstudy and extracted 50 performance requirements models. However, those models don’t achieve the goals of MBT, whichare validating requirements, ensuring their testability, and generating the minimum required test cases. We analyzed 77 Soft-ware Requirements Specification (SRS) documents, extracted 149 performance requirements from those SRS, and illustratethat with PRO-TEST we can model performance requirements, find issues in those requirements and detect missing ones.We detected three not-quantifiable requirements, 43 not-quantified requirements, and 180 underspecified parameters in the149 modeled performance requirements. Furthermore, we generated 96 test environments from those models. By modelingperformance requirements with PRO-TEST, we can identify issues in the requirements related to their ambiguity, measur-ability, and completeness. Additionally, it allows to generate parameters for test environments

Place, publisher, year, edition, pages
Springer, 2023. Vol. 28, no 1, p. 117-144
Keywords [en]
Model-based testing, Performance requirements modeling, Performance aspects, Natural language requirements
National Category
Software Engineering Computer Systems
Identifiers
URN: urn:nbn:se:bth-22848DOI: 10.1007/s00766-022-00379-3ISI: 000782347800001Scopus ID: 2-s2.0-85128212480OAI: oai:DiVA.org:bth-22848DiVA, id: diva2:1653133
Part of project
D-CAT – Digital Collaboration and Automized Tracing Of Information, Swedish Transport Administration
Funder
Swedish Transport Administration, DCAT project
Note

open access

Available from: 2022-04-21 Created: 2022-04-21 Last updated: 2025-09-30Bibliographically approved
In thesis
1. Reducing the Distance Between Requirements Engineering and Verification
Open this publication in new window or tab >>Reducing the Distance Between Requirements Engineering and Verification
2022 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

Background Requirements engineering and verification (REV) processes play es-sential roles in software product development. There are physical and non-physicaldistances between entities (actors, artifacts, and activities) in these processes. Cur-rent practices that reduce the distances, such as automated testing and alignmentof document structure and tracing only partially close the above mentioned gap.Objective The aim of this thesis is to investigate solutions w.r.t their abilityto reduce the distances between requirements engineering and verification. Twotechniques that are explored in this thesis are automated testing (model-basedtesting, MBT) and alignment of document structure and tracing (traceability).Method The research methods used in this thesis are systematic mapping, soft-ware requirements mining, case study, literature survey, validation study, and de-sign science.Results MBT and traceability are effective in reducing the distance between re-quirements and verification. However, both activities have some shortcoming thatneeds to be addressed when used for that purpose. Current MBT techniques inthe context of software performance do not attain all the goals of MBT: 1) require-ments validation, 2) checking the testability of requirements, and 3) the generationof an efficient test suite. These goals are essential to reduce the distance. We de-veloped and assessed performance requirements verification and test environmentgeneration approach to tackle these shortcomings. Also, traceability between re-quirements and verification suffers from the low granularity of trace links and doesnot support the verification of all requirements. We propose the use of taxonomictrace links to trace and align the structure of requirements specifications and ver-ification artifacts. The results from the validation study show that the solution isfeasible in practice. However, this comes with challenges that need to be addressed.Conclusion MBT and improved traceability reduce multiple distances betweenactors, artifacts, and activities in the requirements engineering and verificationprocess. MBT is most effective in reducing the distances when the model used isbuilt from the requirements. Traceability is essential in easing access to relevantinformation when needed and should not be seen as an overhead. When creatingtrace links, we need to consider the difference in the abstraction, structure, andtime between the linked artifacts

Place, publisher, year, edition, pages
Karlskrona: Blekinge Tekniska Högskola, 2022
Series
Blekinge Institute of Technology Licentiate Dissertation Series, ISSN 1650-2140 ; 4
Keywords
Requirements, Model-Based Testing, Traceability.
National Category
Software Engineering
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-23570 (URN)
Presentation
2022-10-05, J1630, Valhallavägen 1, 371 41, Karlskrona, 09:00 (English)
Opponent
Supervisors
Funder
Swedish Transport Administration, DCAT
Note

Chapter 3 and 4 are papers submitted to journals, and therefore removed from the fulltext file.

Available from: 2022-08-25 Created: 2022-08-24 Last updated: 2025-09-30Bibliographically approved

Open Access in DiVA

fulltext(1566 kB)823 downloads
File information
File name FULLTEXT01.pdfFile size 1566 kBChecksum SHA-512
441a27b75708e02fa1f08af1d2ad1d98bf2c82faabe00d8f6e09901e86b0a3cf8fed23da2a874968cb5ffa3a3b2706cf6a81bd8e76f3b6d31eda38a375c6aef6
Type fulltextMimetype application/pdf

Other links

Publisher's full textScopus

Authority records

Abdeen, WaleedChen, XingruUnterkalmsteiner, Michael

Search in DiVA

By author/editor
Abdeen, WaleedChen, XingruUnterkalmsteiner, Michael
By organisation
Department of Software Engineering
In the same journal
Requirements Engineering
Software EngineeringComputer Systems

Search outside of DiVA

GoogleGoogle Scholar
Total: 825 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 1839 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