We worked hard, and my students (some with considerable experience in object-oriented design) became enthusiastic about the possibilities for sharing expertise opened by catalogs of patterns in this book. Although the monograph is not intended as a textbook, for my purpose it proved quite suitable. I selected design patterns and this book for a course called “Selected Topics in Software Engineering,” offered to postgraduate students. I have successfully used this monograph as a textbook. The authors classify the patterns by purpose into three groups: creational patterns (chapter 3), structural patterns (chapter 4), and behavioral patterns (chapter 5). The chapter also includes a catalog of design patterns. The second chapter is a case study that shows some of the patterns used in designing a document editor. The first chapter is an introduction to the notion of patterns and how they are described and used. The book consists of six chapters, three appendices, a bibliography, and an index. The book is in fact “only” a catalog, but what would be just a standard handbook for engineers in other fields is a genuine leap in the development of software engineering. have taken an important step towards that goal with their book on design patterns. (See my review of Sommerville's monograph on software engineering. In the past I have articulated my vision of books that serve both as a source of knowledge and as a reference for both students and practitioners.
0 Comments
Leave a Reply. |