1. Rensselaer Polytechnic Institute David Goldschmidt, Ph.D.

2.  Software is usually a team effort requiring coordination amongst team members  Document your project goals, user requirements, timelines, milestones, task lists, test cases  via a blog, wiki, Google docs, Briefcase, etc.

3.  Good (and up-to-date!) documentation is crucial to the success of a project  however, too much documentation is not good!  Version control provides benefits to both teams and one-person projects  one-person projects often become team projects

4.  Identify and document coding standards for:  Coding/indentation style  Naming conventions  Commenting styles (e.g. comment headers)  Safe approaches to programming  See http://www.gnu.org/prep/standardshttp://www.gnu.org/prep/standards  Code reviews are invaluable for improving the quality of your software

5.  As software systems grow in terms of usage, scope, scale, user-base, reliance, etc., they must be maintained  Important aspects of quality software:  Maintainability  Maintained!  Usability (testing)  Extensibility  Reusability  Consistency  Reliability  Generalization (design)

6.  http://www.cs.rpi.edu/research/groups.html http://www.cs.rpi.edu/research/groups.html