ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1949 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Design Patterns in Communications Software
Linda Rising (ed)
0 521 79040 9
Cambridge University Press
Mark Easterbrook
Appeared in:
This book is a catalogue of design patterns in telecommunications software originating from TelePLoP and ChiliPLoP conferences. This is a valuable resource for any engineer working in the telecom or datacomms software. A basic understanding of design patterns and pattern languages is required to get the most out of the book although the material is presented in a readable style that allows the pattern concepts to be picked up as you go.

The telecoms and datacomms worlds leave the computer world standing when it comes to acronyms, abbreviations and other terminology, making them difficult to new comers. The book is careful to explain these clearly so that, for example, it is clear when IP means Internet Protocol (datacomms), Intelligent Peripheral (telecoms) or Intellectual Property.

As with any collection of patterns or pattern languages, you cannot just use it as a recipe book to produce software solutions - it takes time to learn the pattern languages and understand where they can be applied - and therefore it is not a book to be read cover to cover, but one to be dipped into from time to time, although it is necessary to spend some time initially becoming familiar with the book structure.

There are three sections to the material, the first two covering large collections and small collections respectively and deal with creating solutions from scratch. The final section is concerned with managing change and, given that most developers spend more time changing existing systems than creating new ones, is possibly the most useful section.