Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!fluke!ssc-vax!dickey
From: dickey@ssc-vax.UUCP
Newsgroups: comp.edu
Subject: Re: software engineering
Message-ID: <1191@ssc-vax.UUCP>
Date: Wed, 15-Apr-87 15:38:39 EST
Article-I.D.: ssc-vax.1191
Posted: Wed Apr 15 15:38:39 1987
Date-Received: Fri, 17-Apr-87 05:37:56 EST
References: <340@ndsuvax.UUCP> <1986@cwruecmp.UUCP> <427@applix.UUCP>
Organization: Boeing Aerospace Corp., Seattle WA
Lines: 16
Summary: documenting programs

In article <427@applix.UUCP>, dan@applix.UUCP (Dan Pierson) writes:
> Has anyone tried to drive home the importance of design and documentation by
> forcing students to significantly modify someone else's project?  This could
> be done either by trading projects in mid-course or by giving students in one
> course the final project from a previous (possibly different) course as a 
> starting point.





When I was a computer science TA, I used to make a big deal about
commenting programs. Once, I had a student turn in a program with so
many comments, I had a hard time finding the program.

=========>