I've worked under both MIL STD 2167 and ISO9000 and I can say their both a waste of paper. I haven't looked at TDD but it sounds the same. The best way to ensure high-quality good is to hire excellent programmers. But since you can't always do that, I recommend that you work on the interface design first.

Every piece of software, whether it's a subroutine, module, object, or script, has an interface, either an API or a user interface. Getting it done first gives you a good idea on how to proceed. And once it's done, you can split the work into two: one to write the tests; one to write the code, trying to keep them independent. That way, you have two options on what the interface means and, hopefully, you can catch more bugs that way.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.