基于契约编程理论英文.pptVIP

* * * * * DbC vs defensive programming DbC placeCard(c:INTEGER,x:INTEGER,y:INTEGER) is require valid_card_number: (c=1) and (c=MAXCARDS) do … end * 映射：从契约的设计到产生异常的实现 DbC vs defensive programming 差异 DbC中先验条件是程序文档的组成部分，而产生异常的语句是程序体本身的组成部分。 采用注释来描述例程对参数的限制时，很难保证这个注释正确地描述了该限制。但可以相信具有显式先验条件检查的文档，因为断言在测试时经受了考验。 * 契约的一些开销和限制 契约的撰写成本 实践需求 麻痹大意 质量并不总是主要目标 最好用于顺序式程序（sequential program） 语言不提供支持 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * CS3101 Design by Contract — Principles (c) 2004 University of Manchester CS3101 * (c) 2004 University of Manchester CS3101 * (a) Briefly define and explain (i) software correctness (ii) software reliability. (b) Explain what is meant by Design by Contract and why it is important for OOSC. Illustrate your answer with suitable examples. (c) How well does Java support Design by Contract? Give reasons for your answer. Sample Exam Question Software Reliability (c) 2004 University of Manchester CS3101 * But these must not be attained at the expense of reliability（可靠性）, i.e. The quality factors of software are: compatibility（兼容性） extensibility（可扩展性） reusability(可重用性) robustness — ability to react to cases not in spec correctness — ability to perform according to spec, and Design by Contract (c) 2004 University of Manchester CS3101 * Consider the relationship between a class and its clients: Without such a precise definition we cannot have a significant degree of trust in large software systems. Contract violations lead to run-time errors, i.e. exceptions. Class B m1() contract Class A DbC views this as a formal agreement, or contract, expressing each party’s rights and obligations. claims responsibilities So we will also consider exception handling. Software Correctness (c) 2004 University of Manchester CS3101 * regardless of the size of the program Suppose someone comes to you with a program, and asks “Is this program correct?”. This question is meaningful only if there is a precis