I. OBJECTIVES, OUTCOMES and ASSESSMENT A ... - pace university
I. OBJECTIVES, OUTCOMES and ASSESSMENT A ... - pace university
I. OBJECTIVES, OUTCOMES and ASSESSMENT A ... - pace university
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
testing tools. As a result, JBuilder was adopted for the Java programming<br />
classes (CS121 <strong>and</strong> CS122) <strong>and</strong> for the data structures <strong>and</strong> algorithms classes<br />
(CS241 <strong>and</strong> CS242). We have since switched to Eclipse. The capstone class in<br />
software engineering (CS389) introduces JUnit <strong>and</strong> Subversion. Another<br />
recommendation was for each student to experience the collaborative analysis,<br />
design, construction, <strong>and</strong> testing of a piece of software for solving a problem with<br />
no direct solution. This was fulfilled in September 2002 when CS389, the<br />
project-based software engineering seminar, became a requirement of new<br />
matriculants. These recommendations worked together to contribute to the<br />
achievement of outcomes a, b, c, d, h, i, j, <strong>and</strong> k.<br />
The report is on display in the Goldstein Academic Center, room 314.<br />
Curriculum Improvements Resulting from Assessment<br />
There have been a number of assessment-based changes made to the<br />
curriculum <strong>and</strong> the student environment since the program's accreditation was<br />
last renewed. The first-order improvements, <strong>and</strong> most palpable, have been to<br />
the computer science courses required for graduation. Annual changes are<br />
documented in the students' worksheets. Worksheets enumerate the graduation<br />
requirements for that year's matriculants (entering freshman <strong>and</strong> transfer<br />
students). The Undergraduate Catalog shows these changes as well but with<br />
less chronological granularity because the Catalog is published only every other<br />
year. Table 1.4, below, summarizes these changes.<br />
Table 1.7 Assessment Based Curriculum Improvements<br />
Assessment Action<br />
Change<br />
Effective<br />
Academic Program Review;<br />
Advisory Board<br />
CS389<br />
Software Engineering was changed from an elective to a degree requirement<br />
Fall 2002<br />
Advisory Board; Curriculum CS388<br />
Committee; Student Opinion<br />
Survey<br />
Data Communications was changed from an elective to a degree requirement<br />
CS362<br />
Fall 2002<br />
Advisory Board; Curriculum<br />
Committee<br />
Programming Languages <strong>and</strong> Implementation II (compiler) was removed as a<br />
requirement to allow for the addition of CS389; course was discontinued; topics<br />
from compiler construction were integrated into CS361<br />
CS231<br />
Fall 2002<br />
Advisory Board; Curriculum<br />
Committee<br />
Computer Organization I (assembler) was removed as a requirement to allow<br />
for the addition of CS388; course was discontinued; PHY109 was made a<br />
requirement<br />
PHY109<br />
Fall 2002<br />
CS Curriculum Committee<br />
Digital Electronics was changed from a possible science electives to a course<br />
requirement to supply coverage of gates, adders, registers, <strong>and</strong> instruction<br />
decoders that was lost with the removal of CS231<br />
CS488<br />
Fall 2002<br />
Advisory Board Computer Networks <strong>and</strong> the Internet replaced CS388 as a degree requirement;<br />
CS388 remains available as an elective<br />
Fall 2005<br />
Advisory Board; Course CS271<br />
Opinion Survey; Curriculum UNIX (re-titled: UNIX <strong>and</strong> C) was changed from a<br />
Fall 2006<br />
Committee<br />
one-credit class to two credits; coverage will include C<br />
26