Once developers turn in the final product to their client, their job is not over. As people begin using the software, they will run into situations the developer did not consider during testing. They will need to go back and correct errors in your code. This is the primary reason why it is important to write well documented, modular code. [Modular coding is where developers break up code into "functions" that handle parts of the program instead of cramming it all together. EX: a calculator will have separate 'add', 'subtract', 'multiply', and 'divide' functions.]
When a program is liked and used by many people, they are very likely to request new features. Developers will have to push the existing code to function beyond its previous capabilities and find ways of adjusting it to handle these needed capabilities.
Previous StepThis program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, look on the web at on the web at http://www.gnu.org/copyleft/gpl.html or write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
To contact the director of the S2S Project, send email to Vicki L. Almstrum, almstrum@cs.utexas.edu or write to her at The Department of Computer Sciences C0500, The University of Texas at Austin, TAY 2.124, Austin, TX, USA 78712.