Software Design 2e - DIM

124Transferring design knowledgeA specific feature of this book is that, for just such reasons, no code-based exampleshave been used to illustrate points. The assumption throughout has been, and willbe, that the reader has a basic understanding of the basics of programming, and thatthe role of this book is to help further with developing an understanding of how toform and employ these ‘intermediate models’.SummaryThis chapter has examined some of the principal ways in which software design knowledge andexpertise can be codified and transferred. Particular issues addressed here have included:nnthe reasons for transferring design knowledge, and (where known) for codifying the rationalebehind such knowledge;the role of the concept of architectural style in providing a framework and a vocabulary fortop-level design ideas, and for assisting with the choice of design strategy;nnthe use of design methods to codify design practices and strategies;the rationale for using design patterns and their ability to describe the core features ofreusable design solutions.Further readingMonroe R.T., Kompanek A., Melton R. and Garlan D. (1997). Architectural styles, design patterns,and objects. IEEE Software, 14(1), 43–52A very readable paper that draws together many of the concepts discussed in this chapter andexplores their capabilities and roles, as well as their strengths and limitations, with some simpleexamples for illustration.Shaw M. and Garlan D. (1996). Software Architecture: Perspectives on an Emerging Discipline.Prentice-HallThis is the definitive reference text for the subject of software architecture. Although in terms ofdeveloping the theme its structure is rather fragmented, it contains a wide set of examples andillustrates all of the key ideas.Exercises6.1 The concept of architectural style can be recognised in many domains. Identify some examplesof architectural styles and their principal characteristics, for the following domains:(a) ships;(b) motor vehicles;(c) publications;