When creating documentation for a project, I understand some things are completely necessary, however I was asked to provide a brief description for every query in a system I built. That's over 100 queries.
If unfamiliar with queries (SQL), it is language used to interact with databases. Update/delete/retrive data/add records, etc. It can be tedious and quite convoluted.
The business' case is that it would assist in cleaning up the system of unused/repeated queries.
They are all so specific to a particular process/report that if a Developer came into the system and looked around, they would be able to tell what they do due to their naming conventions and the clarity in the scenarios they are used.
I don't understand why a business user would need this documentation? I am trying to not act like I am just being lazy.
It's not like they should have the ability to go in and delete a query if they don't think it's doing something properly.
I have never heard of documentation being that detailed. To me, it's the same thing as going through each line of code and telling the user what it does. It seems like a very ignorant request, probably with good intentions, but still ignorant.
What can I say back to the user? Or is this a reasonable request?