An interesting defintion of DOCUMENT

I found this definition for DOCUMENT while i was searching for some related content.

D - Data types and Document types,
O - Organizational processes,
C - Context ( types of products or services, industry, geography, regulatory considerations),
U - User types and special user requirements,
M - Models, patterns, or standards that apply,
E - Enterprises and eco systems (ex, Trading communities, standards bodies),
N - Needs (Business case) during the enterprise(s),
T - Technology constraints and opportunities.

This acronym mentions all the related information that we need when we are working on Documents. Simply document centric. Since forms move around the organizations as a part of some business processes, the document process starts with handling several document types, their process models, and the context in which they are working, the kinds of users connected with the documents, and the respective models (document model, like process based, state based, etc).
I got this while i was searching for content related to document modeling. I am doing Masters thesis on document modeling. Many organizations still depends on documents for their daily processes. In this scenario a person submits a document to one authority and that document will move around the organization to get processed, by means of either approving that document, or forwarding, or just receiving. This involves a case where the document initiators may not know to whom to submit the document and how the document will route in the business network. This motivated me to work on this problem. We were approaching this problem by focusing entirely on document (other approaches are on workflow, where some implementations exist), its state, and the routing info( which is adaptive according to the changing rules of an organization). we were presently working on the formulation of document schema for this kind of problems.