System for normalizing data dependency effects across an electronic network environment

A computer implemented method for normalizing data dependency effects across an electronic network environment, the method comprising:

• electronically receiving a technical business requirement document (BRD) from an external source;
• implementing a data sourcing language (DSL) script on the technical BRD;
• generating one or more data processing instructions based on at least implementing the DSL on the technical BRD;
• initiating a data requirement traceability (DRT) engine on the one or more data processing instructions, wherein the DRT engine is configured to:
• ingest the one or more data processing instructions;
• automatically record traceability between the one or more data processing instructions and the technical BRD;
• and
• validate the one or more data processing instructions based on at least recording the traceability between the one or more data processing instructions and the technical BRD;
• initiating a data sourcing (DS) engine configured to retrieve, from one or more authorized data sources, input data;
• initiating a data processing core (DPC) engine configured to implement the one or more data processing instructions on the input data;
• dividing the input data into one or more input sub-streams;
• generating an output data based on at least implementing the one or more data processing instructions on the input data;
• transforming the one or more input sub-streams to one or more output sub-streams based on at least the one or more data processing instructions;
• and
• initiating a data processing scenario (DPS) engine to:
• allocate one or more versions to each of the one or more input sub-streams and the one or more output sub-streams corresponding to each of the one or more input sub-streams;
• and
• initiate a versioning dashboard script configured to generate a graphical representation of the one or more versions of the one or more input sub-streams and the one or more output sub-streams, wherein the graphical representation indicates an initial point of origin of each of the one or more input sub-streams, one or more intermediary points of each of the one or more input sub-streams, and a destination point of each of the one or more input sub-streams.

A computer program product for normalizing data dependency effects across an electronic network environment, the computer program product comprising a non-transitory computer-readable medium comprising code causing a first apparatus to:

• electronically receive a technical business requirement document (BRD) from an external source;
• implement a data sourcing language (DSL) script on the technical BRD;
• generate one or more data processing instructions based on at least implementing the DSL on the technical BRD;
• initiate a data requirement traceability (DRT) engine on the one or more data processing instructions, wherein the DRT engine is configured to:
• ingest the one or more data processing instructions;
• automatically record traceability between the one or more data processing instructions and the technical BRD;
• and
• validate the one or more data processing instructions based on at least recording the traceability between the one or more data processing instructions and the technical BRD;
• initiate a data sourcing (DS) engine configured to retrieve, from one or more authorized data sources, input data;
• initiate a data processing core (DPC) engine configured to implement the one or more data processing instructions on the input data;
• divide the input data into one or more input sub-streams;
• generate an output data based on at least implementing the one or more data processing instructions on the input data;
• transform the one or more input sub-streams to one or more output sub-streams based on at least the one or more data processing instructions;
• and
• initiate a data processing scenario (DPS) engine to:
• allocate one or more versions to each of the one or more input sub-streams and the one or more output sub-streams corresponding to each of the one or more input sub-streams;
• and
• initiate a versioning dashboard script configured to generate a graphical representation of the one or more versions of the one or more input sub-streams and the one or more output sub-streams, wherein the graphical representation indicates an initial point of origin of each of the one or more input sub-streams, one or more intermediary points of each of the one or more input sub-streams, and a destination point of each of the one or more input sub-streams.