Business Engineering With Object Technology

Rating:
Summary: The future of the software creation
Review: A fantastic EASY book (for: programmers, managers and users) to understand the great potential of the object paradigm to fill the gap between technical and business people. I think this is the future of computer development.

Rating:
Summary: Finally... a readable introduction to Object Oriented Design
Review: Dr. Taylor builds a clear case for business process oriented systems development and he can explain what that is, which is unique for IT books. I use this book to help inform key executives about how business objects really work.

Rating:
Summary: Clear, Concise, Transformational
Review: Pulls you through quite a thought process. Great step-by-step manual. The diagrams and margin summaries would make several classic PowerPoint presentations.

Rating:
Summary: Easy to read, but not up-to-date, and a bit naive
Review: The author presents an enthusiastic view of applying some ideas from object-oriented programming to business modeling. In doing so, he makes a number of unsubstantiated, if not false, claims such as "... object technology reflects fundamental cognitive processes" or "... directly supports the way managers think about their business". Compare this to the sobering statement of Jacobsen, one of the founders of the standard model of object orientation (the "UML"), who said that "it is bizarre to apply the way of thinking that governs computer systems to business processes". Clearly, the software engineering concepts brought up by object technology do neither reflect the way the business world is like nor do they reflect the way we think about it. Another weakness of the book is its age. In a world of rapid changes through scientific and technological progress, it is not suprising that the book is not up-to-date. Today, the Unified Modeling Language (UML) defines the standard model of object orientation. Unfortunately, the book is both incomplete and inconsistent with the UML. For instance, it does not discuss the important concept of associations, it calls attributes "variables", and it uses the terms "collections" and "composition" in a way that is incompatible with the UML.

Rating:
Summary: Easy to read, but not up-to-date, and a bit naive
Review: The author presents an enthusiastic view of applying some ideas from object-oriented programming to business modeling. In doing so, he makes a number of unsubstantiated, if not false, claims such as "... object technology reflects fundamental cognitive processes" or "... directly supports the way managers think about their business". Compare this to the sobering statement of Jacobsen, one of the founders of the standard model of object orientation (the "UML"), who said that "it is bizarre to apply the way of thinking that governs computer systems to business processes". Clearly, the software engineering concepts brought up by object technology do neither reflect the way the business world is like nor do they reflect the way we think about it. Another weakness of the book is its age. In a world of rapid changes through scientific and technological progress, it is not suprising that the book is not up-to-date. Today, the Unified Modeling Language (UML) defines the standard model of object orientation. Unfortunately, the book is both incomplete and inconsistent with the UML. For instance, it does not discuss the important concept of associations, it calls attributes "variables", and it uses the terms "collections" and "composition" in a way that is incompatible with the UML.