It is common for business analysts to create business requirement documents to detail the business process and rules that underpin how the system needs to behave. It is also common for solution architects to create technical requirement documents to detail the technology solution that define the way different technology layers, systems and components interact to deliver the working system.
With the prevalence of UX design processes and methods, why is it not common or necessary for UX designers to create user requirement documents to detail the high level user mental model and behaviours that define the interaction and behaviour that the system needs to have with the users to provide the optimal user experience? Are there other types of documentation or names that are used for this type of information presented and used in project design/planning?
To clarify the question, the document should be used to communicate with people within both the business and technology sections of the organisation, and also allows it to be translated into more detailed UX design requirements that form the basis of in-depth research, design and testing activities.