Computer Science Curriculum Workshop

Wednesday–Friday, July 17–19, 2013

Agenda Versions: Pre-workshop agenda Revision for Thursday Revision for Friday
  Time Main Topic Starting Activities/Questions Links
Day 1: Theme: Feedback from Interviews and Surveys 9:00 Review of department activities, goals, and priorities
  • Review goals of this workshop
  • Clarify workshop products (e.g., report) and audiences (e.g., CS faculty, Dean's Office, other faculty, NCA)
  • Review agenda
 
9:30 Departmental activities and organization
  • Develop a list of various jobs and activities in the department
  • Review who does what
 
10:00 Exit Interviews
  • Reporting of responses from 2013 exit interviews
  • What themes can we identify?
11:50 Announcements
  • Change in format/approach for CS2013 template spreadsheet
  • Reminder: Need nominations for students for Iowa Women of Innovation
  • Schedule for Iowa Private College Week: August 5-9; tours of Science building in morning and afternoon daily
  • Screening of Codebreaker film scheduled for Friday, October 11, at 7:00 pm;
    how to organize question and answer session
  • Contributions for CS Computer Museum
    • from Nathaniel Borenstein
    • from Bob Cadmus
  • Admission talk on CS on July 24 at 10:00
  • Feedback welcome on Noyce Fun Facts for Admission
 
Homework Review alumni/ae surveys from 2008-2010 Identify themes, highlights Distributed by Sam via email
Day 2: Theme: Review of Current Course Content 9:00 Themes from Exit Interviews and Alumni Surveys
  • What themes can we identify from exit interviews and alumni surveys
  • What topics do we seem to be covering well?
  • What new or different topics should we consider?
  • What additional themes do alumni suggest?
Notes from Wednesday's discussion
9:30 Mapping Grinnell's curriculum to CS2013
  • General review of all courses
  • Detailed work on CS2013 spreadsheet
  • Review of draft CS2013 spreadsheet
Working Lunch Email on MathLAN Discussion of Policies, Procedures, Adjustments
Bulletin boards
  • What needs to be displayed (departmental materials, SEPC, announcements, posters, others?)
  • How much space is really needed?
  • Constraints
  • Options
Academic Honesty policies and practices
  • What practices do we follow?
  • What recent issues have we encountered?
  • How should we handle citation of individual versus collaborative procedures?
  • How can we clarify and enforce rules for individual work on assignments?
  • How can we distinguish between rules for labs and rules for other activities (when we want to make those distinctions)?
  • Do we/should we have concerns related to contract cheating?
 
  Additional Topics as Time Permits
  • Status of tutors, mentors, assistants for 2013-2014
  • Schedule for LACS
  • Regularizing Computer Vision course
  • Hanging new art work
  • Possible use of ACM authorize option for published-paper access
  • Ongoing discussion of helping students feel/be included in group work
  • Academic Honesty statements for various courses
Homework Continue work on CS2013 Spreadsheet Full review of courses will likely continue through the 2013-2014 academic year Send Henry spreadsheet entries for courses, as they become available
Day 3: Theme: Possible New Directions 9:00 Projects in the CS Curriculum
  • Should projects span over 2 semesters?
  • Should projects be 2 credits/semester or 4 credits?
  • Should projects extend over multiple semesters with multiple groups?
  • Should MAPs be allowed to count toward the project requirement?
10:00 The major requirement in systems
  • Should there be a 1-semester systems course introducing concepts of both architecture and operating systems?
  • Should concurrency be a separate 2- or 4-credit course?
  • Where might issues of networking fit within the systems requirement?
  • Where might issues of security fit within the systems requirement?
11:00 The major requirement for languages
  • What are our goals for our language requirement?
  • How much formalism should be included?
  • Should scripting languages have a more central role?
  • Should event-driven problem solving be emphasized somewhere?
  • Should parallel languages be emphasized?
11:30 Identification of next steps
  • What, if any, changes do we want to make short term? long-term?
  • Are there areas for which we need additional discussion?
  • Who wants to do what?