Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your email address or mobile phone number.

Qty:1
  • List Price: $23.00
  • Save: $8.32 (36%)
FREE Shipping on orders over $35.
Usually ships within 2 to 4 weeks.
Ships from and sold by Amazon.com. Gift-wrap available.
Document Engineering: Ana... has been added to your Cart
+ $3.99 shipping
Used: Good | Details
Condition: Used: Good
Comment: This book has a light amount of wear to the pages, cover and binding. Blue Cloud Books. Hot deals from the land of the sun.
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services Paperback – January 25, 2008

4.1 out of 5 stars 7 customer reviews

See all 4 formats and editions Hide other formats and editions
Price
New from Used from
Paperback
"Please retry"
$14.68
$5.34 $4.70
Free Two-Day Shipping for College Students with Amazon Student Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student


Save Up to 90% on Textbooks Textbooks
$14.68 FREE Shipping on orders over $35. Usually ships within 2 to 4 weeks. Ships from and sold by Amazon.com. Gift-wrap available.

Editorial Reviews

Review

"Document Engineering provides a thorough, common-sense approach to designing the documents used in service-oriented architectures. Well written and packed with examples, it is timely reading for architects, developers, and managers." Ronald Bourret, author of XML and Databases



This manifesto for the document engineering revolution gives you the what the why and the how of automating your business processes with XML leading to greater cost savings higher quality and more flexibility.

(Hal Varian, Haas School of Business and Department of Economics, University of California Berkeley)

"*Document Engineering* provides a thorough, common-sense approach to designing the documents used in service-oriented architectures. Well written and packed with examples, it is timely reading for architects, developers, and managers."--Ronald Bourret, author of "XML and Databases"

About the Author

Robert J. Glushko is Adjunct Full Professor in the School of Information at the University of California, Berkeley. He is the coauthor (with Tim McGrath) of Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services (MIT Press).

Tim McGrath is an independent consultant and is Chair of the Universal Business Language Library Content Subcommittee. With collaborator Robert J. Glushko, he maintains the http://docordie.blogspot.com/ Doc or Die blog.
NO_CONTENT_IN_FEATURE


Product Details

  • Paperback: 728 pages
  • Publisher: The MIT Press (January 25, 2008)
  • Language: English
  • ISBN-10: 0262572451
  • ISBN-13: 978-0262572453
  • Product Dimensions: 7 x 1 x 9 inches
  • Shipping Weight: 2.1 pounds (View shipping rates and policies)
  • Average Customer Review: 4.1 out of 5 stars  See all reviews (7 customer reviews)
  • Amazon Best Sellers Rank: #950,766 in Books (See Top 100 in Books)

More About the Authors

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Top Customer Reviews

Format: Hardcover
At the end of the day, business success comes down to three things: a product, the market, and the business processes. The business processes consist of people, tools and workflow. You can have a great product in a great market but if you have bad business processes...you can forget about it. Many organizations have tried to implement Six Sigma to ensure highly effective business processes. The key to six sigma is data. Data tells you how effective your processes are. For example, data will tell you things like: how many parts per million are defective, how many invoices per million were inaccurate, how many orders shipped late, how long it takes to execute an order once a contract is signed, how long a customer support rep spent on the phone, etc......Once you have the data, evaluating the problem and recommeding a solution is easy. The hard part however is getting the data. You can either collect the data manually over time or if you have the infrastructure you can collect it electronically through software. Unfortunately if you have to collect the data manually, it takes a long time, effort and money. If you collect data electronically it enables no additional time and provides real time visibility and the ability to implement positive changes on the fly. So how do you go from a manual data collection process to an automated data collection process? That's what this book, Document Engineering, will help you figure out. I have owned this book for about 2 months and it has been on my desk since. I continuously refer to it for insights on how to develop a clear plan on how to implement a data collection infrastructure that will help to more effectively manage business processes.
1 Comment 10 of 10 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
I really should like this book - it's highly related to what I do and I love my job. There were a number of good nuggets of information and references that I will find useful however I found I had a great deal of trouble reading the actual text - I found it boring. The large print, gaps between the lines and the stretched filled spacing of each line made it difficult to quickly scan paragraphs and grasp the gist of what was being said, even when rereading. The grid diagrams were also problematic - they all had the same look - there was little that was memorable about them. The authors also often used round about wording where more direct statements would have been clearer.

As an experiment I typed a couple of random paragraphs from the text and found that they made a lot more sense. I also showed the text around to some of my co-workers and got the same reactions. Given the title of the book it is somewhat ironic that it should have this kind of a problem, but the book deals with principles for the automated transformation of content, not effective presentation style.

Better editing would have made a better book.
Comment 5 of 5 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Hardcover
Document Engineering is a practical exploration of the role documents play in the nexus of contracts that drive modern businesses. The interdisciplinary approach put forward here, taking document engineering out of the realm of pure software engineering, is eye opening and provides some real insight into what it takes to make Service Oriented Architectures work in the real world. This is an absolute must read book for anyone seriously considering developing an XML based document integration strategy.
Comment 3 of 3 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Hardcover
The book is a refreshingly understandable approach to explaining Service Oriented Architecture, Web Services and the Semantic Web. Other texts often drown the reader in hugely verbose XML examples. But here, the authors achieve clarity in discussing the essence of the above concepts. The XML snippets are clear, without being overly long.

You can also see why interoperability issues might inevitably arise in a loosely coupled Web Services environment. Often due to differing semantic meanings attached to the same fields in a common document structure. The book touches upon hard problems of ontologies and how the different meanings might be accomodated in a realistic deployment of distributed Web Services.
Comment 2 of 2 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse

What Other Items Do Customers Buy After Viewing This Item?

Want to discover more products? Check out this page to see more: analyzing vocabulary