1.

Design by contract (DbC), also known as contract programming, programming by contract and design-b
A. Design by contract (DbC), also known as contract programming, programming by contract and desig
B. Subsequently, the supplier guarantees to the client that when a delete feature finishes its work, the d
C. This leads to earlier and more specific error detection.
D. In effect, DbC advocates writing the assertions first.

2. Other design contracts are concepts of class invariant.

A. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw
B. However, DbC considers these contracts to be so crucial to software correctness that they should be
C. Other design contracts are concepts of class invariant.
D. The notion of a contract extends down to the method/procedure level; the contract for each method

3. Launching the Python interpreter with "-O" (for "optimize") as an argument will likewise cause the Python
A. It prescribes that software designers should define formal, precise and verifiable interface specificati
B. Launching the Python interpreter with "-O" (for "optimize") as an argument will likewise cause the Py
C. A client class is obliged to make calls to supplier features where the resulting state of the supplier is
D. More often than not, the supplier throws an exception to inform the client that the precondition has b

4. Subsequently, the supplier is obliged to provide a return state and data that does not violate the state re
A. Subsequently, the supplier is obliged to provide a return state and data that does not violate the stat
B. This can be summarised by the "three questions" that the designer must repeatedly answer in the co
C. DbC's "fail hard" property simplifies the debugging of contract behavior, as the intended behaviour o
D. Launching the Python interpreter with "-O" (for "optimize") as an argument will likewise cause the Py

5. Design by contract has its roots in work on formal verification, formal specification and Hoare logic.
A. Contracts are therefore typically only checked in debug mode during software development.
B. The term was coined by Bertrand Meyer in connection with his design of the Eiffel programming lang
C. Design by contract has its roots in work on formal verification, formal specification and Hoare logic.
D. Rather, it complements external testing with internal self-tests that can be activated both for isolated

6. This approach differs substantially from that of defensive programming, where the supplier is responsibl
A. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no spe
B. In such cases, DbC makes the supplier's job easier.
C. When using contracts, a supplier should not try to verify that the contract conditions are satisfied—a
D. This approach differs substantially from that of defensive programming, where the supplier is respon
7. More often than not, the supplier throws an exception to inform the client that the precondition has been
A. All class relationships are between client classes and supplier classes.
B. More often than not, the supplier throws an exception to inform the client that the precondition has b
C. These rules approximate behavioural subtyping.
D. Eiffel Software applied for trademark registration for Design by Contract in December 2003, and it w

8. In many programming languages, contracts are implemented with assert.

A. The current owner of this trademark is Eiffel Software.
B. Subsequently, the supplier is obliged to provide a return state and data that does not violate the stat
C. In many programming languages, contracts are implemented with assert.
D. This effectively eliminates the run-time costs of asserts in production code—irrespective of the numb

9. These rules approximate behavioural subtyping.

A. Languages that implement most DbC features natively include: Additionally, the standard method co
B. These rules approximate behavioural subtyping.
C. When using contracts, a supplier should not try to verify that the contract conditions are satisfied—a
D. The current owner of this trademark is Eiffel Software.

10. A client class is obliged to make calls to supplier features where the resulting state of the supplier is no
A. Where this assumption is considered too risky (as in multi-channel or distributed computing), the inv
B. The class invariant guarantees (for the local class) that the state of the class will be maintained with
C. A client class is obliged to make calls to supplier features where the resulting state of the supplier is
D. The notion of a contract extends down to the method/procedure level; the contract for each method

11. Rather, it complements external testing with internal self-tests that can be activated both for isolated te
A. Design by contract (DbC), also known as contract programming, programming by contract and desig
B. Launching the Python interpreter with "-O" (for "optimize") as an argument will likewise cause the Py
C. When using contracts, a supplier should not try to verify that the contract conditions are satisfied—a
D. Rather, it complements external testing with internal self-tests that can be activated both for isolated

12. However, DbC considers these contracts to be so crucial to software correctness that they should be p
A. In such cases, DbC makes the supplier's job easier.
B. However, DbC considers these contracts to be so crucial to software correctness that they should be
C. In many programming languages, contracts are implemented with assert.
D. DbC's "fail hard" property simplifies the debugging of contract behavior, as the intended behaviour o
13. This effectively eliminates the run-time costs of asserts in production code—irrespective of the number
A. This effectively eliminates the run-time costs of asserts in production code—irrespective of the numb
B. For instance, a supplier data buffer may require that data is present in the buffer when a delete featu
C. Contract conditions should never be violated during execution of a bug-free program.
D. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no spe

14. The notion of a contract extends down to the method/procedure level; the contract for each method wil
A. The notion of a contract extends down to the method/procedure level; the contract for each method
B. Subsequently, the supplier is obliged to provide a return state and data that does not violate the stat
C. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw
D. Asserts are by default compiled away in release mode in C/C++, and similarly deactivated in C# and

15. This leads to earlier and more specific error detection.

A. More often than not, the supplier throws an exception to inform the client that the precondition has b
B. Languages that implement most DbC features natively include: Additionally, the standard method co
C. This leads to earlier and more specific error detection.
D. In many programming languages, contracts are implemented with assert.

16. The metaphor comes from business life, where a "client" and a "supplier" agree on a "contract" that def
A. The DbC approach assumes all client components that invoke an operation on a server component
B. The metaphor comes from business life, where a "client" and a "supplier" agree on a "contract" that
C. Design by contract (DbC), also known as contract programming, programming by contract and desig
D. Languages that implement most DbC features natively include: Additionally, the standard method co

17. Where this assumption is considered too risky (as in multi-channel or distributed computing), the invers
A. Where this assumption is considered too risky (as in multi-channel or distributed computing), the inv
B. Rather, it complements external testing with internal self-tests that can be activated both for isolated
C. Contracts are therefore typically only checked in debug mode during software development.
D. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw

18. All class relationships are between client classes and supplier classes.
A. All class relationships are between client classes and supplier classes.
B. However, DbC considers these contracts to be so crucial to software correctness that they should be
C. The notion of a contract extends down to the method/procedure level; the contract for each method
D. Rather, it complements external testing with internal self-tests that can be activated both for isolated
19. Later at release, the contract checks are disabled to maximize performance.
A. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no spe
B. These specifications are referred to as "contracts", in accordance with a conceptual metaphor with t
C. Later at release, the contract checks are disabled to maximize performance.
D. This approach differs substantially from that of defensive programming, where the supplier is respon

20. In such cases, DbC makes the supplier's job easier.

A. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no spe
B. Contracts are therefore typically only checked in debug mode during software development.
C. Design by contract has its roots in work on formal verification, formal specification and Hoare logic.
D. In such cases, DbC makes the supplier's job easier.

21. Languages that implement most DbC features natively include: Additionally, the standard method comb
A. The use of assertions can be considered to be a form of test oracle, a way of testing the design by c
B. The term was coined by Bertrand Meyer in connection with his design of the Eiffel programming lang
C. In such cases, DbC makes the supplier's job easier.
D. Languages that implement most DbC features natively include: Additionally, the standard method co

22. These specifications are referred to as "contracts", in accordance with a conceptual metaphor with the
A. The metaphor comes from business life, where a "client" and a "supplier" agree on a "contract" that
B. Design by contract has its roots in work on formal verification, formal specification and Hoare logic.
C. This effectively eliminates the run-time costs of asserts in production code—irrespective of the numb
D. These specifications are referred to as "contracts", in accordance with a conceptual metaphor with t

23. DbC's "fail hard" property simplifies the debugging of contract behavior, as the intended behaviour of e
A. More often than not, the supplier throws an exception to inform the client that the precondition has b
B. It prescribes that software designers should define formal, precise and verifiable interface specificati
C. The class invariant guarantees (for the local class) that the state of the class will be maintained with
D. DbC's "fail hard" property simplifies the debugging of contract behavior, as the intended behaviour o

24. The DbC approach assumes all client components that invoke an operation on a server component wil
A. Design by contract (DbC), also known as contract programming, programming by contract and desig
B. The DbC approach assumes all client components that invoke an operation on a server component
C. The metaphor comes from business life, where a "client" and a "supplier" agree on a "contract" that
D. It prescribes that software designers should define formal, precise and verifiable interface specificat
25. Design by contract also defines criteria for correctness for a software module: Design by contract can a
A. Other design contracts are concepts of class invariant.
B. Subsequently, the supplier is obliged to provide a return state and data that does not violate the stat
C. Design by contract also defines criteria for correctness for a software module: Design by contract ca
D. The advantage of internal self-tests is that they can detect errors before they manifest themselves a

26. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no specia
A. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no spe
B. Asserts are by default compiled away in release mode in C/C++, and similarly deactivated in C# and
C. Contract conditions should never be violated during execution of a bug-free program.
D. Design by contract does not replace regular testing strategies, such as unit testing, integration testin

27. The original contributions include: The central idea of DbC is a metaphor on how elements of a softwar
A. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw
B. The DbC approach assumes all client components that invoke an operation on a server component
C. In effect, DbC advocates writing the assertions first.
D. A client class is obliged to make calls to supplier features where the resulting state of the supplier is

28. Contract conditions should never be violated during execution of a bug-free program.
A. Contract conditions should never be violated during execution of a bug-free program.
B. When using contracts, a supplier should not try to verify that the contract conditions are satisfied—a
C. The class invariant guarantees (for the local class) that the state of the class will be maintained with
D. Where this assumption is considered too risky (as in multi-channel or distributed computing), the inv

29. This can be summarised by the "three questions" that the designer must repeatedly answer in the cont
A. Contracts are therefore typically only checked in debug mode during software development.
B. The notion of a contract extends down to the method/procedure level; the contract for each method
C. This can be summarised by the "three questions" that the designer must repeatedly answer in the co
D. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no spe

30. It prescribes that software designers should define formal, precise and verifiable interface specification
A. For instance, a supplier data buffer may require that data is present in the buffer when a delete featu
B. Contracts are therefore typically only checked in debug mode during software development.
C. The use of assertions can be considered to be a form of test oracle, a way of testing the design by c
D. It prescribes that software designers should define formal, precise and verifiable interface specificat
31. The current owner of this trademark is Eiffel Software.
A. The notion of a contract extends down to the method/procedure level; the contract for each method
B. This leads to earlier and more specific error detection.
C. The term was coined by Bertrand Meyer in connection with his design of the Eiffel programming lang
D. The current owner of this trademark is Eiffel Software.

32. The class invariant guarantees (for the local class) that the state of the class will be maintained within s
A. The advantage of internal self-tests is that they can detect errors before they manifest themselves a
B. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw
C. These rules approximate behavioural subtyping.
D. The class invariant guarantees (for the local class) that the state of the class will be maintained with

33. Asserts are by default compiled away in release mode in C/C++, and similarly deactivated in C# and Ja
A. Design by contract (DbC), also known as contract programming, programming by contract and desig
B. These rules approximate behavioural subtyping.
C. Asserts are by default compiled away in release mode in C/C++, and similarly deactivated in C# and
D. In such cases, DbC makes the supplier's job easier.

34. For instance, a supplier data buffer may require that data is present in the buffer when a delete feature
A. For instance, a supplier data buffer may require that data is present in the buffer when a delete featu
B. Later at release, the contract checks are disabled to maximize performance.
C. The advantage of internal self-tests is that they can detect errors before they manifest themselves a
D. When using contracts, a supplier should not try to verify that the contract conditions are satisfied—a

35. The term was coined by Bertrand Meyer in connection with his design of the Eiffel programming langua
A. The class invariant guarantees (for the local class) that the state of the class will be maintained with
B. In such cases, DbC makes the supplier's job easier.
C. The term was coined by Bertrand Meyer in connection with his design of the Eiffel programming lang
D. Design by contract also defines criteria for correctness for a software module: Design by contract ca

36. Contracts are therefore typically only checked in debug mode during software development.
A. Contracts are therefore typically only checked in debug mode during software development.
B. This leads to earlier and more specific error detection.
C. Languages that implement most DbC features natively include: Additionally, the standard method co
D. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw
37. In effect, DbC advocates writing the assertions first.
A. In such cases, DbC makes the supplier's job easier.
B. The class invariant guarantees (for the local class) that the state of the class will be maintained with
C. In effect, DbC advocates writing the assertions first.
D. A client class is obliged to make calls to supplier features where the resulting state of the supplier is

38. Design by contract does not replace regular testing strategies, such as unit testing, integration testing a
A. The DbC approach assumes all client components that invoke an operation on a server component
B. Design by contract does not replace regular testing strategies, such as unit testing, integration testin
C. Other design contracts are concepts of class invariant.
D. Where this assumption is considered too risky (as in multi-channel or distributed computing), the inv

39. Subsequently, the supplier guarantees to the client that when a delete feature finishes its work, the dat
A. Subsequently, the supplier is obliged to provide a return state and data that does not violate the stat
B. Subsequently, the supplier guarantees to the client that when a delete feature finishes its work, the d
C. However, DbC considers these contracts to be so crucial to software correctness that they should b
D. In many programming languages, contracts are implemented with assert.

40. When using contracts, a supplier should not try to verify that the contract conditions are satisfied—a pr
A. It prescribes that software designers should define formal, precise and verifiable interface specificati
B. The DbC approach assumes all client components that invoke an operation on a server component
C. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw
D. When using contracts, a supplier should not try to verify that the contract conditions are satisfied—a

41. The contracts for a module can be regarded as a form of software documentation for the behavior of th
A. The original contributions include: The central idea of DbC is a metaphor on how elements of a softw
B. The contracts for a module can be regarded as a form of software documentation for the behavior o
C. This can be summarised by the "three questions" that the designer must repeatedly answer in the co
D. However, DbC considers these contracts to be so crucial to software correctness that they should b

42. The advantage of internal self-tests is that they can detect errors before they manifest themselves as in
A. These specifications are referred to as "contracts", in accordance with a conceptual metaphor with t
B. The advantage of internal self-tests is that they can detect errors before they manifest themselves a
C. The term was coined by Bertrand Meyer in connection with his design of the Eiffel programming lang
D. The notion of a contract extends down to the method/procedure level; the contract for each method
43. Eiffel Software applied for trademark registration for Design by Contract in December 2003, and it was
A. Eiffel Software applied for trademark registration for Design by Contract in December 2003, and it w
B. This can be summarised by the "three questions" that the designer must repeatedly answer in the co
C. The notion of a contract extends down to the method/procedure level; the contract for each method
D. More often than not, the supplier throws an exception to inform the client that the precondition has b

44. The use of assertions can be considered to be a form of test oracle, a way of testing the design by con
A. The term was coined by Bertrand Meyer in connection with his design of the Eiffel programming lang
B. Asserts are by default compiled away in release mode in C/C++, and similarly deactivated in C# and
C. The contracts for a module can be regarded as a form of software documentation for the behavior o
D. The use of assertions can be considered to be a form of test oracle, a way of testing the design by c

45. Launching the Python interpreter with "-O" (for "optimize") as an argument will likewise cause the Pytho
A. Launching the Python interpreter with "-O" (for "optimize") as an argument will likewise cause the Py
B. It prescribes that software designers should define formal, precise and verifiable interface specificati
C. All class relationships are between client classes and supplier classes.
D. The notion of a contract extends down to the method/procedure level; the contract for each method

46. The contracts for a module can be regarded as a form of software documentation for the behavior of th
A. Where this assumption is considered too risky (as in multi-channel or distributed computing), the inv
B. However, DbC considers these contracts to be so crucial to software correctness that they should be
C. The contracts for a module can be regarded as a form of software documentation for the behavior o
D. The DbC approach assumes all client components that invoke an operation on a server component

47. Design by contract has its roots in work on formal verification, formal specification and Hoare logic.
A. Languages that implement most DbC features natively include: Additionally, the standard method co
B. Design by contract has its roots in work on formal verification, formal specification and Hoare logic.
C. The contracts for a module can be regarded as a form of software documentation for the behavior o
D. Design by contract (DbC), also known as contract programming, programming by contract and desig

48. Design by contract also defines criteria for correctness for a software module: Design by contract can a
A. Design by contract (DbC), also known as contract programming, programming by contract and desig
B. In many programming languages, contracts are implemented with assert.
C. Design by contract also defines criteria for correctness for a software module: Design by contract ca
D. Contracts can be written by code comments, enforced by a test suite, or both, even if there is no spe
49. DbC's "fail hard" property simplifies the debugging of contract behavior, as the intended behaviour of e
A. The advantage of internal self-tests is that they can detect errors before they manifest themselves a
B. Design by contract does not replace regular testing strategies, such as unit testing, integration testin
C. Design by contract also defines criteria for correctness for a software module: Design by contract ca
D. DbC's "fail hard" property simplifies the debugging of contract behavior, as the intended behaviour o

50. However, DbC considers these contracts to be so crucial to software correctness that they should be p
A. However, DbC considers these contracts to be so crucial to software correctness that they should be
B. Design by contract (DbC), also known as contract programming, programming by contract and desig
C. The use of assertions can be considered to be a form of test oracle, a way of testing the design by c
D. This approach differs substantially from that of defensive programming, where the supplier is respon