A dependency analyzer for use with a data processing system configured to execute programs (109, 150, 160, 170) in any of multiple computer programming languages that access a plurality of records comprising fields, the dependency analyzer configured for dependency analysis of programs (109, 150, 160, 170) in the multiple computer programming languages, the dependency analysis comprising computing dependency information relating to field-level lineage across programs (109, 150, 160, 170) in the multiple computer programming languages, the dependency analyzer comprising: a front end configured to process a plurality of programs (109, 150, 160, 170) controlling the data processing system, wherein the plurality of programs (109, 150, 160, 170) are written in a plurality of programming languages of the multiple programming languages, and wherein the front end comprises a plurality of front end modules (152, 162, 172), each front end module (152, 162, 172) configured to receive as input a computer program (109, 150, 160, 170) of the plurality of programs (109, 150, 160, 170) written in a different programming language of the plurality of programming languages and to output a language-independent data structure representing dependencies on fields of the plurality of records created within the program, wherein, said language-independent data structure is comprised of one or more dependency constructs, wherein each dependency construct includes an indication of at least one field and a dependency related to the at least one field; a back end configured to receive language independent data structures from the plurality of front end modules (152, 162, 172) and to output dependency information for the data processing system representing dependencies created within the plurality of programs (109, 150, 160, 170), wherein the dependency information comprises field-level dependencies introduced in multiple programs (109, 150, 160, 170) of the plurality of programs (109, 150, 160, 170) such that the dependency information comprises field-level lineage across the plurality of programs (109, 150, 160, 170); a first tool configured to load the dependency information in a metadata repository; and a second tool configured to receive as input an indication of a field used by the data processing system, to access the metadata repository and to output indications of programs (109, 150, 160, 170) of the plurality of programs (109, 150, 160, 170) that introduce a dependency impacting the indicated field. a front end configured to process a plurality of programs (109, 150, 160, 170) controlling the data processing system, wherein the plurality of programs (109, 150, 160, 170) are written in a plurality of programming languages of the multiple programming languages, and wherein the front end comprises a plurality of front end modules (152, 162, 172), each front end module (152, 162, 172) configured to receive as input a computer program (109, 150, 160, 170) of the plurality of programs (109, 150, 160, 170) written in a different programming language of the plurality of programming languages and to output a language-independent data structure representing dependencies on fields of the plurality of records created within the program, wherein, said language-independent data structure is comprised of one or more dependency constructs, wherein each dependency construct includes an indication of at least one field and a dependency related to the at least one field; a back end configured to receive language independent data structures from the plurality of front end modules (152, 162, 172) and to output dependency information for the data processing system representing dependencies created within the plurality of programs (109, 150, 160, 170), wherein the dependency information comprises field-level dependencies introduced in multiple programs (109, 150, 160, 170) of the plurality of programs (109, 150, 160, 170) such that the dependency information comprises field-level lineage across the plurality of programs (109, 150, 160, 170); a first tool configured to load the dependency information in a metadata repository; and a second tool configured to receive as input an indication of a field used by the data processing system, to access the metadata repository and to output indications of programs (109, 150, 160, 170) of the plurality of programs (109, 150, 160, 170) that introduce a dependency impacting the indicated field.