Explain the answer to this question: "How does my design maintain low coupling?"

Hint: How to maintain low coupling?

Consider a scenario where you are asked to run the program but given a completely different record structure, e$.$g$.$ what would you have to change in your code if you have to sort this file $($assuming you would have to order it by field number $3)$:

$0,2861$ Lauzon Rd$,$Little River Golf Course,$-82\mathrm{.}928171415500003,42\mathrm{.}306079492199999$

$1,455$ Kennedy Dr W$,$Roseland Golf and Curling Club,$-83\mathrm{.}006129491199999,42\mathrm{.}251240488400001$

$2,3215$ Forest Glade Dr$,$Forest Glade Community Centre,$-82\mathrm{.}915715771300000,42\mathrm{.}303155757299997$

$3,5200$ Matchette Rd$,$Ojibway Nature Centre,$-83\mathrm{.}075720068600006,42\mathrm{.}264275746999999$

Note that it would be useful to design the code so that it can read any text file $($assuming it maintains the same comma$-$delimited records$)$ and sort it by any specified field. This would require additional design characteristics that we like you to think about.

HINT: Consider a template or a configuration file that is required to accompany the input text file. Now put the overall design together justifying this agile ability of this software.

Solve the following:

a$)$ The answer to the question "How does my design maintain low coupling?".

b$)$ The revised UML design $($revised class diagram only$)$

c$)$ The answer to the question "How does my design maintain low coupling?" in reference to your revised design