I1 (2 points)
https://knobit.org/id/task/mm-requirements-use-cases/I1
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| rdfs:label | I1 (2 points) en |
| schema:hasPart | mm-requirements-use-cases I1a: lake files needed within minutes (UC-108) served from the ingest metastore, not a weekly file scan |
| schema:hasPart | mm-requirements-use-cases I1b: attribute definitions retyped from the modelling tool (MX-110) harvested from its repository or XMI |
| schema:hasPart | mm-requirements-use-cases I1c: a failing core banking scan nobody noticed (MX-111) given load monitoring with an owner |
| schema:hasPart | mm-requirements-use-cases I1d: lineage for ECB inspectors delivered in a portal they cannot reach (UC-102) handed over as a report |
| schema:identifier | I1 |
| schema:position | 4 |
| schema:text | The right source and delivery for the need, 0.5 each. (a) UC-108 needs files within 15 minutes of landing, and MX-109 scans the lake's file listing weekly: the lake metadata comes from the lake metastore, which the ingest framework fills as each file lands, read through the catalogue's live connector - a daily (or more frequent) scan of the file listing does not earn it. (b) MX-110 has BI developers retype what the data modelling tool AS-030 holds: it is harvested by the catalogue's modelling tool scanner, or imported as XMI. (c) The scan log shows MX-111 (core banking) failing since 12 October with no note in the draft: reported, with someone (the Data platform lead) made responsible for fixing it and for monitoring the loads - alerts on failure or load statistics. (d) UC-102's delivery has the ECB inspectors browse a portal they cannot reach: a lineage report or export of the COREP figures is handed over to them. en |