The Art Of Software Development (part 4): Delivering Quality (
Page 1 of 7 )
Just writing code isn't enough - you also need to test it
thoroughly before you release it to a customer. This article discusses
the testing phase of the software development cycle, providing you with
an overview of test cases and testing processes, together with a
discussion of how to go about documenting your software in a clear and
concise user manual.If you've been following along, you now know all about the first three
phases of a software development project: requirements analysis,
software design and implementation. But in case you thought your job
ended with the completion of the code, think again - you've still got a
way to go before you can call it a wrap.
In this fourth article of a five-part series, I'm going to be spending
some time discussing what happens *after* you've finished writing the
code that meets your customer's requirements. I'll be discussing the
various types of testing your code must go through, providing you with a
brief overview of how test cases should be prepared and software
problems should be reported, and explaining how software is released to
a customer. I'll also be discussing that bane of developers everywhere -
documentation - with some tips and tricks that might make the process
more painless. So let's get started.
/ 4 
