Administrivia
Professor Robert J. Glushko
Email: glushko@ischool.berkeley.edu
Website: http://www.ischool.berkeley.edu/~glushko
Office number: +1-510-6432754
Office Hours: Monday 4:00pm-5:00pm Wednesday 11:00am-12:00pm 313 South Hall
TA Zach Gillen
Email: zgillen@ischool.berkeley.edu
Course Description
This course introduces the discipline of Document Engineering: specifying, designing, and deploying electronic documents and information repositories that enable document-centric or information-intensive applications. These applications include web services, information supply chains, single-source publishing, composite applications/virtual enterprises/portals, and so on. Course topics include developing requirements, analyzing existing documents and information sources, conceptual modeling, identifying reusable semantic components, modeling business processes and user interactions, applying patterns to make models more robust, representing models using XML schemas, and using XML models to implement and drive applications. The syllabus contains over 20 short case study examples from different industries, with special emphasis on business-to-business, healthcare and medical informatics, and e-government.
- There are 5 assignments spread out during the semester. These short assignments are designed to develop and reinforce practical skills applied by business analysts and consultants in information-intensive industries.
- Small-team projects on topics chosen by students synthesize the concepts and skills of the course during the second half of the semester
- There is no final exam or midterm
Course Information
Course Dates: January 23 to May 12, 2007
Lecture Schedule: Monday Wednesday 9:00am-10:30am in 202 South Hall
Units: 3
Grading Option: Letter Grade only
Course Text
Required
Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services, Robert J. Glushko and Tim McGrath. MIT Press, 2005.
Course Work
May 7 :
January 23 : Wednesday
1. Course Overview – Key Concepts of Document Engineering and Information Architecture
Introducing the key concepts and challenges of Document Engineering and Information architecture using recent news stories from commercial/for-profit and governmental/non-profit sectors, and from both the narrative and transactional end of the Document Type Spectrum; overview of the course syllabus; course administrivia.
Required Readings
Chapter 1 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Resources
January 28 : Monday
2. Motivation and Strategies for DE and IA; Analyzing Case Studies
The business case for DE and IA; using the eight letters of DOCUMENT as a mnemonic for systematically analyzing eight aspects or dimensions of case studies.
Required Readings
Chapter 16 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 554-571]
"Tailing Virulent Veggies" Jane Zhang [Online]
Wall Street Journal (March 13, 2007)
"More Clicks at the Bricks" Nanette Byrnes [Online]
Business Week (December 6, 2007)
"Landstuhl to use Electronic Medical Records" Kelly Kennedy [Online]
Army Times (January 16, 2008)
"Why XForms", Elliotte Rusty Harold [Online] (October 31, 2006)
"Accelerating RosettaNet" Philip Burgert [Online]
E-Commerce World (November 2001)
"Department of Homeland Security's Efforts Promise to Be the Biggest Change Management Job of All Time" Todd Datz [Online]
CIO (December 2002)
Resources
January 30 : Wednesday
3. XML Foundations; Introduction to Modeling
DE and IA have nothing inherent to do with XML, but XML is useful as a format for encoding information and process models; most of this lecture will be an introduction to modeling: methods, metamodels, tools, notations, and artifacts.
Required Readings
Chapter 2 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Chapter 15 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 491-501]
Chapter 3 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 73-86]
Resources
February 4 : Monday
Business-to-business processes and relationships are strongly shaped by document engineering and information architecture issues. We take a more detailed look into B2B here.
Required Readings
"Beyond CPFR" Paul Demery [Online]
Internet Retailer (February 2006)
"Paperless Trading: Benefits to APEC", Australian Department of Foreign Affairs and Trade [Online] (2001)
"Adoption of UBL in Denmark – business cases and experiences" M. Brun, J. Brown and R. Lohde [Online]
XTech (2005)
Resources
February 6 : Wednesday
5. Case Studies: Healthcare & Medical Informatics
Healthcare and medical informatics share many of the same goals and challenges as B2B DE and IA efforts, but they also differ in key ways.
Required Readings
"HIT and MIS: Implications of Health Information Technology and Medical Information Systems" P. Goldschmidt [Online, 69-74]
Communications of the ACM (October 2005)
"Electronic Health Records: Just around the Corner? Or over the Cliff?" R. Baron, E. Fabens, M. Schiffman and E. Wolf [Online, 222 - 226]
Annals of Internal Medicine 143 (August 2005)
"Cracks in the Pharmaceutical Supply Chain" Susannah Patton [Online]
CIO (January 15, 2006)
Resources
February 11 : Monday
6. The Document Engineering Approach
An overview of Document Engineering, illustrating different analysis and modeling activities and issues using the "Document Engineering in the News" stories analyzed by students in Assignment 1. Each of the major activities will be covered in depth in subsequent lectures.
Required Readings
Chapter 7 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Resources
Due on May 12
February 13 : Wednesday
7. Business Patterns; Models of Business Organization [1]
Patterns are models that are sufficiently general, adaptable, and worthy of imitation. We'll introduce the idea of business patterns of different levels of abstraction and granularity and the "Model Matrix" that organizes them in the Document Engineering methodology. We'll also discuss some other frameworks for reusing business model and business architecture patterns.
Required Readings
Chapter 3 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 86-100]
Do Some Business Models Perform Better than Others?, Peter Weill, Thomas W. Malone, Victoria T. D’Urso, George Herman and Stephanie Woerner [Online]
"Global Disaggregation of Information-Intensive Services" Uday M. Apte and Richard O. Mason [Online, pp. 1250-1262]
Management Science 41(7) (July 1995)
Resources
February 20 : Wednesday
9. Models of Business Organization [2]
More on business organization patterns, within and between firms (e.g., component business maps, "buy side" vs "sell side," supply chains).
Required Readings
Chapter 4 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 102-118]
"Marketplace and technology standards for B2B e-commerce: Progress, challenges, and the state of the art." Conan Albrecht, Douglas Dean, and James Hansen [Online, pages 865-875]
Information & Management 42 (2005)
"Systemic Assessment of SCOR for Modeling Supply Chains." Vijay Kasi [Online]
Proceedings of the 38th Hawaii International Conference on System Sciences (2005)
Resources
February 25 : Monday
10. Models of Business Processes
A more granular look at business organization in terms of processes and information exchanges; some key resources of reusable patterns in the MIT Process Handbook and RosettaNet
Required Readings
Chapter 4 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 119-127]
"What is in the Process Handbook?" George A. Herman and Thomas W. Malone [Online, pages 221-231]
Organizing Business Knowledge (September 2003)
MIT Process Handbook [Online]
RosettaNet PIP Directory [Online]
Resources
February 27 : Wednesday
11. Models of Business Information [1]
Conceptual and physical models of business information; XML vocabularies, "XMLification"of other formats
Required Readings
Chapter 4 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 128-147]
Chapter 6 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Resources
March 3 : Monday
12. Models of Business Information [2]
A close look at integration and interoperability issues in B2B and eHealthcare domains.
Required Readings
"Interoperability Costs in the US Automotive Supply Chain" Smita Brunnermeier and Sheila Martin [Online, 71-82]
Supply Chain Management 7(2) (2002)
"Operation Clean Data" Malcolm Wheatley [Online]
CIO (July 2004)
"Key Issues of Technical Interoperability Solutions in eHealth and the RIDE Project" Asuman Dogac, Tuncay Namli, Alper Okcan, Gokce Laleci, Yildiray Kabak and Marco Eichelberg. [Online]
Resources
Due on March 12
March 5 : Wednesday
13. How Models and Patterns Evolve; Emerging Technologies
Principles and themes about the co-evolution of business patterns and information technology; Web services and service-oriented architecture; some novel applications in healthcare enabled by mobile technology and personal portable data storage
Required Readings
Chapter 5 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
"E-Government Architecture in Ireland" Sean McGrath and Fergal Murray [Online]
XML 2004 Conference
"Mobile Telemedicine System for Home Care and Patient Monitoring" M. V. M. Figeuredo and J. S. Dias [Online]
Proceedings of the 26th Annual Conference of the IEEE EMBS (September 2004)
"Redefining the Patient Record Paradigm" MedicAlert Foundation [Online]
Whitepaper (January 2005)
Resources
March 10 : Monday
Identifying and describing the context of a DE and IA effort; once this context has been defined, any constraints on possible goals or solutions that must be satisfied are the requirements; generic requirements in information-intensive contexts
Required Readings
Chapter 8 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
"Habits of Effective Analysts" Karl Wiegers [Online]
Software Development (1 October 2000)
"When "It Doesn't Matter" Means "It Matters"" B. Tommie Usdin [Online]
Extreme Markup Languages 2002
Resources
March 12 : Wednesday
15. Document Anthropology and Archeology
Finding relevant documents and information sources is inherently iterative: a document may refer or link to other documents, or to people, who can refer to other people or to other documents; using process patterns to locate informaiton artifacts and sources; organizational issues
Required Readings
Chapter 11 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Chapter 16 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook, 540-554]
Two Case Studies (pages 33-49) [Handout]
The Myth of the Paperless Office, A. Sellen and R. Harper. (2002)
Resources
March 17 : Monday
March 31 : Monday
20. Business Process Analysis [2]
Control and logic patterns; transaction patterns; business signals; the Business Process Modeling Notation standard
Required Readings
"BPMN and the Business Process Expert, Part 2: Mastering the Notation", Bruce Silver [Online] (November 5, 2007)
"BPMN and the Business Process Expert, Part 3: The Art of Process Modeling", Bruce Silver [Online] (November 19, 2007)
Resources
April 2 : Wednesday
21. Business Process Analysis [3]
Two additional process modeling approaches: service blueprinting, which focuses on the "customer encounters," and operational specification, which focuses on the "business artifacts" and their transformations
Required Readings
"Service Blueprinting: A Practical Technique for Service Innovation" M. J. Bitner, A. Ostrom, and F. Morgan [Online]
California Management Review (in press, 2008)
"Business Artifacts: An Approch to Operational Specification." A. Nigam and N. Caswell [Online]
IBM Systems Journal 42(3) (2003)
Resources
April 7 : Monday
22. Business Process Design [1]
Adopting, adapting, inventing, and implementing patterns to design processes; using the Design Structure Matrix to improve processes
Required Readings
Chapter 10 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Resources
Due on April 15
April 9 : Wednesday
23. Business Process Design [2]
Case studies of innovative process design; personalization patterns
Required Readings
"RosettaNet for Intel’s Trading Entity Automation" J. Cartwright, J. Hahn-Steichen, J. He and T. Miller [Online]
Intel Technology Journal (August 2005)
"Combining RFID Technology and Business Intelligence for Supply Chain Optimization – Scenarios for Retail Logistics." Henning Baars, Hans-Georg Kemper, Heiner Lasi, and Marc Siegel [Online]
Proceedings of the 41st Hawaii International Conference on System Sciences (January 2008)
"Personalization Technologies: A Process-Oriented Perspective" Adomavicius, G. & Tuzhulin, A [Online]
Communications of the ACM 48(10) (October 2005.)
Resources
April 14 : Monday
Analyzing information sources and documents to identify their significant "information components" and their attributes; separating content, structure, and presentation; relationships among content components
Required Readings
Chapter 12 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Resources
April 15 : Tuesday
April 16 : Wednesday
Systematic variation in document types across the Document Type Spectrum; harvesting components; defining what a component means
Required Readings
"Model-driven Application Design for a Campus Calendar Network (Sections 1-3.2.3.2.2)" Alison Bloodworth and Robert Glushko [Online]
XML 2004 Conference
Recommended Readings
Overview and The Sylvia Data Model [Online]
The Syllabus Viewing Application, Lisa De Larios-Heiman and Carolyn Cracraft. ()
Resources
Due on April 29
April 21 : Monday
Case studies of document analysis in different domains.
Required Readings
"Common Data Model for Design Document Exchange in Business-to-Business Networks" Katrine Jokinen, Jukka Borgman and Reijo Sulonen [Online]
Proceedings of the 38th Hawaii International Conference on System Sciences - 2005
"XML in the Pharmaceutical Industry: Structured Product Labeling" K. Thomas [Online]
XML 2004 Conference (2004)
Resources
April 23 : Wednesday
Consolidating harvested components to achieve semantic clarity and precision; primitive and aggregate components; designing for component reuse
Required Readings
Chapter 13 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
"Creating and Maintaining Large Families of Related Schemas" Anthony B. Coates [Online]
XML 2005 Conference
Resources
April 28 : Monday
28. Assembling Document Models
Transforming a component model - a relational view of semantic building blocks - into a hierarchical document model to meet the information exchange requirements of some context; formal and heuristic techniques
Required Readings
Chapter 14 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
Resources
April 29 : Tuesday
May 5 : Monday
30. Implementing Models in Applications [1]
Creating information and process models requires significant investment -- now we can use those models to implement applicationts that enforce the business rules and constraints embodied in those models
Required Readings
Chapter 15 of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services [Textbook]
"Business Rules in User Interfaces" Kamlesh Pandey [Online]
Business Rules Journal 8(12) (December 2007)
Resources
last updated on 2008-05-10 by RJG