Reminder: Please put your projects into: /proj/asl/lieber/f95/com3360/ as described below. -- Karl L. ========================================================= repeated message WHAT TO TURN IN AND HOW TO TURN IT IN ===================================== This file is in: /proj/adaptive/www/course/hw/project/projects.txt (on the WWW at http://www.ccs.neu.edu/research/demeter/course/hw/project/projects.txt) Your software will live on even after you graduate provided you have done an ``interesting'' project which will catch the attention of your successors or WWW browsers. It is very important that you leave the software in a form so that later teams can learn about what you did and continue in your footsteps. It is very important that you put your README-project file into the right place as described below so that your successors can find the right pointers to your work. It is important that the file contains the information requested. The project is due on Dec. 4 with some flexibility for late submission. The absolute deadline is Dec. 15. The NTU students have the usual one week extension, unless they have made special arrangements with me. In /proj/adaptive3/projects/com3360-f95 you have created all your great works but the permanent place for your efforts is /proj/asl/lieber/f95/com3360/ So move your project over to this directory into a subdirectory which has the same name as your login name. In this directory, I expect to find your "README-project" file which tells me what you did. See: /proj/asl/lieber/f95/com3360/lieber which contains file README-project The ownership of the directories /proj/asl/lieber/f95/* will change to me with world read access. Remove any information from the disk which you consider private. There is a plan to put the best projects on the WWW as sample applications of adaptive programming. If you explicitly don't want your application to appear on the WWW, please mention this in the first line of your README-project file. I know that some of you have a project of a proprietary nature. Please make special arrangements with me so that only I can read the source. Your personal software process: ======= Write a few paragraphs (at the end of file README-project; see below) which summarizes the approach you used in your project. What was your strategy and which techniques worked best? How did you learn about adaptive software? What was hard about adaptive software? What was hard about the tools? How did you find useful information? This will be useful wisdom for your successors and me! (I can update teaching/tools/documentation.) ======= What you hand in is all electronic. The goal is that the information you hand in will allow other students to build on your projects. You may assume that those students are as educated as you are in object-oriented systems development using class dictionaries and propagation patterns. WHAT TO TURN IN. ================================================ You will almost certainly spend most of your days as a practicing computer professional working in groups. Your effectiveness will depend on your ability to contribute your engineering expertise to those groups. Therefore you had the opportunity in this course (but it was not required) to develop software in groups. You learned about how to bring good members to your group, participating in meetings, partitioning the work etc. To get additional input regarding the grade for your project, I would like you to evaluate your peers (only if you worked in a group). Please answer the following questions in the last week of the quarter, put the answers into an envelope into my mailbox or bring it to class. =============== Project: Your name: Let's assume that the grade for your project is B. Which grade would you give to each of the team members (including yourself)? Why? The evaluation is confidential. It will serve as additional input for assigning a grade. ============= For team projects, turn in only ONE project (one README-project file) and one version of the source code. List all team members on the file. Select the login name of one of the team members to store the project in the specified directory /proj/asl/lieber/f95/com3360/. OPEN YOUR FILES FOR READ ACCESS. For the purpose of grading your projects please use a command such as: chmod -R go+rx xy & for the top directory which contains your project. Make very sure that the top directory itself is accessible to me. --------------------------------------- Include the following information in what you turn in for your project: Put this information into file /proj/asl/lieber/f95/com3360/YOUR_LOGIN/README-project and mail a copy to lieberherr. ---------------------------------------- Your name: ====================================== Your host: (if applicable) ====================================== Account Number: ====================================== Project: (brief description) ====================================== Directory: This is a directory in: /proj/asl/lieber/f95/com3360/YOUR_LOGIN/README-project ====================================== Credits: (from where did you reuse some of the software/ideas in your project? reuse is good as long as you give proper credit. Give directory names and name of person from which you used ideas.) ====================================== (The following is geared towards a C++ project using Tcl/Tk. If you used only Tcl/Tk, adapt what is below. The Ph.D. students who did research project, please turn in your research paper and ignore what is below. The command to run your program and the interface of your command. Give an example how to run your application. ====================================== If it is a C++ program produced by Demeter, use dinstall to create an executable. man dinstall tells you how to install your application. Once you have done dinstall, run make clobber to free disk space! Please leave only useful information in your directory. Useful to your successors but please don't waste disk space. Class dictionary which you used. ====================================== Growth plans which you used, if any. ====================================== Parts of your project which you would have developed further if you had more time. Include a list of known bugs here. (The more bugs you know, the better you have tested your project!) ====================================== Names of files where test inputs can be found. ====================================== Names of files where outputs can be found. ====================================== Include one interesting input/output pair in this file. (well, if your output is graphical, maybe you have some printed form for the graphical information.) ====================================== Include one interesting input/output pair where the behavior of your program could be improved. ====================================== Any information which you think is useful to properly reuse your software. ====================================== Your propagation patterns should contain the following minimal documentation: // brief explanation *operation* void f( Please answer the following questions: Did you change the generated C++ code which make generates from the cd.cd and *.pp files? Did you change the generated Makefile which gen-make produced? I hope not, but if you did, please explain what and why you changed. This is important information for reusing your software. If you had the priviledge to have one of my Ph.D. students as host or if you had interactions with the teaching assistant, an evaluation of their performance would be welcome. ---------------------------------------- It would be useful, if in your subdirectory of /proj/adaptive3/projects/com3360-f95 you could also leave a trace of the most interesting parts of your homework, especially your own class dictionary you developed and the little pps you wrote for it. BE CONSERVATIVE WITH DISKSPACE!