The CSE Undergraduate Studies Committee (UGSC) organized the annual undergraduate forum on Feb. 3, '11 in DL 480. The forum started at about 5:30 pm and continued till about 7:15 pm, with most students staying on till near the end. The summary below tries to describe the main points that were made during the discussions but does not capture the enthusiasm of the participants.
Some more details about courses under semesters: The 221-sequence (plus 421) will be replaced by Software I, II which will use Java (but will continue to have the focus on specifications/design-by-contract etc. that the 221-sequence does). There will be multiple "project" courses (which will replace 560). Students will be required to take one of these courses. For example, one of the proposed project courses will involve GUI design; another will involve web services; etc. The 600-level courses that are currently required of all students will be replaced by four groups of courses with each group containing two courses. For example, one group consists of the replacements for 625 and 655; another consists of the replacements for 675 and 677; etc. Each student will be required to take one course from each group (with the other course being available as a tech elective). All students will be required to take a capstone design course (these being the replacements for the current CSE 758, 762, 731 etc.)
There were some comments about a few of the (current) courses. One student noted that CSE 551 (Information Security) seems to be devoting too much attention to security issues in the Windows (mobile) platform and this may be detracting from the more general conceptual discussion. A couple of students noted that CSE 652 (Inf. Sec. Projects) was a very useful course and provided a lot of practical knowledge and experience. There were some complaints about the 221-sequence to the effect that some relatively simple matters were made unnecessarily difficult without any pedagogical rationale for doing so. (Paolo Bucci who is involved with the sequence tried to address the questions; some changes in the course materials may also be made.)
Another important set of requirements has to do with assessment of the objectives and outcomes using well-defined, documented, processes, the results of the assessments being used to identify possible improvements in the program. We use a number of assessment mechanisms (see this page for details). One of these is POCAT, the multiple-choice exit test that graduating students are required to take. Several students knew about the test and were interested in learning more about it; so we spent some time talking about it. The results of the test have been useful in helping us identify improvements in a number of courses. Comments about our objectives, outcomes, and assessment mechanisms and results, are welcome; please email them to neelam AT cse