Customer Reviews


14 Reviews
5 star:
 (11)
4 star:
 (2)
3 star:
 (1)
2 star:    (0)
1 star:    (0)
 
 
 
 
 
Average Customer Review
Share your thoughts with other customers
Create your own review
 
 

The most helpful favorable review
The most helpful critical review


18 of 18 people found the following review helpful
4.0 out of 5 stars A good book
The main objective of the book is to present software components and their importance in software engineering mainly for reuse purpose. To a large extent, this objective has been achieved. The book is a fairly good and complete coverage of many technical (foundations, approaches, implementation, standards, etc.) and non-technical aspects (markets,...
Published on May 25, 2000 by mimou

versus
7 of 13 people found the following review helpful
3.0 out of 5 stars Easy Reading
I got this book by almost by accident waiting for one of those Japanesse Fish barns to open.
It explained many of the issues that occur in OO development - problems with extreme re-use - fragile base class problem, "changing the way you do business" and many others. I actually found these non-component chapters in some ways more useful than the...
Published on December 16, 1998


‹ Previous | 1 2 | Next ›
Most Helpful First | Newest First

18 of 18 people found the following review helpful
4.0 out of 5 stars A good book, May 25, 2000
The main objective of the book is to present software components and their importance in software engineering mainly for reuse purpose. To a large extent, this objective has been achieved. The book is a fairly good and complete coverage of many technical (foundations, approaches, implementation, standards, etc.) and non-technical aspects (markets, billing, professions, etc.) of software components. The presentation of the three major approaches for software components, i.e., OMG CORBA, Sun Java and Microsoft COM, and their comparison are very valuable especially when one has to choose one of this approach in building component-based systems. The discussion of non- technical aspects, especially, the market issue is a plus in such types of books.
In this book, systematic reuse is viewed as how to build reusable asset consisting primarily of software components. Reuse is mostly viewed through implementation inheritance and object composition with forwarding or delegation in the object-oriented sense. In that respect, the book goes into many details related to objects. While objects are tightly related to software components from the author's point of view, it is sometimes not clear how the presented discussion is useful for actually building reusable components. Also, sometimes the reader may lost the relationship and differences between objects and components. On the other hand, the author should have discussed in more details the importance of software components in the general area of software reuse. In particular, will software components based on objects be the only way to build reusable components. There are also a number of software engineering issues that should receive more attention regarding the reuse of components. These concern library or catalog of components and quality measurement of components.
The book is well organized, but I think that short chapters should be grouped together. This is especially the case for the last part. Also, one of the problem that I had while reading the book is that in some instances the link between successive sections is not well done. Finally, in my opinion, many of the chapters in part two, three and four should be read in two passes, a first quick pass and a second more deep reading. This will enable the reader to get a maximum benefit from them.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


12 of 12 people found the following review helpful
5.0 out of 5 stars The definitive text for component software, January 27, 1998
By 
cek "cek" (Bellevue, WA) - See all my reviews
If found this book very enlightening. It is the first book I have seen that discusses component oriented software in a real world way. Mind you this is a text book, not your typical programming book, so some of its appeal will be limited. However, for anyone doing any serious thinking about component software this book is a must read.
The author (one of the principles behind Oberon and Component Pascal) very carefully avoids taking explicit sides in the so-called "component wars" (the same cannot be said about his stance on objects v. components, he clearly believes OO has failed to live up to its promises). However, I think the book is (indirectly) about Microsoft's COM in that it explains, in a very detailed, academic sort of way, the same principles that are behind COM. I don't think the author intended to write a book about COM, it's just that his ideas and the ideas of the designers of COM appear to be very similar.
At 28 chapters & 411 pages this is a long book. It covers a lot of material. Some parts are pretty hard to read because they are so academically grounded. The author recognizes this and warns the reader beforehand. Most of the sections I found hard to read could easily be skipped over without detracting from the real value the book provides.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


9 of 9 people found the following review helpful
5.0 out of 5 stars A new bible for component designers, developers, and users., July 26, 1998
Szyperski's book discusses component software from an unusual point of view: as an academic and a professional. This perspective provides the reader with the best of both worlds: a discussion of essential academic object and component concepts as well as a pragmatic review of existing component systems. In particular, the important topics that Szyperski covers include callbacks and their impact on reuse, reentrant code, component interface specification with contracts, subtyping (co/contravariance), code and behavioral inheritance, and finally safety and progress specifications. Each of these topics is critical to the development of robust and reusable components. Szyperski's discussion of todays' component frameworks (loosely, CORBA, COM, and Java) shows his biases, but they are objectively justified. Finally, the author discusses the next generation of component architectures. Included in this discussion is a brief foray into OpenDoc! , a discussion of Oberon Microsystems' BlackBox component framework, and Portos and Denia, two hard realtime component frameworks. Any designer or developer that uses or builds components must read this book. It will help the good component designer/developer/manager become a _great_ component thinker.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


6 of 6 people found the following review helpful
4.0 out of 5 stars Best conceptual foundation around, June 1, 2004
This review is from: Component Software: Beyond Object-Oriented Programming (2nd Edition) (Hardcover)
Szyperski has written a truly outstanding introduction to component software systems. This is the most complete, clearest introduction to the basic problems and practice of component software development that I've seen.
After the introductory chapter, about the first third of the book discusses object oriented development. That's no contradiction: OO technology is usually the implementation vehicle for component systems. Szyperski adds (or at least collects) real content about OO technique, including the problematic relationship between 'contracts' and callbacks, language features for containment and control, and the many needs that current OO languages don't meet. Lots of the discussion sounds like 'the loyal opposition' - he supports OO practice, even demands it, but is harshly critical of the OO techniques that cause real problems.
The remainder of the book describes requirements of a workable component system and a workable component industry. If done right, component software really could solve a lot of problems: squabbling in multi-vendor environments, maintenance across multiple generations of releases, and more. The theoretical discussion is backed up with case studies, including JavaBeans, CORBA, and OpenDoc.
The would-be component user won't find a lot here; this book is really for the component or component framework developer. Developers, however, should not expect a lot of direct, technical detail. This discusses principles, not implementation. That's my one real disappointment in this book: the lack of detail. Even the case studies are brief and somewhat shallow. Those problems are easy to fix, however, with other books on specific APIs, systems, and development techniques.
If you are planning a component-based system, whether as a component user or a component developer, this book may be essential. It gives a complete, critical view of what components can do and what they should but cannot yet do. As you go through development, you'll come back to this book (or at least to its issues) again and again.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


5 of 5 people found the following review helpful
5.0 out of 5 stars Excellent book, November 19, 1998
By A Customer
I am relatively new to "components" and after reading a few disappointing books, I found this gem of a book quite by chance. This is not your typical introductory fluffy book - it is very technical and detailed in parts, but provides a good roadmap for beginning readers who want just an overview before digging into thte details. Besides providing a good perspective about Java, Corba, COM etc., the unique thing about this book is that the author also discusses their differences from two different perspectives - the technical (academic) differences and the "real-world" differences (i.e. how they impact your software infrastructure. Very well-written (dont be put off by a typo in the very sentence of chapter 1 - its the only typo I noticed)
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


4 of 4 people found the following review helpful
5.0 out of 5 stars Insightful analysis of software components, May 15, 1998
By A Customer
A beautifully written and researched book, Component Software is a fascinating study of the practical aspects of making components work in software development. Touching on Java, CORBA, COM, architectures, frameworks, component assembly, domain standards and much more, the author gives the reader an impressive panaroma of the state-of-the-art in component technology.....But this doesn't do justice to the expressiveness, insight, and impressive range of integration between fields of component study that Szyperski puts into this book. You will not find a more useful addition to your library about component technology and we recommend it strongly. -- Object News Book Reviews
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


5 of 6 people found the following review helpful
5.0 out of 5 stars Highly recommended SW Components book, May 24, 2003
This review is from: Component Software: Beyond Object-Oriented Programming (2nd Edition) (Hardcover)
When I started SW Engineering the SW functional decomposition methods were in fashion. People became relatively quickly familiar with them, and we developed our SW on Intel's 8086 based chip sets, with a few Ks of memory. The programming practices were reinforced by our peers and the Management.
Then came the buzz-word SW Object Orientation. I first heard it in the mid 80s. To be frank about it, it had taken me about three years to get to the bottom of it. In my experience about 95% of the people who talked about it were either clueless or those who only wanted to jump on the fast track wagon.
In my view, the OO in its pure form is a little bit complex concept. Lets face it, when you start with a mean set of customer requirements and you have your boss breathing down your neck in some cases for no good reason, you are not going to be in the best frame of mind to look for SW objects in a bubble pool of analysis. OOD requires all kind of disciplines. Even the best OO design may not be supported by your target language and it may not be the best approach to your problem, what I'm mean that is like trying to dig your garden with a eating fork which may look like a garden fork !
Here comes the SW component part. Why not group the requirements into a set of likely entities ? Once the requirements are grouped in such fashion the SW Analysis elements are easily mapped onto what is called 'SW Components' which are well described in this book. The author is very descriptive about the idea and he is able to convey it in a simple manner. This book is not only about SW components it also covers other serious technologies such as SW Standards, differences in Components and Objects, SW design architecture, parallel and concurrency.
My comments here are related to SW System Developments, NOT System programming which requires different set of rules and support.
This book is for those who wish to learn about new technologies, the SW Components. It may not necessarily solve your current problems. At the end of the day there is never an optimal SW Technology which has all the best solutions for all the SW cases.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


4 of 5 people found the following review helpful
5.0 out of 5 stars Great Book!, August 6, 1999
By A Customer
It was refreshing to read a book with objective analysis without any marketing hype and propaganda that you find in other books in the market. I particularly liked the section where the author gives an unbiased comparison of COM/DCOM, CORBA, and JavaBean.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


1 of 1 people found the following review helpful
5.0 out of 5 stars Absolutely must read for any serious Software Engineer, December 1, 2005
By 
This review is from: Component Software: Beyond Object-Oriented Programming (2nd Edition) (Hardcover)
Very well written and informative. I 've read a few book that tend to be either very verbose or written for novices. This one hits the spot.

The best part is that reading this book makes you think.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


2 of 3 people found the following review helpful
5.0 out of 5 stars What we really wanted was software components -- read about it here, September 6, 2010
This review is from: Component Software: Beyond Object-Oriented Programming (2nd Edition) (Hardcover)
I searched for a book that would fill in the details about what I already felt, and was learning from a colleague: that to create software components you don't need classes. My efforts were rewarded when I saw the titles of chapters 1 and 7:

1.1 Components are for composition
7. Object versus class composition, or how to avoid inheritance

and further,

7.1 Inheritance -- the soup of the day?

Component Software: Beyond Object-Oriented Programming goes back to first principles and requirements -- what we really want from software development, how such design methods would look, and then, in the later chapters that I only skimmed, how it might be done in current languages and frameworks. Bonus of understanding: why what's popularly known as "Object-Oriented" programming is really only "Inheritance-Based" programming. For software architects, and for developers who are early adopters, risk-takers, or inventors of better ways to code, well worth checking out this book.

--
Full disclosure: I only had time to read the first third of the book before I had to move on to other topics.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


‹ Previous | 1 2 | Next ›
Most Helpful First | Newest First

Details

Component Software: Beyond Object-Oriented Programming (2nd Edition)
Component Software: Beyond Object-Oriented Programming (2nd Edition) by Clemens Szyperski (Hardcover - November 23, 2002)
Used & New from: $14.91
Add to wishlist See buying options
Search these reviews only
Send us feedback How can we make Amazon Customer Reviews better for you? Let us know here.