specifications - Caltech

More documents

Recommendations

Info

Specificand Sets• For any specification (of a procedure) consider the set of allprocedures that satisfy it.– Almost always either empty (not useful) or infinite.• Example:/** REQUIRES: x >= 1* EFFECTS: Returns some y where 0 < y = 1, 0 < f(x)
Specificand Sets• For any specification (of a procedure) consider the set of allprocedures that satisfy it.– Almost always either empty (not useful) or infinite.• Example:/** REQUIRES: x >= 1* EFFECTS: Returns some y where 0 < y = 1, 0 < f(x)
Page 1 and 2: CS 3Introduction to Software Engine
Page 3 and 4: Announcement• Welcome to second
Page 5 and 6: Specifications“logical firewalls
Page 7 and 8: Where Specs Come From• Interpreta
Page 9 and 10: Where Specs Come From• Scenario I
Page 11: Specificand Sets• For any specifi
Page 15 and 16: Changing Specificands/** Returns so
Page 21 and 22: Changing Specificands/** REQUIRES:
Page 27 and 28: Stronger/Weaker• Let S and T be s
Page 29 and 30: Restrictiveness• Client must work
Page 31 and 32: Specifications and Correctness• A
Page 33 and 34: Correctness of Client Code• Most
Page 35 and 36: Correctness of Client Code• Judge
Page 37 and 38: Integration• True or false?If eac

specifications - Caltech

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?