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
A natural language-based method to specify privacy requirements: an evaluation with practitioners
Universidade de Pernambuco (UPE), Brazil.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0002-3646-235x
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-0619-6027
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0002-0679-4361
Show others and affiliations
2024 (English)In: Requirements Engineering, ISSN 0947-3602, E-ISSN 1432-010X, Vol. 29, no 3, p. 279-301Article in journal (Refereed) Published
Abstract [en]

Organisations are becoming concerned with effectively dealing with privacy-related requirements. Existing Requirements Engineering methods based on structured natural language suffer from several limitations both in eliciting and specifying privacy requirements. In our previous study, we proposed a structured natural-language approach called the “Privacy Criteria Method” (PCM), which demonstrates potential advantages over user stories. Our goal is to present a PCM evaluation that focused on the opinions of software practitioners from different companies on PCM’s ability to support the specification of privacy requirements and the quality of the privacy requirements specifications produced by these software practitioners. We conducted a multiple case study to evaluate PCM in four different industrial contexts. We gathered and analysed the opinions of 21 practitioners on PCM usage regarding Coverage, Applicability, Usefulness, and Scalability. Moreover, we assessed the syntactic and semantic quality of the PCM artifacts produced by these practitioners. PCM can aid developers in elaborating requirements specifications focused on privacy with good quality. The practitioners found PCM to be useful for their companies’ development processes. PCM is considered a promising method for specifying privacy requirements. Some slight extensions of PCM may be required to tailor the method to the characteristics of the company. © The Author(s), under exclusive licence to Springer-Verlag London Ltd., part of Springer Nature 2024.

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2024. Vol. 29, no 3, p. 279-301
Keywords [en]
Empirical study, Privacy criteria method, Privacy requirements specification, Software development, Quality control, Requirements engineering, Semantics, Software design, Empirical studies, Engineering methods, Natural languages, Privacy requirement specification, Privacy requirements, Requirement engineering, Requirements specifications, Software practitioners, User stories, Specifications
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-26772DOI: 10.1007/s00766-024-00428-zISI: 001272283700001Scopus ID: 2-s2.0-85198939572OAI: oai:DiVA.org:bth-26772DiVA, id: diva2:1887738
Part of project
SERT- Software Engineering ReThought, Knowledge Foundation
Funder
Knowledge Foundation, 20180010Available from: 2024-08-09 Created: 2024-08-09 Last updated: 2024-09-19Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records

Gorschek, TonyMendez, DanielFucci, Davide

Search in DiVA

By author/editor
Gorschek, TonyMendez, DanielFucci, Davide
By organisation
Department of Software Engineering
In the same journal
Requirements Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

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