Software Design 2e - DIM

provide a major challenge to the designer and for the transfer of design knowledge betweendesigners. Design patterns, frameworks and methods all have a contribution to make and,indeed, the would-be designer of object-oriented systems really requires some degree of familiaritywith all three!A question sometimes raised is whether, after three decades of object-orientation, this paradigmhas really delivered what was promised? In some areas there are certainly questions that remain.Reuse has not proved to be as easily achieved as was once claimed, and some of the powerfulimplementation mechanisms of object-orientation, such as inheritance, have not proved easy touse well. On the other hand, there are also those domains such as the design of distributed systems,an important topic even if one not explicitly pursued in this book, where the object-orientedarchitectural style has found wide acceptance. The pragmatic view must be one that recognizesthat, while object-orientation has not delivered all that was originally hoped for (and we mightwell ask what software architectures have ever done this), it is now a major implementationalparadigm, and so one for which we need to be able to develop design models as effectively aspossible.399Further readingFurther readingSnyder A. (1993). The essence of objects: Concepts and terms. IEEE Software, January, 31–42A very well-written and carefully produced summary of both the object concept and the ideasthat go with it. The author writes on behalf of a ‘task force’ that has tried to provide a set ofterms to help with understanding of the concepts and with communication between those whomay be using those concepts. The paper defines a set of terms, and provides a taxonomy for theirmeanings, and probably represents one of the clearest summaries of key issues available.Booch G. (1994). Object-Oriented Analysis and Design with Applications. Second Edition.Benjamin-CummingsGrady Booch is one of the most elegant and informative writers about the object concept, andthis book provides an excellent introduction to these issues. Since it pre-dates the UML, thenotations are now little used, but that does not detract from the fact that this book provides avery informative and useful introduction to the object model and also to many of the issuesabout designing with objects.Coleman D., Arnold P, Bodoff S., Dollin C., Gilchrist H., Hayes F. and Jeremes P. (1994).Object-Oriented Development: The Fusion Method. Prentice HallA very readable text on this method, and one that introduces many of the issues through a casestudy approach that greatly assists with following the key points. The dominance of the UP incurrent literature should not be allowed to conceal the fact that methods such as Fusion are simplerin form, whilst also addressing most of the same development issues.Arlow J. and Neustadt I. (2002). UML and the Unified Process: Practical Object-Oriented Analysisand Design. Addison-WesleyThis is a very clear introduction to the Unified Process which uses a workflow-first approach andgives a very clear view of the key design and analysis elements.