I think your statements are the nub of the issue - as a developer, the view is of how the software is designed and operates internally. Users don't (normally) h

I think your statements are the nub of the issue - as a developer, the view is of how the software is designed and operates internally. Users don't (normally) have that same view. This is why 'Use Cases' and/or 'User Stories' can help cross the divide between what the user needs the software to do, and the technical details of how it may do it internally. Of course, Use Cases or User Stories don't easily capture the UI/UX aspects, which would come from a broader level of business modelling in the application/user domain.