Document engineering

Document engineering is a document-centric synthesis of complementary ideas from information and systems analysis, electronic publishing, business process analysis, and business informatics to ensure that the documents and processes make sense to the people and applications that need them. Originating from research published by Robert J. Glushko and Tim McGrath, document engineering attempts to unify these different analysis and modeling perspectives and helps to specify, design, and implement documents and the processes that create and consume them.

In the context of document engineering, document generally refers to ordered pieces of information used by computer applications or web services rather than directly by people. It has particular relevance in the areas of XML vocabulary design. The principles of document engineering were applied to the development of the OASIS Universal Business Language.

From 2003 to 2007, the University of California at Berkeley operated a research center for document engineering, which has been subsumed by its program in Information and Service Design.^[1]

The conventional discipline that most resembles document engineering is probably business informatics. However, document engineering emphasizes the need for conceptual modeling of documents and processes at an implementable granularity.

Alternative definitions

Document engineering may also refer to the design of a document to meet very specific requirements for clarity or embodiment of rules (e.g., ensuring that regulations or a contract are drafted precisely). This usage, coming from contexts of legal or technical writing, focuses on a specific, previously existing instance of a document.

The ACM Symposium on Document Engineering^[2] is a yearly conference of computer scientists interested in text or document processing.

References

1. ^ http://cde.berkeley.edu/
2. ^ http://www.documentengineering.org/

External links

• Document Engineering,MIT Press.
• Document Engineering, O'Reilly Digital Blogs