I1 (3 points)
https://knobit.org/id/task/da-flows-roadmap-dependencies/I1
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-flows-roadmap-dependencies/I1 |
| rdfs:label | I1 (3 points) en |
| schema:hasPart | da-flows-roadmap-dependencies I1: card limits created twice within a transition state |
| schema:hasPart | da-flows-roadmap-dependencies I1: one creator per card entity at the end of each state |
| schema:hasPart | da-flows-roadmap-dependencies I1: card transactions moved by no package |
| schema:identifier | I1 |
| schema:position | 3 |
| schema:text | Transition states read by entity, 1 each. (a) WP-021 makes card management create EN-013 but leaves the legacy card system's CRU on it: card limits are created in two applications at the end of TS-1 and TS-2. Found and fixed: AS-010 keeps EN-013 as R only, fed by a flow from AS-002 (FL-031 extended with EN-013, or a new flow), or loses it once core banking reads from card management. (b) No package moves the creation of EN-014 Card Transaction to AS-002 (placement TP-022 unreached): FL-032 and FL-034 send EN-014 from AS-002, which never holds it, and after the switch-off the warehouse and the fraud engine read card transactions that nothing creates. A package (new or extended, proposed) realises TP-022 and makes AS-002 the creator of EN-014 no later than the flows that send it from AS-002, keeping every flow's source holding what it sends in every state. (c) state_creators is correct for the answer's own packages: for each of TS-1..TS-3 and each of EN-008, EN-013, EN-014 exactly one creator, and AS-002 for all three by TS-3. en |