ACM Books

The "Search Inside this Book" feature was not available when this review was posted. This book contains the following (excellent) articles:

TABLE OF CONTENTS

I. COMPONENT DEFINITON.
1. Definition of Software Component and its Elements.
George T. Heineman, William T. Councill.
2. The Component Industry Metaphor.
Hedley Apperly.
3. Component Models and Component Services: Concepts and Principles.
Rainer Weinreich, Johannes Sametinger.
4. An Example Specification for Implementing a Temperature Regulator Software Component.
Janet Flynt, Jason Mauldin.

II. THE CASE FOR COMPONENTS.
5. The Business Case for Software Components.
John Williams.
6. COTS Myths and Other Lessons Learned in Component-Based Software Development.
Will Tracz.
7. Roles for Component-Based Development.
Paul Allen.
8. Common High Risk Mistakes in Component-Based Software Engineering.
Wojtek Kozaczynski.
9. CBSE Success Factors: Integrating Architecture, Process, and Organization.
Martin L. Griss.

III. SOFTWARE ENGINEERING PRACTICES.
10. The Practice of Software Engineering.
George T. Heineman.
11. From Subroutines to Subsystems: Component-Based Software Development.
Paul C. Clements.
12. Status of CBSE in Europe.
Barry McGibbon.
13. CBSE in Japan and Asia.
Mikio Aoyama.

IV. THE DESIGN OF SOFTWARE COMPONENT INFRASTRUCTURES.
14. Software Components and the UML.
Kelli Houston, Davyd Norris.
15. Component Infrastructures: Placing Software Components in Context.
Steve Latchem.
16. Business Components.
James Carey, Brent Carlson.
17. Components and Connectors: Catalysis Techniques for Defining Component Infrastructures.
Alan Cameron Wills.
18. An Open Process for Component-Based Development.
Brian Henderson-Sellers.
19. Designing Models of Modularity and Integration.
Kevin J. Sullivan.

V. FROM SOFTWARE COMPONENT INFRASTRUCTURES TO SOFTWARE SYSTEMS.
20. Software Architecture.
Alexander L. Wolf, Judith A. Stafford.
21. Software Architecture Design Principles.
Len Bass.
22. Product-Line Architectures.
Martin L. Griss.

VI. THE MANAGEMENT OF COMPONENT-BASED SOFTWARE SYSTEMS.
23. Measurement and Metrics for Software Components.
Jeffrey Poulin.
24. The Practical Reuse of Software Components.
Don Reifer.
25. Selecting the Right COTS Software: Why Requirements are Important.
Cornelius Ncube, N.A.M. Maiden.
26. Build vs. Buy: A Rebuttal.
George T. Heineman.
27. Software Component Project Management Processes.
William T. Councill.
28. The Trouble with Testing Software Components.
Elaine Weyuker.
29. Configuration Management and Component Libraries.
Hedley Apperly.
30. The Evolution, Maintenance and Management of Component-Based Systems.
Mark Vigder.

VII. COMPONENT TECHNOLOGIES.
31. Overview of the CORBA Component Model.
Douglas C. Schmidt, Nanbor Wang, Carlos O'Ryan.
32. Transactional COM+: Designing Scalable Applications.
Timothy J. Ewald.
33. The Enterprise JavaBeans Component Model.
David Blevins.
34. Bonobo and Free Software Gnome Components.
Michael Meeks.
35. Choosing Between COM+, EJB, and CCM.
Andy Longshaw.
36. Software Agents as Next Generation Software Components.
Martin L. Griss.

VIII. LEGAL AND REGULATORY.
37. CBSE as a Unique Engineering Discipline.
John Speed, William T. Councill, George T. Heineman.
38. The Future of Software Components: Standards and Certification.
Janet Flynt, Manoj Desai.
39. Commercial Law Applicable to Component-Based Software.
Stephen Chow.
40. The Effects of UCITA on Software Component Development and Marketing.
Stephen Chow.

IX. CONCLUSION.
41. Summary.
William T. Councill, George T. Heineman.
42. Future of CBSE.
William T. Councill, George T. Heineman, Jeff Poulin.
Appendix A. Glossary.
References.
About the Authors.

I hope this helps.

This book is an excellent collection of articles describing all of the important issues surrounding the construction of component-based software systems. Each chapter describes a different aspect of the question of how to build a system using reusable components. Although each of these chapters is written by a different author or authors, they have been edited so that they read as a continuous whole. It is interesting that the editors were able to get some of the biggest names in the field to write articles on their specialties. A look at the author biographies show that they include industry practitioners, academics, industrial researchers, and independent consultants. Together they have a very impressive amount of experience and varied expertise. Perhaps my only complaint is that because so many different topics are covered, and each article is rather brief, some of the articles just touch the surface of the issues. But they do provide a balanced picture of these issues which then allow you to go out and do further in-depth reading on salient topics using the included list of references.

Covers the full spectrum of component-based software engineering, from the basics to legal aspects. Contains one of the most authoritative collections of essays and whitepapers on the subject between two covers. I have used this book as a basis for component-based development, and have also used it as the foundation for a SQA initiative because the material also addresses quality. Many of the essays support a software reuse strategy, which is an added bonus. Another use of this outstanding book is as a resource for in-house training in many aspects of software engineering outside of the component-based domain. It's that comprehensive and complete. I recommend using this book with Successful Software Development as the two primary references in mature development organizations.

This 818 page collection of 42 papers and articles is a definitive work on component-based software engineering. Regardless of your area(s) of interest, there is probably a chapter that addresses it. More importantly, each chapter is written by a top expert in their subspecialty.

Instead of giving a chapter-by-chapter description, I am going to cover the chapters that I found useful. To begin, Part II, chapters 1 through 3 gave me a quick primer in software components and highlighted the need to think in a different frame when dealing with component-based development. If you are new to CBSW then the 48 pages devoted to the basics are worthwhile reading.

Part II's five chapters on making a business and technical case for components is outstanding and the authors cover every facet. I found Part III, which covers software engineering practices, particularly useful. The value to me was the status of CBSW engineering on a global scale because I am currently providing consulting services to an India-based company that specializes in components. For this reason I also found Part IV's eight chapters on managing component-based software systems especially valuable.

The real eye-opener [for me], however, was in Part VIII, which devotes four interesting chapters on aspects of legal and regulatory issues as they related to software development as a discipline, and component-based software engineering specifically. In particular, chapter 38 on software component standards and certification was enlightening. I was also enlightened by chapter 39's fascinating discussion on commercial law applicable to component-based software, and the effects of the Uniform Computer Information Transactions Act (UCITA) on component-based software development and marketing.

This is an excellent book that covers the entire landscape of component-based software engineering and, although is a weighty 818 pages, is not difficult to read through. Each chapter is really a paper or article, so each is standalone. If you are dealing with off-shore development in any way, the book is especially valuable, and if you are doing CBSW in-house, the key differences between this approach and other development approaches are highlighted and will give you sufficient information with which to approach CBSW intelligently and effectively.

This book presents an excellent collection of papers describing various forms of mobility. It would be useful for a wide variety of technical professionals. This would also be an invaluable resource for students and researchers who plan to work in this increasingly important area. The unique feature of this book is the width of its coverage. It covers all the important papers I can think of.

1) The three areas covered - although they have similar problems with similar solutions - are rarely presented together. 2) The editors have selected a nice cross-section of papers from the three areas, and 3) The editors make some key points about and draw some key parallels between the three areas in the introductions and summaries.

This book is an excellent collection of research papers on mobility, and it serves as a good introduction on the topic as well as a reference for new work. It stands out for three reasons: (1) Its breadth - it covers all important aspects of mobility in a single volume. (2) Its depth - it pulls together papers from many different sources, including major conferences, but also hard-to-find, yet ground-breaking papers. (3) Its commentary - both by the authors and by the individual researchers (in the form of afterwords).

Having reviewed this book before and after it's publication, I can say without a doubt that this is the best book to date on how to implement a effective, systematic reuse program. The book addresses all aspects of Software Reuse, from organizational factors to implementation technologies. All the authors have experience with implementing reuse programs in the real world, and they speak from experience as well as from expertise. If you are at all interested in Software Reuse, or with improving software development productivity, you need this book.

Don't limit yourself to code reusability. This book goes further. Think about reusability from the beginning, put it into your analysis and design models.

The book talks about an _architecture_ and a _process_ to achieve software reusability. I found the book hard to read. Sometimes I felt they did not "hit-the-ground". My problem? I was thinking in code. Don't let that happen to you.

The authors talk about a complete organized process to achieve reusability. The book is a must if you are thinking in reusability.

Read it!

This is an excellent book for developers, architects, project managers, and development managers. It clearly explains how to adjust your development practices to achieve reuse at all levels. I found it particularly helpful in diagnosing common management issues that hinder reuse practices. This book has helped me gather the information needed to effectively establish reusability.

Until such time as someone tries to fill the shoes of Jean Sammet and write a new overview of programming languages (a major job, that!), the HOPL conferences are the main source of insight into the development of programming languages that, Sapir-Whorf style, have shaped the way we view programming and the problems we try to solve with a computer. Even if someone does take up that task, the HOPL conferences are invaluable, since they provide information straight from the people involved.

This volume of the proceedings of HOPL II is thus invaluable for the student of programming. HOPL I covered the main early languages (Algol 60, FORTRAN, COBOL, LISP, APT, BASIC...); HOPL II covers important languages of more recent vintage (Algol 68, Pascal, C, C++. more recent dialects of LISP). C.H. Lindsey's fine paper on the turbulent development of Algol 68, the best language you probably never used and a major influence on later languages, is worth the price of admission by itself.

I have read many many computer jounrals about the history of computing. Very few resources have put the kind of time and effort that Thomas Bergin has done in his book. Along with assistant editor, RIck Gibson, both men do a fine job collecting the best of the best resources and giving it right to the public upfront. I wish Bergin can do another book or something Internet related because this is truly apart of computing that we do not really have much material on.

npthin

It's just the book I am looking for

This book covers the most up to date information in the field of human computer interaction, also known as human factors engineering. It is a collection of papers from industry experts and discusses works in progress.

The book is extremely well organized since it has not only an index of terms but an index of authors and a table of contents that groups papers by topic.

The topics cover the most technical issues of virtual reality, software programming tools and techniques to the most human centered issues of the learning processes, keyboard styles and narrative techniques.

This book provides important information for any person that designs, develops, delivers or trains people in the field of automation.

This book identifies the correct terms for computing history phases, and also shows the history for early computing well. A good read written by an IBM director in France.

For any use of the Unisys A Series/Clearpath systems that desires some deeper knowledge of how these systems were designed, I highly recommend this book.

This book gives a complete presentation of the major operator and stack architecture elements. While much of the information is no longer valid for the current architectures, the basic PCW, RCW, MSCW words are there in theory, if not accurate for today's systems. This book gives a good insight into the reason that ALGOL screams on these systems. I highly recommend this book for all support or systems persons on the A Series or Clearpath NX systems.

I was so impressed by the depth, comprehensiveness, and the presentation of this book. Anyone who wants to know more about security should read this book.