The Hero Contract Scenario
The image illustrates Design by Contract (DbC) using a hero analogy. It defines three logical constraints: a Precondition where the hero must have web fluid before swinging, a Postcondition guaranteeing a web line attaches if fluid was present, and a Class Invariant requiring the hero’s mask to stay secure throughout the entire combat process.
The first panel in the image above contains a scenario description: "If the hero jumps with 'empty' shooters, the 'shooter' is not required to save him." This specific detail illustrates which core philosophy of Design by Contract?

Question

The Hero Contract Scenario

The image illustrates Design by Contract (DbC) using a hero analogy. It defines three logical constraints: a Precondition where the hero must have web fluid before swinging, a Postcondition guaranteeing a web line attaches if fluid was present, and a Class Invariant requiring the hero’s mask to stay secure throughout the entire combat process.

The first panel in the image above contains a scenario description: "If the hero jumps with 'empty' shooters, the 'shooter' is not required to save him." This specific detail illustrates which core philosophy of Design by Contract?

Answer

Fail-Fast (the system must not attempt to recover from a contract breach).

Answer

Loose Coupling (interfaces cannot enforce numeric constraints on parameters).

Answer

Encapsulation (method details must be completely hidden from the caller).

Answer

Polymorphism (preconditions must automatically adjust based on the type of hero).

Answer

Defensive Programming (the supplier should always handle user error safely).

Crowdly

The Hero Contract Scenario The image illustrates Design by Contract (DbC) u...

Want instant access to all verified answers on learning.monash.edu?