Report on Undergraduate Forum of March 22, 2017


The CSE Undergraduate Studies Committee (UGSC) organized the annual undergraduate forum on March 22, 2017 in BE 180. The forum started at about 5:30 pm and continued till about 6:45 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. The summary is based on notes made by Paolo Bucci and Jeremy Morris; many thanks to both for taking detailed notes.


Attendees:
Students:
Glen Gainer.25
Brian Gainer.34
Ernest Parke.26
Shyam Thiagarajan.12
Anshu Kumar.472
Jeremy Kaufman.405
Yihang Du.376
Stephen Wu.2719
Courtney Campbell.1807
Edrienne Co.11
Emily Engle.165
Winnie Li.3899
Jiway Kim.6323

Faculty: Matthew Boggus, Paolo Bucci, Doreen Close, Mike Fritz, Michael Green, Wayne Heym, Jeremy Morris, Neelam Soundarajan, Paolo Sivilotti, Rafe Wenger, Annatala Wolf

Advising staff: Leslie Dowler, Nikki Strader, CA Wade

Systems staff: Dave Kneisley

Summary of discussion:

  1. Neelam briefly welcomed everyone to the forum, explained the purpose of the forum, and explained the activities of the Undergrad Studies Committee and the Curriculum Committee. Following that, everyone in the room introduced themselves.

  2. Rafe Wenger (who is Associate Chair for the dept. and is responsible for determining how many sections of each course to offer in each semesters and for assigning them to suitable faculty) talked about waitlists for the courses, etc. All majors who schedule their CSE courses when their registration windows open have been able to get into the courses. The few exceptions are with respect to courses that are intended to serve both CSE graduate students as well as undergraduate students such as CSE 5523, Machine Learning. Rafe noted that we are trying to recruit faculty who can teach additional sections of these high-demand courses. Students at the forum did not report any case of being closed out of a course if they scheduled when their registration window opened.

    One point worth noting is that students following a particular specialization option do not have any special priority for courses related to or recommended for that option. It was also noted that CSE 5914, the capstone course based on the Watson system, while it is recommended for students pursuing the AI specialization option, does not "count" as part of the option. This is to ensure that students following this option actually take at least three courses that discuss key AI concepts (whereas 5914 is primarily focused on using the Watson system to build interesting application(s)). (Similarly 5911 doesn't "count" for the Software Engineering option.)

  3. Specific courses of interest:

  4. Why CSE 2501/Phil 1338 is required: Some students felt that CSE 2501 was not really useful and questioned the need for it in the curriculum. Neelam noted that the (ABET) accreditation criteria for the BS-CSE program require that students in the program acquire an understanding of professional, ethical, legal, security and social issues and responsibilities. The criteria also require students to acquire an an ability to communicate effectively with a range of audiences. CSE 2501 and Phil 1338 are designed to help meet these requirements. And even apart from the accreditation requirements, these are important outcomes that students should achieve as they go through our program so that they are well prepared for their professional careers. As a related point, one of the program educational objectives (PEOs) of the BS-CSE program has, for a long time, required, in part, that graduates of the program will be "... responsible engineering and computing professionals". During the last meeting of the department's Advisory Board (which consists of our alumni and distinguished people from a number of corporations) suggested that we might want to add, to that objective, a reference to the ACM/IEEE Code of Conduct which is part of the discussion in both CSE 2501 and Phil 1338. The capstone courses help students further refine their communication skills; and also, depending on the particular project, give an opportunity to students to explore the ramifications of ethical and professional issues in the context of the project. There was also a brief discussion of the accreditation criteria.

    Winnie Li pointed out that some of the other ABET outcomes require students to be able to function in diverse teams and, more broadly, to be familiar with diversity-related issues. CSE 2501/Phil 1338 contribute in important ways toward these outcomes. Winnie mentioned that a number of students (all members of ACM-W) have been working with the advisors to introduce some discussion of these issues Eng 1100, the survey course that all (engineering) freshmen take. Wade argued that the discussion of diversity and related issues should, preferably, continue through the curriculum so that the ideas are reinforced. Toward this end, Winnie promised to put together a collection of resources on the topic that would be avilable to faculty in more advanced courses to ensure that students in those courses to present to students, as the opportunity arises. This should help improve the extent to which (both CSE and CIS) students achieve these outcomes that are important for success in an increasingly diverse society. Thus although CSE 2501 and Phil 1338, as well as the planned discussion in the survey course etc., do not have the technical content that most CSE courses do, they play an essential role in preparing students for their professional careers.

  5. Possible new courses: Given the wide range of new tools, technologies, and practices that have been introduced in the last few years, many of which are in wide use in industry, Neelam raised the question of whether any of our courses should include discussion of any of them and, if so, which course(s). A key problem, of course, is that it is hard to predict which of these items have staying power and which are likely to disappear after a short while; moreover, the wide range of available items means that no single or handful of courses would be appropriate. An alternative that we have considered is the 5xy9 model; i.e., a 2-credit course whose contents will likely change (with the tools/technologies) from one offering to the next and that deals with a number of these items, possibly related to very different topics. Most students liked the idea of a 2 cr. hr course on new technologies and tools and suggested a number of topics that would be appropriate (e.g.: Node+React; VR/AR; Maven, Gradle, ..; Deep learning, Tensor flow; etc.)
    But there are a number of questions to address before such a course can be implemented, the most important one being, who would teach the course? Most of our regular faculty would probably not be able to talk effectively about more than a handful of these tools and techniques. One possibility here would be to have an industry professional or several industry professionals teach the course; for example, perhaps three people with interests in and knowledge of a range of these specific tools/techniques could team-teach the course with each person teaching for 4-5 weeks of the semester. This will enable the students in the course to get exposed a fairly wide range of current tools and techniques. We will explore these possibilities.
    One of the advisors noted that since most of our tech elective courses are 3 credit hours each and since students are required to take 17 hours of tech electives, a 2 cr hr. course would fit well with that.

  6. Bulletin board for announcements: One of the ideas that was proposed at last year's forum was the creation of a bulletin-board like facility that would list, in reverse chronological order, announcements that may be of general interest to our majors. Currently, these are sent out by email to the student mailing list but often, apparently, get overlooked in the deluge of emails that students receive. Having a specified place that archives the announcements in an easily accessible fashion would help address this issue and, indeed, was why it was proposed last year. Unfortunately, because of pressure of various other activities, this has not been implemented. We will work on getting this done in the near future.

If you have any comments or questions on this report, please email Neelam (soundarajan.1).