1) Read a program that you wrote a long time ago (the older the better) and a recent program. Can you understand the older program? Do you notice any changes in your programming style? Include a copy of the old program and a copy of the recent program you use to answer this question. For each program, explain.
2) Find a program that you wrote (or one assigned by your professor) and analyze it for style. Is it indented correctly? Are the names well chosen? Can it benefit from refactoring? Discuss the issues with your fellow students or with other software developers. Include a copy of the program that you use to answer this question.
3) Consider the seeded defect approach to creating a stop-testing condition and the example in this chapter.
i) After reaching the 70 percent level, suppose that more and more (e.g., twenty) unseeded defects are found without discovering a single new seeded defect. Explain what you think is happening.
ii)After reaching the 70 percent level, suppose that the remaining three seeded defects are found along with only four more real defects. Explain what you think is happening.
4) Describe your level of comfort for quality if a group of software developers tell you that they used test-driven development. Explain why.
