search

mojaloop / fraud_risk_management

Central repo for fraud and risk management development and specifications
Other
13 stars 7 forks source link

[EPIC] Data integration/processing user interface or builder #21

Open JustusOrtlepp opened 3 years ago

JustusOrtlepp commented 3 years ago

Description

A data integration/processing user interface will allow developers to create and update data processing routines as plugable modules in an easy and efficient manner.

For developers who write code to validate, cleanse, standardise, transform and enrich incoming transactional data the data processing platform is an Integrated Development Environment that allows developers to unlike a more traditional approach where every routine is hard-coded to a specific purpose our solution allows developers to create modular, reusable and configurable data processing routines

Initiative / goal

If one of the goals of a Mojaloop FRM solution is reach and applicability beyond just the Mojaloop FRM platform, then the speed and ease of implementation and integration within a new and unfamiliar environment will be an essential attribute.

Hypothesis

Visualise data entering the system and passing through the rules engine as a stream of information. A developer must be able to add data processing routines in the stream as discrete, reusable and fit-for-purpose modules required to process the data for specific purposes, including the up-front data preparation and transformation.

Acceptance criteria and must have scope

A standard and well-documented library of common data processing functions Branching of the information stream for parallel processing Recombination of the information stream Looping of a particular data process or cluster of data processes Paramterisation of a data process Data lineage/provenance Audit logging of developer changes

Leading indicators

Estimation of the effort to implement may exceed appetite

Nonfunctional requirements (NFRs)

Nonfunctional requirements associated with this epic.

Stakeholders

Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.

Timeline

What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date.

JustusOrtlepp commented 3 years ago

Mojaloop FRM solution compliance with ISO20022 provides integrating platforms (including the Mojaloop switching hub) with a static target for integration and it is expected that the integration will be handled through an adapter developed by the integrating system, if that system is not natively ISO20022 compliant. From this perspective (outside the doorstep to the FRM system), the integration IDE will not be particularly useful, but the true value lies in the data processing that will be performed on the data stream once it is inside the system boundaries. Data validation, cleansing, standardisation, transformation and enrichment will be an ongoing activity, not only for new system integrations, but also as fraud risk typologies evolve over time and the specific requirements for data and data preparation changes.