TEAM LinG DOCUMENT ENGINEERING DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES Robert J Glushko and Tim McGrath The MIT Press Cambridge, Massachusetts London, England © 2005 Massachusetts Institute of Technology All rights reserved No part of this book may be reproduced in any form by any electronic or mechanical means (including photocopying, recording, or information storage and retrieval) without permission in writing from the publisher This book was set in Bauer Bodoni and Eurostile by Andrea R Nelson Printed and bound in the United States of America Library of Congress Cataloging-in-Publication Data Glushko, Robert J Document engineering: analyzing and designing documents for business informatics and Web services / Robert J Glushko and Tim McGrath p cm Includes bibliographical references and index ISBN0-262-07261-0 (alk paper) Text processing (Computer science) Electronic data interchange Commercial documents—Data processing I McGrath, Tim II Title QA76.9.T48 G54 2005 005—dc22 2001030659 CONTENTS v CONTENTS PREFACE xv FOREWORD xxi PART I INTRODUCTION CHAPTER ONE INTRODUCTION TO DOCUMENT ENGINEERING 1.0 INTRODUCTION 1.1 A SIMPLE BUSINESS TRANSACTION? 1.2 THE EXTENDED OR VIRTUAL ENTERPRISE 1.3 IT’S ALL ABOUT EXCHANGING DOCUMENTS 1.3.1 THE DOCUMENT TYPE SPECTRUM 1.3.2 DOCUMENT EXCHANGE AS A BUILDING BLOCK 1.3.3 DOCUMENT EXCHANGE AS LOOSE COUPLING IN BUSINESS MODEL PATTERNS 1.4 UNDERSTANDING THE MEANING OF DOCUMENTS 10 11 13 14 1.4.1 INCOMPATIBLE INFORMATION MODELS 16 1.4.2 STANDARD INFORMATION MODELS 17 1.5 XML AS AN ENABLING TECHNOLOGY 1.6 USING XML-ENCODED MODELS TO DESIGN AND DRIVE APPLICATIONS 17 18 1.6.1 DOCUMENT MODELS AS INTERFACES 20 1.6.2 MODELS OF BUSINESS PROCESSES 22 1.6.3 WEB SERVICES AND SERVICE ORIENTED ARCHITECTURES 23 1.7 DOCUMENT SPECIFICATIONS AND DOCUMENT ENGINEERING 1.8 DOCUMENT ENGINEERING—A NEW AND SYNTHETIC DISCIPLINE 26 27 1.8.1 BUSINESS PROCESS ANALYSIS 28 1.8.2 TASK ANALYSIS 29 1.8.3 DOCUMENT ANALYSIS 29 1.8.4 DATA ANALYSIS 30 1.8.5 UNIFICATION IN DOCUMENT ENGINEERING 31 1.9 THE DOCUMENT ENGINEERING APPROACH 32 1.10 KEY POINTS IN CHAPTER ONE 37 vi DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES PART II FOUNDATIONS CHAPTER TWO XML FOUNDATIONS 2.0 INTRODUCTION 42 2.1 FROM HTML TO XML 43 2.1.1 THE BROWSER WAR 46 2.1.2 FROM THE WEB FOR EYES TO THE WEB FOR COMPUTERS 47 2.2 XML’S BIG IDEAS 48 2.3 CREATION OF NEW SETS OF TAGS FOR DOMAIN-SPECIFIC CONTENT 49 2.4 SEPARATION OF CONTENT AND PRESENTATION 51 2.5 DEFINITION OF DOCUMENT TYPES 53 2.5.1 DOCUMENTS AS IMPLEMENTATION MODELS 54 2.5.2 XML SCHEMAS 55 2.5.3 SCHEMA LANGUAGES 56 2.5.4 RULES THAT SCHEMA LANGUAGES CAN’T REPRESENT 61 2.6 VALIDATION 62 2.7 CONVERSION AND TRANSFORMATION 64 2.7.1 CONVERSION TO XML 64 2.7.2 TRANSFORMATION FROM XML 67 2.7.3 WHERE TO TRANSFORM 69 2.8 KEY POINTS IN CHAPTER TWO CHAPTER THREE 72 MODELS, PATTERNS, AND REUSE 3.0 INTRODUCTION 74 3.1 MODELS 75 3.2 ADAPTING THE CLASSIC MODELING 76 APPROACH TO DOCUMENTS 3.2.1 EXTERNAL VIEWS: INSTANCES OF DOCUMENT IMPLEMENTATIONS 3.2.2 PHYSICAL VIEWS: DOCUMENT IMPLEMENTATION 3.2.3 CONCEPTUAL VIEWS: DOCUMENT COMPONENT MODELS (OR SCHEMAS) AND ASSEMBLY MODELS 3.3 THE MODEL MATRIX 78 79 81 86 3.3.1 METADATA AND METAMODELS 88 3.3.2 METAMODELS FOR PROCESSES 89 CONTENTS 3.4 PATTERNS 90 3.4.1 PATTERNS IN BUSINESS 91 3.4.2 WHY BUSINESSES FOLLOW PATTERNS 92 3.4.3 FINDING PATTERNS IN THE MODEL MATRIX 94 3.4.4 USING THE MODEL MATRIX AS A FRAMEWORK 96 3.4.5 PROCESS AND DOCUMENTS: YIN AND YANG 97 3.5 KEY POINTS IN CHAPTER THREE CHAPTER FOUR 99 DESCRIBING WHAT BUSINESSES DO AND HOW THEY DO IT 4.0 INTRODUCTION 102 4.1 VIEWS OF BUSINESS ORGANIZATION 104 4.1.1 PHYSICAL VIEWS OF BUSINESS ORGANIZATION 4.1.2 CONCEPTUAL VIEWS OF BUSINESS ORGANIZATION 108 4.1.3 CONCEPTUAL VIEWS OF BUSINESS RELATIONSHIPS 111 4.2 VIEWS OF BUSINESS PROCESSES 4.2.1 PHYSICAL VIEWS OF BUSINESS PROCESSES 4.2.2 CONCEPTUAL VIEWS OF BUSINESS PROCESSES 4.3 VIEWS OF BUSINESS INFORMATION 104 119 119 120 128 4.3.1 PHYSICAL VIEWS OF BUSINESS INFORMATION 128 4.3.2 CONCEPTUAL VIEWS OF BUSINESS INFORMATION 132 4.4 VIEWS OF BUSINESS ARCHITECTURE 4.4.1 PHYSICAL VIEWS OF BUSINESS ARCHITECTURE 4.4.2 CONCEPTUAL VIEWS OF BUSINESS ARCHITECTURE 4.5 KEY POINTS IN CHAPTER FOUR 134 135 138 145 CHAPTER FIVE HOW MODELS AND PATTERNS EVOLVE 5.0 INTRODUCTION 150 5.1 THE COEVOLUTION OF TECHNOLOGY AND BUSINESS MODELS 151 5.2 FROM HIERARCHICAL TO NETWORK MODELS 152 5.3 INFORMATION ABOUT GOODS BECOMES A GOOD 156 5.4 NEW BUSINESS MODELS FOR INFORMATION GOODS 158 5.5 FROM FORECAST OR SCHEDULE–DRIVEN TO DEMAND 159 OR EVENT–DRIVEN MODELS 5.6 FROM TIGHTLY COUPLED TO LOOSELY COUPLED MODELS 161 vii viii DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES 5.7 FROM PROPRIETARY TO STANDARD MODELS 163 5.8 TOWARD MODELS WITH REUSABLE COMPONENTS 164 5.9 KEY POINTS IN CHAPTER FIVE 168 CHAPTER SIX WHEN MODELS DON’T MATCH: THE INTEROPERABILITY CHALLENGE 6.0 INTRODUCTION 172 6.1 THE INTEROPERABILITY CHALLENGE 175 6.1.1 THE INTEROPERABILITY TARGET 176 6.1.2 RECOGNIZING EQUIVALENCE 180 6.2 CONTENT CONFLICTS 181 6.3 ENCODING CONFLICTS 184 6.3.1 LANGUAGE CONFLICTS 184 6.3.2 GRAMMATICAL CONFLICTS 186 6.4 STRUCTURAL CONFLICTS 187 6.4.1 DOCUMENT ASSEMBLY CONFLICTS 188 6.4.2 COMPONENT ASSEMBLY CONFLICTS 189 6.4.3 COMPONENT GRANULARITY CONFLICTS 6.5 SEMANTIC CONFLICTS 191 193 6.5.1 FUNCTIONAL DEPENDENCY CONFLICTS 194 6.5.2 VOCABULARY CONFLICTS 195 6.5.3 CONTEXTUAL CONFLICTS 198 6.6 MOTIVATING THE DOCUMENT ENGINEERING APPROACH 200 6.7 KEY POINTS IN CHAPTER SIX 203 PART III THE DOCUMENT ENGINEERING APPROACH CHAPTER SEVEN THE DOCUMENT ENGINEERING APPROACH 7.0 INTRODUCTION 208 7.1 AN APPROACH, NOT A METHODOLOGY 208 7.1.1 MODELING METHODOLOGIES 7.2 THE DOCUMENT ENGINEERING APPROACH 210 211 7.2.1 UNIFIED APPROACH TO MODELING 212 7.2.2 ARTIFACT-FOCUSED VIEW OF MODELING 214 7.2.3 THE MODELING PHASES, TASKS, AND ARTIFACTS 215 7.2.4 IMPLEMENTING MODELS IN APPLICATIONS 219 CONTENTS 7.3 ANALYZING THE CONTEXT OF USE 221 7.3.1 REQUIREMENTS 221 7.3.2 PATTERNS OF CONTEXT 223 7.3.3 SCOPE OF CONTEXT 224 7.4 ANALYZING BUSINESS PROCESSES 224 7.5 DESIGNING BUSINESS PROCESSES 226 7.6 ANALYZING DOCUMENTS 226 7.6.1 CREATE THE DOCUMENT INVENTORY 227 7.6.2 SAMPLE THE DOCUMENT INVENTORY 228 7.7 ANALYZING DOCUMENT COMPONENTS 228 7.7.1 HARVEST THE COMPONENTS 229 7.7.2 NAME THE CONTENT COMPONENTS 231 7.7.3 CONSOLIDATE THE CANDIDATE COMPONENTS 232 7.8 ASSEMBLING DOCUMENT COMPONENTS 232 7.8.1 FORMALIZE THE COMPONENT MODEL 233 7.8.2 ASSOCIATIONS BETWEEN STRUCTURES 234 7.8.3 REFINE THE COMPONENT NAMES 234 7.9 ASSEMBLING DOCUMENT MODELS 235 7.10 IMPLEMENTING MODELS 236 7.10.1 ENCODING DOCUMENT IMPLEMENTATION MODELS 237 7.10.2 ENCODING BUSINESS PROCESS IMPLEMENTATION MODELS 238 7.11 SUMMARY OF MODELING PHASES AND ARTIFACTS 239 7.12 KEY POINTS IN CHAPTER SEVEN 241 CHAPTER EIGHT ANALYZING THE CONTEXT OF USE 8.0 INTRODUCTION 8.1 UNDERSTANDING DOCUMENT AND PROCESS REQUIREMENTS 8.1.1 STRATEGIC AND TACTICAL REQUIREMENTS 244 247 248 8.1.2 SOURCES OF REQUIREMENTS 250 8.1.3 GENERIC REQUIREMENTS 252 8.2 CONTEXT AND REQUIREMENTS 254 8.3 EXPRESSING REQUIREMENTS AS RULES 259 8.3.1 USAGE REQUIREMENTS 261 8.3.2 STRUCTURAL REQUIREMENTS 262 8.3.3 SEMANTIC REQUIREMENTS 263 8.3.4 PRESENTATION REQUIREMENTS 264 ix 690 DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES serialization: XML 15.2.1.1; Service Level Agreement: 10.7.2; satisfying 15.1.2; service oriented architecture: 1.6.3; 1.8.5; 7.1; IBM 17.2; information exchanges 9.3.1; model based 7.2.4; model based applications 15.0; organizational maturity 16.1; perspective 4.4.2.2; plug and play 5.8; plug-and-play 16.2.3.1; strategic perspective 16.1.3.3; strategic project 16.2.1; XML encoding 15.1; Services Business Language: XML vocabulary 4.4.2.2; SGML: assembly models 14.6; document analysis 13.3.1; encoding document models 15.1.1.1; generic requirement 8.1.3; schema language 2.5.3; Shakespeare, William: “Merchant of Venice” 5.3; plays of 2.4; Shapiro, Carl: “Information Rules” 4.0 (endnote 1); 5.2 (endnote 6); Ship’s Manifest: document 11.2; shipping container: qualifying names 12.1.11; shipping forms: tasks and documents 11.2.1; Shipping Note: 1.3; 1.3.3; entry point 14.4.3; incremental information trail 9.8.6; Shipping Notice: type of document 9.4.2; Shipping Schedules: 4.3.1.3; 9.8.4; INDEX Shopping Cart: form 1.1; incremental information trail 9.8.6; Silverston, Len: “Data Model Resource Book” 4.3.2; Single Administrative Document: type of document 10.4.3; single-source publishing: 1.8.3; 2.7.1; 10.4.3; applications 15.3; model based application 15.3.3; SITPRO: trade facilitator 4.1.3.4; SKICal: see Structured Knowledge Initiative; Smartdraw: modeling notations 15.1.2; SMTP: Internet EDI 5.6; SOA: see service oriented architecture; SOAP: 10.8.1; Header 14.4.3 (sidebar); Social Security Number: identifier 12.1.10; web services 4.4.1.3; software as a service: 5.4; software engineering: complementing 15.0; costs 16.2.2.5; design patterns 3.4 (endnote 11); 15.4; XML 1.6; 15.1; Software Engineering Institute: capability maturity 16.1.2; Soukup, Martin: model based architecture 16.2.2.5; sourcing: business collaboration pattern 9.8.2; spreadsheet: document 7.6.1; 11.2.1; SQL: metadata 3.3.1; SQL/DDL: 3.2.2; standard: 1.4.2; 1.7; 5.2; and reuse 5.8; benefits 16.2.2.5; 691 692 DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES de-facto 16.2.2.5; de-jure 16.2.2.5; international 2.5; licensing 16.2.2.5; open vs proprietary 5.7; organizational maturity 16.1; Standard: document name 11.3.1; Standard Metropolitan Statistical Areas: reconciliation 10.8.1; standards compliance: background 2.0; generic requirement 8.1.3; Standards Maturity Model: 16.2.2.5; standards organizations: customization 14.5.2; statement of accounts: 8.2; physical view 4.3.1; Statistical Data and Metadata Exchange: 5.8 (sidebar); Statistical Office of the European Communities: see Eurostat; statistics: 5.8 (sidebar); Stone Age: accounting 3.2.3; STP: see straight through processing; straight through processing: 1.7; 4.2.2.6; automation 16.2.2.3; generic requirement 8.1.3; requirements 8.0; trend toward 5.2; strategic perspective: 16.1.3.3; process bias 16.1.4.2; strategic projects: patterns 9.0; strategy: vs tactical projects 8.1.1; structural components: 9.2; aggregating 13.3; associations 13.4.4; document models 13.0; entry point 14.4.3; normalization 13.4.3; INDEX structural integrity: narrative documents 14.3; presentational 7.7.1; structural requirements: 8.3; 8.3.2; structural rules: document assembly 14.4.1; narrative document 13.2.1; structure: 1.4.2; 8.3.2; aggregating 7.8; and interoperability conflicts 6.0; 6.4; hierarchical 7.9; rules 7.3.1; Structured Knowledge Initiative: contextualized 11.2.3; library 14.5.2; Style Guide: document name 11.3.1; style guide: metadata 7.6.1; 11.2.1; rules 13.2.1; stylesheet: 1.8.3; styling: 2.7.2; subtractive refinement: customization 14.5.1; supply chain: 1.3.2; abstract patterns 1.7; business problems 16.2.2.2; conceptual model of business 4.1.2.1; EDI 16.2.2.1; improving 16.2.1; organizational maturity 16.1.3.2; pattern 10.5.2 (sidebar); 10.8.2; patterns 9.0; physical model of business 4.1.1.2; physical vs information 4.2.2.4; properties 10.7.2; reengineering 11.1; strategic project 8.1.1; university context 10.5.3; Supply Chain Council: SCOR 4.2.2.2; standards 4.1.3.4; 693 694 DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES Supply Chain Operations Reference Model: 4.1.1.2; development 4.1.3.4; patterns 4.2.2.2; processes 5.5; reference model 9.3.2; SCOR 4.2.2.2; standards 5.7; surrogate key: 13.4.4 (sidebar); SWIFT: patterns 13.5.3; Sydney Opera House: technology limitations 16.2.3.4; synchronization: pattern 10.5.3; syndication: 2.7.1; information aggregation pattern 4.3.1.3; of business processes 9.3.1; synonym: 12.2; syntactic requirements: 8.3; pattern 10.5.2 (sidebar); syntax: 1.4.2; 8.3.5; and interoperability conflicts 6.0; system model: 15.2.3 (endnote 17); systems analysis: 1.8; systems architecture: 4.4.1; 6.3; and business relationships 4.1.3; tables: 12.1.6; tactical perspective: 16.1.3.3; technology bias 16.1.4.1; tactical projects: vs strategic projects 8.1.1; tag: 2.1 (sidebar); 2.1.2; Talaris: composite service 4.4.2.2; task analysis: 1.8; 1.8.2; 3.4.4; and Document Engineering 7.2.1; techniques 7.3.1; tax code: analogy to methodology 7.2.2; Tax Receipt: e-forms 15.3.1; pottery 1.0; type of document 11.1; 14.0; INDEX technology: evolution 5.1; technology maturity: 16.1.3.2; Teece, David: business relationships 16.3.2.1; telecommunications: and marketplaces 5.1; telegraph: 1.0; information about goods 5.3; text encoding: markup 11.3.1; third normal form: 13.4.6; tight coupling: 1.3.3; integration 4.4.1.2; physical interfaces 15.3.4; vs loose coupling 5.6; Time to Acknowledge Acceptance: properties 10.7.2.1; Time to Acknowledge Receipt: properties 10.7.2.1; Time to Respond: properties 10.7.2.1; timeliness: generic requirement 8.1.3; Timesheets: e-forms 15.3.1; type of document 1.4.1; 1.6.1; Timmers, Paul: 8.2; To-Be model: 3.2; 7.10.2; 13.3; and business reference models 9.3.2; context dimensions 9.0; creating 10.4; implementing 7.10; pattern 10.3; 10.5; 10.5.3; process design 7.2.3; transactions 10.8.2; top-down analysis: 10.4.2; top-down approach: analysis 1.8.3; process bias 16.1.4.1; strategic perspective 16.1.3.3; top-down thinking: 17.3; 695 696 DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES Topic Maps: semantic web 15.3.7; Toyota: 4.1.3.2; traceability: of artifacts 9.3.3; product 16.2.2.2; trade association: 4.1.3.4; trade practice: 3.4.2; Tradegate: trade facilitator 4.1.3.4; trading community: 4.1.3.3; Training Manual: single-source publishing 15.3.3; type of document 14.5.2; transaction: 3.3.2; analyzing 9.4; hierarchy 1.8.1; in ebXML 9.0; in UMM 9.3.1; patterns 15.1.2.2; properties 10.7; transaction costs: Coase’s Law 5.2; transaction patterns: ebXML 9.6; transaction properties: 10.7.2; transactional documents: analysis 1.8; and content integrity 8.3.7; and schema languages 2.5.3; business rules 13.2.2; model based applications 15.0; naming 7.7.2; organizational maturity 16.1.4.1; sampling 11.3.1; transformation: 2.2; 2.4; 2.7; from XML 2.7.2; where to use 2.7.3; translation: 2.7.1; transparency: migration 15.3.1; scalability 5.6; service substitutions 10.1; INDEX Troubleshooting Guide: single-source publishing 15.3.3; type of document 14.5.2; Tucci, Christopher: 8.2; TurboTax: 7.2.2; UBL: see Universal Business Language; UCCnet: product information 5.8; UCR: see Unique Consignment Reference number; UDDI: service descriptions 10.4.3 (sidebar); web services 4.4.1.3; UI design: see user interface design; UML: see Unified Modeling Language; UMM: see UN/CEFACT Modeling Methodology; UN Layout Key: presentation integrity 8.3.4; UN/CEFACT: 3.3.2; implementation models 15.1.1; standards 4.1.3.4; UN/CEFACT Modeling Methodology: 3.3.2; 7.1.1; UN/EDIFACT: 2.7.1; 3.2.2; 4.3.1.2; code sets 12.1.8; EDI standards 4.3.1.1; implementation models 15.1.1; Message Function Code 12.1.9; Order document 6.3.1; patterns 13.5.3; shoehorning definitions 12.2.2; UN-XML 6.5.2 (sidebar); UN/SPSC: 8.2; coding system 3.4.1; Unified Modeling Language: 1.6; 7.8.1; 10.8.1; activity diagrams 7.4; class diagrams 3.2.3; 4.0; 13.2 (sidebar); 14.6; dependency diagrams 14.5.2 (endnote 6); mapping 15.1.1.2 (sidebar); metadata 3.3.1; model based architecture 16.2.2.5; model-driven architectures 15.2.1.1; modeling tool 9.3.3; notations 3.1; process metamodel 15.1.2.1; 697 698 DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES sequence diagrams 9.4.1; 9.4.1 (sidebar); use case diagrams 7.3.1; Unique Consignment Reference number: transaction patterns 9.6; United Nations: 5.8 (sidebar); United Nations Convention on Contracts for the International Sale of Goods: 9.6.1; Universal Business Language: 1.4.2; 2.3; 4.3.2; 4.3.2 (sidebar); core plus customization 14.5.2; customization 15.1.1.4; Danish government 16.2.2.1; Naming and Design Rules 15.1.1.1; order 9.0; Order schema 15.3.1; patterns 13.5.3; re-usable components 7.10.1; schema library 15.1.1.3; spreadsheet 14.6; University of California, Berkeley: “Center in a Box” 15.3.3; campuses 11.2.2; Course Approval System 10.4.4 (sidebar); Document Engineering course 17.3 (endnote 3); Event Calendar Network Project 8.0; supply chain pattern 10.5.3; unmarshalling: see deserialization; up translation: 2.7.1; UPS: 1.3.2; field stocking 10.6; information aggregation 5.3; package delivery service 4.4.2.2; US Army: content management 4.2.2.6; US Census Bureau: 8.2; US Department of Defense: Interactive Electronic Training Manuals 15.3.2; US Government: Federal Enterprise Architecture 9.3.2; Integration Acquisition Environment 16.2.2.1; US National Academy of Sciences Institute of Medicine: medication errors 16.2.2.2; US Postal Service: postal address 8.1.1; Zip codes 6.2; INDEX usability: generic requirement 8.1.3; usability engineering: 7.2.4 (sidebar); usage requirements: 8.3.1; use case: 1.8.2; and task analysis 7.2.1; user interface: applications 15.3; design tasks 15.3.1.1; model based 15.3.1.3; user interface design: 7.2.3 (sidebar); user-centered: interface design 7.2.3 (sidebar); validating parser: 2.6; validation: 2.6; one of XML’s big ideas 2.2; value chain: 4.2.2.4; supply chain 4.2.2.6; value-added services: 4.1.2.2; van der Vlist, Erik: “XML Schema” 15.1.1.1; Varian, Hal: “Information Rules” 4.0 (endnote 1); 5.2 (endnote 6); real-time business model 5.5 (endnote 25); vendor managed inventory: 4.2.2.5; process pattern 5.5; vendors: products 15.0; software 16.2.2.5; vertical integration: 4.1.3; virtual business builder: 10.4.3 (sidebar); virtual enterprise: 1.0; evolution 5.2; patterns 9.0; vision 6.0; Visa: 1.1; 1.3.2; payment service 4.4.2.2; Visio: modeling notations 15.1.2; Vitale, Michael: atomic business patterns 4.4.2; VMI: see vendor managed inventory; vocabulary: 2.1.2; 2.3; 2.5.1; 6.5.2; 699 700 DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES voice mode: 4.1.3.2; technologies 16.2.3.1; W3C: see World Wide Web Consortium; Wal-Mart: 1.8.3; document 11.1; document automation 1.8.3; Internet EDI 5.6; RFID 5.1; Walmsley, Priscilla: “Definitive XML Schema” 15.1.1.1; Waybill: entry point 14.4.3; web browsers: see browsers; Web EDI: 5.6; Web for computers: 2.1.2; Web for eyes: 2.1.2; Web Ontology Language: semantic web 15.3.7; web page: document 7.6.1; patterns 13.5.3; web services: 1.0; 1.3.2; 1.5; 1.6.3; and SOA 4.4.2.2; application 9.3.3; BPEL 15.1.2.2; business case 16.2.1; deploying 8.1.1; document exchange 4.1.3; economic impact 5.2; Event Calendar project 16.1.4.2; explicit models 15.3.1.3; history of idea 1.1 (endnote 3); 4.4.1.3 (endnote 62); hosted drop shipment 10.6; hype 7.3.1; information exchanges 9.3.1; interoperability 6.6; model based 7.2.4; model based application 15.0; overview 4.4.1.3; plug and play 5.8; responsiveness 10.7.2; semantic 15.3; 15.3.7; INDEX standards 16.2.2.5; 5.7; XML 15.1; Web Services Description Language: 4.4.1.3; Web Services Industry Councils: 4.1.3.3; wedding invitation: type of document 12.1.4; Weill, Peter: atomic business patterns 4.4.2; well-formed: 2.6; Wellpoint Health Networks: document automation 16.2.2.2; Williamson, Oliver: business organization 5.2; Wittenstein, Ludwig: intension and extension 12.1.9 (sidebar); word processing files: document 7.6.1; workflow: business collaboration pattern 9.8.6; worksheets: 7.4; 9.3.3; analysis 7.3.1; modeling notations 15.1.2; World Bank: 5.8 (sidebar); World Wide Web Consortium: 2.1.1; 2.5.3; 2.5.4; 2.7.2; recommendations 5.7; semantic web 12.1.11 (sidebar); XML Schema 15.1.1 (sidebar); WorldCom: 4.2.2.6; WSDL: see Web Services Description Language; X12: see ANSI ASC X12; XAML: vocabulary 15.3.1.1; XCBL: 4.3.1.2; schema library 15.1.1.3; XForms: alternatives 15.3.1.1; e-forms 15.3.1 (sidebar); mapping 15.3.1.2; XHTML: 2.3; e-form applications 15.3.1 (sidebar); physical interface model 15.3.1; transforming 15.3.3; 701 702 DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES XML: 1.0; 1.5; and conversion 2.7.1; and document automation/STP 4.2.2.6; and document implementation models 7.10.1; and document models 2.5.1; and naming 6.5.2 (sidebar); and transformation 2.7; 2.7.2; and validation 2.6; and web services 4.4.1.3; as standard 5.7; big ideas 2.2; capability 10.7.1; compared to HTML 2.3; document automation 16.2.2.1; document exchange 4.1.3; e-forms 15.3.1 (sidebar); editors 15.1.1.2 (sidebar); encoding 15.0; in model based applications 7.10; metadata 14.6; modeling approaches 13.3.1; naming and design rules 6.3.2; narrative components 12.1.2; not self describing 2.5.2; overview 2.0; process model 15.1.2.1; separating content from presentation 2.4; syntax 2.1 (sidebar); system architectures 4.4.1.1; web services 15.3.1.3; XML applications: see XML vocabularies; XML Common Business Library: see XCBL; XML Schema: 2.5.3; XML schema: see schema; XML Schema: and UBL 4.3.2 (sidebar); as metamodel 3.3.1; customization 15.1.1.4; datatypes 15.3.1; encoding rules 15.1.1.1; implementation models 15.1.1; mapping 15.1.1.2 (sidebar); metadata 14.6; INDEX style 2.5.3 (endnote 14); W3C 15.1.1 (sidebar); XML vocabularies: 2.3; domain-specific 15.3.1.1; encoding process models 15.1.2; patterns 7.10.1; proliferation of 4.3.1.2; qualifying values 12.1.8; syntactic requirements 8.3.5; user interface modeling 13.3.1.2 (sidebar); XPath: 2.5.4; 2.7.2; BPEL 15.1.2.2; resolving encoding conflicts 6.3.2; XSD: see XML Schema; XSL FO: see Extensible Stylesheet Language for Formatting Objects; XSLT: see Extensible Stylesheet Language for Transformation; XUL: rendering 15.3.1.1; Yahoo: ontologies 12.1.11 (sidebar); Yin and Yang: in Document Engineering 3.0; 7.0; zipcode: not a code 12.1.11; zombie systems: risks 16.2.3.2; 703 ... IN DOCUMENT ENGINEERING 31 1.9 THE DOCUMENT ENGINEERING APPROACH 32 1.10 KEY POINTS IN CHAPTER ONE 37 vi DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES. .. Robert J Document engineering: analyzing and designing documents for business informatics and Web services / Robert J Glushko and Tim McGrath p cm Includes bibliographical references and index.. .DOCUMENT ENGINEERING DOCUMENT ENGINEERING ANALYZING AND DESIGNING DOCUMENTS FOR BUSINESS INFORMATICS & WEB SERVICES Robert J Glushko and Tim McGrath The MIT Press