Homework - Practices

With the design out of the way, it's time to finally sit downand write some code. This article discusses the implementation phase ofthe software cycle, outlining some ideas and techniques that should helpyou deliver cleaner, faster and more maintainable code. Miss it at yourperil!

TABLE OF CONTENTS:

By: Vikram Vaswani, (c) Melonfire

Poor Best

Rating:

/ 5

September 12, 2002

print this article

SEARCH DEV SHED

TOOLS YOU CAN USE

That's about all I have time for in this article. In the next part, I'll be discussing how to test the code you've developed, with an overview of unit testing, system testing and acceptance testing procedures. I'll also discuss the process of software delivery and installation, and spend some time on that other bane of developers - documentation. All that and more, coming soon...but until then, here are links to the various software tools discussed in this article:

PHP FastTemplate, at http://www.thewebmasters.net/

Smarty, at http://smarty.php.net/

patTemplate, at http://www.php-tools.de/

CGI::FastTemplate, at http://www.cpan.org/

Cheetah, at http://www.cheetahtemplate.org/

Velocity, at http://jakarta.apache.org/velocity/

Perl DBI, at http://www.cpan.org/

Metabase, at http://www.phpclasses.org/

ADODB, at http://php.weblogs.com/adodb/

Carp, at http://www.cpan.org/

PHP ErrorHandler class, at http://www.phpclasses.org/browse.html/package/345.html

PEAR, at http://pear.php.net/

CVS, at http://www.cvshome.org/

Until next time...stay healthy!

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