Copyright 2006 Robert J. Glushko
Take Home Final Exam
Final Project Presentations
10 Things to Remember About Document Engineering
Yardi
Kawamoto
Cobb / Kartavenko / Meyer / Reinhart
Hankin / O'Brien
Collett / Ferrario / Tabas
Document Engineering isn't about XML; it's about D-O-C-U-M-E-N-T
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 (e.g., trading communities, standards bodies)
N -- the needs (business case) driving the enterprise(s)
T -- technology constraints and opportunities

Narrative and Transactional Documents are on a Continuum

Documents and Processes are Yin and Yang


Overlapping Information Is the Glue of Processes

Friends don't let Friends Model Alone

"The expense of resolving ambiguous business terms over and over on a daily basis pales in comparison with the expense of NOT realizing that there is an ambiguity in the term"

Patterns Rule! Reuse when you can, and Follow the Golden Rule when you can't

Balance Archeology and Anthropology
Inventory / sample / harvest / consolidate / refine / assemble / encode
Analyzing the Context -- UML use case diagrams
Analyzing/Designing Business Processes -- Worksheets, UML Activity and Sequence Diagrams
Applying Patterns to Business Processes -- Document Checklist
Analyzing Documents -- Document Inventory
Analyzing Document Components -- Consolidated Table of Content Components
Assembling Document Components -- UML Class Diagram
Assembling Document Models -- UML Class Diagram or Spreadsheet
Implementing Models -- XML Schemas
Preserve your Modeling Investments in your Implementations


This is not the end of Document Engineering