Here's the scenario.
A long while back, the Powers That Be decided that a particular module should be called Widget Authorizations. As such, a whole lot of stuff was named after that:
- Database tables - AuthorizationTypes, AuthorizationFlows, etc.
- Database columns - Authorization_Id, Authorized_User, etc.
- Classes - AuthorizationBroker, IAuthorizable, etc.
- Files/Folders - \Admin\Authorizations\, CompleteAuthorizationForm.aspx, etc.
- UI Elements - labels, helper text, etc
- Printed Material - manual, brochers, etc.
Now, the same Powers That Be have decided that "Widget Authorizations" is a poor name and needs to be renamed to "Approval Sprokets" in the next release. So, my question is, how far do you go in renaming things beyond the Printed Material and UI Elements?
Is it worth the trouble/risk to change the code and back-end stuff? Will we really suffer that much if, to us, it's called WidgetAuthorizations but to the business/users it's ApprovalSprockets?