Dependency Between Data and Programs
Generally speaking, creating an application that handles files involves a number of operations[1], such as :
Record structuring: defining fields, their types and order
Choice of organization: sequential, indexed sequential, direct, etc.
Choice of media: hard disk, removable disk, etc.
Note :
This means that the data contained in the files is directly associated with the programs that use them, by means of a description contained in the programs themselves.
Example :
If you have to set up a loan management application in which it is assumed that a borrower can borrow up to three (3) books, you need to create a file with approximately the structure shown in the figure below.

Programs that use such a file define its structure within their own code.
If this file is used by programs P1, P2, and P3, and a modification is needed to meet the requirements of P2 (for example, to include the borrower's age), then P1 and P3 will also need to be updated. This is because all the programs access the file in the same way, even if they don't require the same information.
In the same way, a change in the organization of the file on disk for the needs of a Pi program (moving, for example, from a sequential organization to a direct organization in order to optimize Pi's access times) will force the other programs to take this change into account and, in a way, to follow Pi, even if they don't really need this type of organization.
In the same way, a reorganization of the record's fields (changing the order of the fields within the record) will lead to a modification in the programs and a reconstruction of the file on the medium.
