Proceedings of the 14th International Conference on Evaluation of Novel Approaches to Software Engineering 2019
DOI: 10.5220/0007722900680079
|View full text |Cite
|
Sign up to set email alerts
|

A Formal Modeling Scheme for Analyzing a Software System Design against the GDPR

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
3
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 0 publications
0
3
0
Order By: Relevance
“…While there are works in literature [50,[52][53][54][55][56][57] that have focused on extracting privacy-related and software requirements from GDPR, our work is focused on assisting developers with the compliance requirements associated with Android permissions declarations and UML design based on articles from the GDPR law. We provide a literature review of two key areas that relate to our work: (i) completeness checking of privacy policies, and (ii) completeness checking of software (applications) against data protection regulations.…”
Section: Literature Reviewmentioning
confidence: 99%
See 1 more Smart Citation
“…While there are works in literature [50,[52][53][54][55][56][57] that have focused on extracting privacy-related and software requirements from GDPR, our work is focused on assisting developers with the compliance requirements associated with Android permissions declarations and UML design based on articles from the GDPR law. We provide a literature review of two key areas that relate to our work: (i) completeness checking of privacy policies, and (ii) completeness checking of software (applications) against data protection regulations.…”
Section: Literature Reviewmentioning
confidence: 99%
“…The algorithms investigated are Universal Sentence Encoder (USE) [40], Sentence Bert (SBERT) [41], Glove [42], Bi-Directional Encoder Representations (BERT) word embedding [43], N-Grams, Vector Space Modelling (VSM) [44,45] and Fuzzy String Matching (FSM). • Requirements Engineering: While other techniques have operationalized requirements from texts using statistical NLP [46], semantic frames [47], semantic parsing [48], domain-specific language [49], graphical modelling language [50], privacy-enhanced busi-ness process model and notation [51],information-flow labels [21], we used statistical NLP and UML mapping to identify permission-related requirement. • Privacy Policy Generation at Design Time Using UML Diagrams: Using modelling languages for visualising a system at design time, we implement a solution that helps developers to generate compliant sensitive permission declarations using UML diagrams (class diagrams, activity diagrams etc) during design time.…”
mentioning
confidence: 99%
“…Assessment pipelines, therefore, need to involve interdisciplinary knowledge, including evaluation criteria supported by legal and not only technical interpretations. Some research explicitly highlights the need to incorporate interdisciplinary knowledge into the evaluation pipeline (ID17, ID1051), while others do include a preliminary interdisciplinary analysis (ID21,ID25).…”
Section: Trends and Findingsmentioning
confidence: 99%