The anti - pattern to following this principle would be to thoroughly document precise requirements at the outset of the project , force stakeholder acceptance of requirements , and then negotiate any changes to the requirements , where each change may increase the cost or duration of the project 遵循这一原则的反模式是在项目开始详细记录精确的需求,强制涉众接受需求,然后对需求的变更进行协商,而需求的每一点变更都将增加项目的成本或持续时间。
For instance , a common anti - pattern that we ve seen far too often is a design where a persistence layer is wrapped inside an xml api and then placed in a process separate from the business logic that needs to invoke the persistence layer . in versions of this design , we ve seen people actually serialize java 例如,一个我们熟得不能再熟了的常见反模式( anti - pattern )是这样的一种设计:一个持久性层被包装在一个xml api内,然后将它放在与需要激活这个持久层的业务逻辑隔离的流程中。