软件体系架构(第十三章中文).docxVIP

是人们在生产生活实践当经过积累的经验的抽象和升华。简单地说，就是从不断重复出现的事件中发现和抽象出的规律，是解决问题形成经验的高度归纳总结。只要是一再重复出现的事物，就可能存在某种模式。[1]模式，即pattern。其实就是解决某一类问题的方法论。即把解决某类问题的方法总结归纳到理论高度，那就是模式。restrict dependencies. layers define an ordering and only allow a layer to use the services of its adjacent layer. the possible communication paths are reduced to the number of layers minus one. this limitation has a great influence to dependencies betweeen the layers and makes it much easier to limit the side effects of replacing a layer.Without any one of its tactics, the pattern might be ineffective. For example, if the restrict dependencies tactics is not employed, then any function in any layer can call any other function in any other layer, destroying the low coupling that makes the layering pattern effective. If the increase semantic coherence tactics is not employed, then functionality could be randomly sprinkled throughout the layers, destroying the separation of concerns, and hence ease of modification, which is the prime motivation for employing layers in the first place.Table 13.12 shows a number of the architectural patterns described in the book pattern-oriented software architecture 1:A System of Patterns, by Buschmann et al., and shows which modifiability tactics they employ.如果不采用增加语义一致性的策略，那么功能便可以随机散置在所有层，破坏了关注分离，因此不易于修改，而易于修改是起初采用层的主要动机。表13.12展示了Buschmann等人著作的书——《面向模式的软件架构，第一卷》所描述的一些软件架构，并展示了他们所使用的可修改性策略。Using tactics to augment patterns使用策略来增强模式A pattern is described as a solution to a class of problems in a general context. When a pattern is chosen and applied, the context of its application becomes very specific. A documented pattern is therefore underspecified with respect to applying it in a specific situation.To make a pattern work in a given architectural context, we need to examine it from two perspectives:一种模式被描述为在一般情况下的一类问题的解决方案。当一个模式被选择并且应用，其应用程序的上下文（当前的语言环境，背景，内容）变得非常具体。因此并不会指定在某个特定情况下使用某一个文档齐全的模式。为了使一种模式能够在一个给定的架构环境中起作用，我们需要从两个方面来检测：The inherent quality attribute tradeoffs that the patte