16.01.2015 Views

CS2013-final-report

CS2013-final-report

CS2013-final-report

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Proposed Curricular Revisions<br />

Although the 2012-2013 CS major and curriculum had many strengths, on-going review<br />

identified possibilities for improvement in two substantial ways: the division of some 4-credit<br />

courses into 2-credit courses could provide students with opportunities for more breadth in the<br />

major, and the design of some of those courses could reflect the evolution of the discipline as<br />

represented by CS 2013. The 2-credit courses are likely to meet 1.5 hours per week for the full<br />

semester, although we are also considering half-semester courses.<br />

Full implementation of a substantive major and curricular revision requires substantial<br />

brainstorming, analysis, attention to detail, review, and consultation. The following comments<br />

suggest directions for revised courses and major; adjustments and refinements are likely as<br />

planning and development continue.<br />

Rather than fitting a full range of software engineering topics into a single, required, 4-credit<br />

course, one 2-credit course could highlight concepts, principles, and methodology, and a<br />

second 2-credit course could allow teams to address community needs. The second<br />

course would permit students to join on-going projects for one or more semesters, taking<br />

on more advanced roles in subsequent semesters. Core HCI topics could be incorporated<br />

in one or both of these courses.<br />

A 4-credit elective on computer networks could be split into a more focused, 2-credit<br />

networks course, and a new 2-credit course on computer security<br />

Many SP topics could be covered through the department's weekly seminar presentations or<br />

through an on-going CS table series of discussions. In particular, an annual presentation<br />

and discussion will focus on issues of intellectual property.<br />

Because the multi-paradigm introductory sequence exposes students to many basic<br />

conceptual issues in programming languages, the upper-level course on programming<br />

language can be relatively flexible. Elements of the existing programming languages and<br />

compilers course could be combined into a single 2-credit, interpreter-based<br />

“programming language implementation" course.<br />

Students who take CSC 211 encounter fewer Core-Tier1 topics than those who take CSC 213<br />

because the AR knowledge unit contains primarily Core-Tier2 topics. The CS faculty<br />

considered combining CSC 211 and 213, which some schools have done. However, the<br />

current courses provide good depth, and thus seemed appropriate in the revised<br />

curriculum.<br />

Since Grinnell's liberal arts context limits major requirements to 32 credits, a minimal major can<br />

cover numerous, but not all, learning outcomes recommended by CS 2013. As noted above,<br />

many SP topics can be covered in the weekly department seminar and/or in a reading group<br />

associated with a weekly CS Table. Also, while many IM learning outcomes fit well within a<br />

liberal arts context, a few seem less appropriate.<br />

Advising can encourage students to cover a wide range of topics. The following listing illustrates<br />

possible major requirements and also advising recommendations that could extend a program to<br />

about 38 credits, plus supporting mathematics. The CS faculty will continue to offer a variety of<br />

electives.<br />

- 482 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!