Anais Estendidos Do X Congresso Brasileiro De Software: Teoria E Prática (CBSoft Estendido 2019) 2019
DOI: 10.5753/cbsoft_estendido.2019.7666
|View full text |Cite
|
Sign up to set email alerts
|

PCM Tool: Privacy Requirements Specification in Agile Software Development

Abstract: Recent research has pointed out that software developers face difficulties to specify requirements for privacy-sensitive systems. To help addressing this issue, this paper presents a tool, called PCM Tool, that supports the Privacy Criteria Method (PCM) - an approach designed to guide the specification of privacy requirements in agile software development.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
4
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
5
1
1

Relationship

1
6

Authors

Journals

citations
Cited by 13 publications
(9 citation statements)
references
References 7 publications
0
4
0
Order By: Relevance
“…As ongoing research, we are analysing other data collected in the interviews to observe the behavioral and environmental factors of SCT, and how they interact with personal factors and affect developers' understanding of privacy. We are also working on defining and evaluating a requirements specification method designed to guide developers to consider privacy from the beginning of agile software development [8].…”
Section: Final Considerationsmentioning
confidence: 99%
“…As ongoing research, we are analysing other data collected in the interviews to observe the behavioral and environmental factors of SCT, and how they interact with personal factors and affect developers' understanding of privacy. We are also working on defining and evaluating a requirements specification method designed to guide developers to consider privacy from the beginning of agile software development [8].…”
Section: Final Considerationsmentioning
confidence: 99%
“…Sob essa perspectiva, os Requisitos Funcionais (RF) normalmente são descritos através das Estórias, enquanto os Cenários BDD, focam no comportamento das funcionalidades, descrevendo Requisitos Não-Funcionais (RNF) e de Domínio. É importante destacar que os RNF normalmente são mais complexos de compreender, elicitar, documentar e validar, uma vez que possuem uma natureza mais abstrata, são mais conflituosos entre si para atender e de difícil medição [19] [20]. Visando auxiliar o processo de Engenharia de Requisitos, este estudo busca mapear elementos do IDP com as cláusulas-padrão que determinam as estruturas de construção das Estórias de Usuário e Cenários BDD, mostrados anteriormente.…”
Section: Artefatos Da Engenharia De Software áGilunclassified
“…PRIPARE also considered including privacy in a dedicated sprint. In contrast to PRIPARE, Peixoto [23] aims to provide tool support to agile teams by guiding them through the specification of privacy requirements. However, extensive knowledge of privacy is required to fill out the form provided by the tools.…”
Section: A Privacy Requirements Engineeringmentioning
confidence: 99%
“…Despite the comprehensive approach offered by ProPAN [22], it still requires a huge workload of careful planning and expertise to follow its plan-driven steps. LINDDUN needs a significant amount of time for modeling the system [6], also in-depth privacy expertise is needed to specify accurate privacy criteria [23]. The lightweight approaches offered by Threat Poker and LINDDUN GO may not provide a comprehensive view of the system, especially for complex systems.…”
Section: A Privacy Requirements Engineeringmentioning
confidence: 99%
See 1 more Smart Citation