'test-first' software development
I am always interested in techniques for designing and implementing software.
For all but the smallest projects, I like to start out with some "light weight" UML design - specifically, I find use case diagrams and sequence diagrams to be well worth the effort to produce and keep up to date during development.
'Test-first' development is getting more popular, and I think that this approach works well with producting UML use case diagrams: go directly from use case analysis to specifying tests that the software must pass (implemented in JUnit for Java, SUnit for Smalltalk, etc.)
Note: as my collegue David Young recently pointed out: sequence diagrams are a great visualization tool for spotting possible points of failure in a system - so, they too are useful in moving directly into writing test cases.
10:11:43 AM 
|
