CS 190 Computer Science Design Project Winter 1998

A. Klinger 3531-H Boelter Office (3532-J Mail Slot) Tues/Thurs 8-10 AM Boelter 5272

Course Organization and Administrative Information

Secretary: Mrs. Rita Drew, 3532-F, <gpham@cs.ucla.edu>, 310 825-1322

Now URL: http://www.cs.ucla.edu/~klinger

Old URL: http://www.cs.ucla.edu/csd-lanai/fweb/cs190

___________________________________________________________________________________

Objectives: Learning to work in a group and set one's own goals. Developing 1) skill at transmitting ideas, and 2) fundamental ethical standards. Acting to innovate and to accomplish things in computer hardware, software, or analytic-models. Enabling students to share their knowledge.

Talks and Reports: Each person gives three or more individual talks to the class: at least two are on the project tasks he/she undertakes. There are many types of first presentations. One can explain a project idea, possibly with the goal of recruiting partners. A book on an issue in the professional development area, a new aspect of computing, or information found from a web site, can be the basis of a talk. Since practice and process are the issues here, a talk can really be about any topic of interest to computer science students: people have used JAVA, registering domain names, CGI scripts, and many other things as subjects. Still most of the talks should describe what you have done in your project design or to develop professionally this quarter. At least one talk must show something you have done. A very good way to do that is focus on preparing figures, graphs or tables before the talk. Then either by xeroxing them or developing film transparencies you can get your peers to look at your results while you speak about them.

Activities and Grades: Developing a personalized ten-week plan of objectives. Selecting reading material. Choosing a project. Creating a common, jointly-prepared/approved work effort culminating in preliminary and final reports and a briefing. Attendance and active participation at course meetings. Contributing to other projects. by comments at talks, and reviews of progress reports and paper drafts. Course grades reflect team results, initiative and work quality; and individual participation.

___________________________________________________________________________________

Initiating a Project: The first three weeks begin with team formation and project selection. Project teams of three or four members begin to address combining different visions of what will be done. Teams can work on coordinated projects, or do the same project independently. Student-originated projects must have instructor-approved of their written description, deliverables, and specifications.

Requirements:

1. Work with partners to create two high-quality written project reports.

2. Read, write, and compute. Distill that work into presentation material.

3. As an individual prepare and give presentations to the class.

4. Write an individual weekly progress report.

5. At course conclusion submit a letter describing the group experience.

6. Participate in all evaluation activities and serve as a responsible commentator and reporter re class meetings.

Presentations: The course work involves discussions and talks. Students ask questions about, and comment on, each other's work. Numerous course handouts, reports, figures, suggestions on giving talks, and material on computer innovation appear in the course web site. Everyone must give a talk. from new visuals composed for that purpose. [Students can use computer visual preparation software.]