C1 (3 points)
https://knobit.org/id/task/da-data-flows/C1
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/da-data-flows/C1 |
| rdfs:label | C1 (3 points) en |
| schema:hasPart | da-data-flows C1: the address is created twice |
| schema:hasPart | da-data-flows C1: the double creation is raised to the owners |
| schema:hasPart | da-data-flows C1: the address flows into CRM and loops |
| schema:identifier | C1 |
| schema:position | 1 |
| schema:text | The customer address, 1 each. (a) EN-012 Customer Address is created in both CRM (AS-004) and core banking (AS-001): reported as double creation. It is visible only by reading the matrix by entity; the flows alone show an exchange, not two creators. (b) Which application captures address changes is a business decision for the owners of the Party and Account domains: the answer proposes CRM (the system of record) as the only creator, marked proposed, and raises the question - it does not quietly delete core banking's C as if agreed. (c) The two flows FL-001 (CRM to core banking) and FL-006 (core banking to CRM) form a loop, and FL-006 writes into the address's system of record: FL-006 is retired (or redirected), leaving one direction from the system of record. en |