Pith Number

pith:EMSZVE4E

pith:2026:EMSZVE4EJOVJY57U4SN6UMWED5

not attested not anchored not stored refs resolved

Modelling GDPR-based Privacy Requirements with Software Engineering Diagrams: A Systematic Literature Review

Anna Philippou, Evangelia Vanezi, Georgia M. Kapitsaki

A review of 18 studies shows current software engineering diagrams capture only partial GDPR privacy requirements and lack integration across the development lifecycle.

arxiv:2604.16361 v1 · 2026-03-19 · cs.SE

Open paper page JSON Open Graph Bundle Merged state Verified badge What is a Pith Number?

Add to your LaTeX paper

\usepackage{pith}
\pithnumber{EMSZVE4EJOVJY57U4SN6UMWED5}

Prints a linked badge after your title and injects PDF metadata. Compiles on arXiv. Learn more · Embed verified badge

Record completeness

1 Bitcoin timestamp

2 Internet Archive

3 Author claim open · sign in to claim

4 Citations open

5 Replications open

✓ Portable graph bundle live · download bundle · merged state

The bundle contains the canonical record plus signed events. A mirror can host it anywhere and recompute the same current state with the deterministic merge algorithm.

Claims

C1strongest claim

The findings highlight the need for inter-diagram integration, full lifecycle traceability mechanisms, tool support, and automated compliance checking.

C2weakest assumption

That the 18 primary studies selected via the search protocol provide a comprehensive and unbiased representation of all relevant research on modelling GDPR-based privacy requirements with SE diagrams.

C3one line summary

A systematic literature review of 18 studies from 2017-2025 categorizes SE diagrams used for GDPR privacy requirements and highlights gaps in integration, traceability, tool support, and automated compliance checking.

References

3 extracted · 3 resolved · 0 Pith anchors

[1] is this ohk´ ey? 2019

[2] V anezi, E., V asileiou, A., and Papadopoulos, G 2021

[3] Springer. V eseli, F., Olvera, J. S., Pulls, T., and Rannenberg, K. (2019). Engineering privacy by design: lessons from the design and implementation of an identity wallet platform. In Proceedings of 2019

Formal links

2 machine-checked theorem links

Receipt and verification

First computed	2026-05-28T02:04:47.930787Z
Builder	pith-number-builder-2026-05-17-v1
Signature	Pith Ed25519 (`pith-v1-2026-05`) · public key
Schema	pith-number/v1.0

Canonical hash

23259a93844baa9c77f4e49bea32c41f54330fa26d223a518b3f8332bce90058

Aliases

arxiv: 2604.16361 · arxiv_version: 2604.16361v1 · doi: 10.48550/arxiv.2604.16361 · pith_short_12: EMSZVE4EJOVJ · pith_short_16: EMSZVE4EJOVJY57U · pith_short_8: EMSZVE4E

Agent API

Resolver JSON Graph JSON Events JSON Schema Signing key

Verify this Pith Number yourself

curl -sH 'Accept: application/ld+json' https://pith.science/pith/EMSZVE4EJOVJY57U4SN6UMWED5 \
  | jq -c '.canonical_record' \
  | python3 -c "import sys,json,hashlib; b=json.dumps(json.loads(sys.stdin.read()), sort_keys=True, separators=(',',':'), ensure_ascii=False).encode(); print(hashlib.sha256(b).hexdigest())"
# expect: 23259a93844baa9c77f4e49bea32c41f54330fa26d223a518b3f8332bce90058

Canonical record JSON

{
  "metadata": {
    "abstract_canon_sha256": "cb2ef2a36e051e11281be9b61b8f4fc549a2328eb696f7ea943ea5934e8c70a2",
    "cross_cats_sorted": [],
    "license": "http://creativecommons.org/licenses/by-nc-nd/4.0/",
    "primary_cat": "cs.SE",
    "submitted_at": "2026-03-19T15:07:45Z",
    "title_canon_sha256": "af459dfeb16aa7ddf5cbea9e4ee7f0432c502588e4fb5c7f49b7614039bf408d"
  },
  "schema_version": "1.0",
  "source": {
    "id": "2604.16361",
    "kind": "arxiv",
    "version": 1
  }
}