C2 (3 points)
https://knobit.org/id/task/mm-requirements-use-cases/C2
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/mm-requirements-use-cases/C2 |
| rdfs:label | C2 (3 points) en |
| schema:hasPart | mm-requirements-use-cases C2a: same-day lineage from a quarterly wiki (UC-101, MX-102) replaced by SQL parsing on deployment |
| schema:hasPart | mm-requirements-use-cases C2b: classifier-inferred personal data classes published as approved (MX-107) made candidates until confirmed |
| schema:hasPart | mm-requirements-use-cases C2c: curated workbook steps with a vacant curator (MX-104) given a curator who holds the role |
| schema:identifier | C2 |
| schema:position | 2 |
| schema:text | Capture method held against freshness, status and curator, 1 each. (a) UC-101 needs lineage the same day as a pipeline change; the risk data mart's pipelines deploy daily and MX-102 redraws lineage in a wiki quarterly: reported as freshness the capture method cannot meet, and lineage harvested instead by the catalogue's SQL parsing on each deployment, with MX-102 retired or kept only for what parsing cannot see. (b) MX-107 is inferred by the classifier and published as approved: reported, and published as candidate (or proposed, recorded - any status short of approved) until a named role - the Data protection officer or a delegate - confirms each class. (c) MX-104 is curated by the Metadata curator, a vacant post: reported, and the curator becomes a role with a current holder (the Head of Credit Risk Modelling, who owns the workbook, is the natural one), or the vacancy is raised as an open question asking who curates until the post is filled. Leaving the vacant role, or null, with no note earns nothing. en |