CMPT 376 (Spring 2008): Assessment of Test-Driven Development---Final version

Turn in: A six-page single-spaced recommendation. Once again, you will submit a PDF electronically. It perhaps not be submitted via WebCT, given that webCT's in the 376 doghouse at the moment. I'll give detailed submission instructions as the deadline nears.

Instructions

Now that you have an initial understanding of test-driven development (TDD), together with a recommendation on whether the organization should use it, you can write the final recommendation.

I'm asking you to decide on a structure for the documnt (we'll likely work on this in class at some point). You'll want your document to answer the following questions:

• Briefly, what is TDD?
• Do you recommend that it be adopted or not by your organization?
• How well does TDD fit your team?
• If you recommend TDD, what form do you recommend? What kind of granularity? If you do not recommend TDD, briefly mention what alternative you prefer.
• If you recomend TDD, are there any software libraries you'd specifically recommend? If you do not recommend TDD, are problems with the libraries one the reasons?
• In addition to the above, what are the general advantages and disadvantages of TDD?

In many organizations you would start the recommendation with an executive summary. Because writing an executive summary requires special skill, I'm not going to ask for it in this assignment. We'll add that feature in later assignments.