Endgame - Practices

Just writing code isn't enough - you also need to test itthoroughly before you release it to a customer. This article discussesthe testing phase of the software development cycle, providing you withan overview of test cases and testing processes, together with adiscussion of how to go about documenting your software in a clear andconcise user manual.

TABLE OF CONTENTS:

By: icarus, (c) Melonfire

Poor Best

Rating:

/ 4

September 24, 2002

print this article

SEARCH DEV SHED

TOOLS YOU CAN USE

Once the software has been formally accepted, all that's left is torelease it to the customer, together with the required documentation.This release may be delivered either on a CD-ROM or via the Internet,depending on the nature of the software. In case you're also supposed toturn over the software source code to the customer, make sure that it'sincluded in your release.

Every release should be prominently tagged with a version number, andshould include a release note which provides information on the release.This release note should include the version number of the softwarebeing released, the release date, and a brief description of the changesin the release (if any). This release note provides both customer andvendor with an easy-to-understand trace of the software release history.

In case the software requires installation, it should be packagedappropriately with an installer; if it's a Web site or Web application,installation typically involves merely placing the files in a specificlocation on the Web server. Either way, specific installationinstructions should be included with your deliverable, either as part ofthe manual or as an additional appendix on the delivery media.

At this point, you've successfully designed, implemented, tested anddelivered a software application to the specified requirements of yourcustomer. All that's left now is to wait for the rest of the cash toroll in, and get ready for what many consider to be the mostcommercially profitable phase of the software lifecycle: softwareupdates. I'll be discussing that in the next (and final) article in thisseries...but until then, lie back and take a well-deserved break. You'veearned it!

Note: Examples are illustrative only, and are not meant for a productionenvironment. Melonfire provides no warranties or support for the sourcecode described in this article. YMMV!