On Wed, 27 Oct 2004 14:45:29 -0500, Brad Appleton <[EMAIL PROTECTED]> wrote:
> Could someone help me out by clarifying for me what the
> difference would be between Assertion-Driven Development
> (ADD) and Design-by-Contract (DBC)? (and how, if at all,
> do you feel DBC is different from TDD)
"ADD" is just a try-this-on-for-size alternate name for TDD, just to
get away from the term "test."
I think the difference between TDD and DBC is where the assertions are
located. My recollection may well be faulty, but I have the idea that
DBC places assertions in the code itself, using them at runtime to
verify that callers are obeying preconditions, and that methods called
preserve invariants and obey postconditions.
TDD places assertions in external code, and relies on the need to
satisfy those assertions to motivate the writing of the production
code. It does not necessarily worry about preconditions and
invariants, although it could.
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
