Graduate Handbook

The Master of Computer Science (MCS)

The MCS is a course-based program for individuals who seek to enhance their careers with advanced knowledge of computer science. The requirements described here are in addition to the University-wide requirements for master's degrees described in the Manual of Rules and Regulations of the Graduate College, Section X.

Course Requirements

The MCS requires a minimum of 32 semester hours of coursework beyond the bachelor's degree.

Theory Requirement

All MCS students are required to take one of the following for a total of 3 semester hours:
      22C:131 Limits of Computation
      22C:135 Theory of Computation
      22C:231 Design and Analysis of Algorithms

Systems Requirement

All MCS students are required to take one of the following courses for a total of 3 semester hours. New or alternative offerings may, from time to time, be designated as also satisfying this requirement.
     22C:160 High Performance Computer Architecture
     22C:166 Distributed Systems and Algorithms
     22C:181 Formal Methods in Software Engineering
     22C:185 Programming Language Foundations
     22C:186 Compiler Construction

Colloquium Requirement

All MCS students must accumulate at least 2 semester hours of 22C:399, the CS colloquium series. Students enrolled in 22C:399 are graded S/U. The Department will offer approximately 10 talks each semester; of these, students must attend at least seven talks to get a satisfactory score for the course. (Note: if, for some reason the Department schedules significantly more or significantly less than 10 talks in a semester, the required number of talks that must be attended may be changed for that particular term.)

Elective Courses

MCS students should fill the remaining semester hours with a combination of directed readings, CS graduate courses, and non-CS graduate courses approved by their advisor and subject to the following constraints:

• at least 6 courses (18 semester hours) of “didactic” (any CS course numbered 22C:120 or greater, excluding 22C:191, 22C:197, 22C:290, 22C:299, and 22C:399) CS graduate-level courses;
• at most 1 CS graduate-level “readings” course (22C:197 or 22C:290); and
• at most 2 non-CS graduate-level technical courses (approved by advisor).

Software Engineering Subtrack

The Computer Science Department, with the Electrical and Computer Engineering Department, offers a subtrack in software engineering within the MCS program. Students completing 22C:180 (Fundamentals of Software Engineering), 22C:181 (Formal Methods in Software Engineering), 22C:182 (Software Engineering Languages and Tools), and 22C:183 (Software Engineering Project) receive a special designation on their transcript. See the Graduate Program Administrator to file the appropriate paperwork when applying for the degree at graduation.

Final Semester/Graduation

Besides the Application for Degree, MCS students should complete a Non-Doctoral Plan of Study Summary Sheet, found on the Graduate College website at http://www.grad.uiowa.edu/Pubs/Forms/index.asp, with the help of the Graduate Program Administrator and filed by the appropriate deadline.

Residency Requirement

The Graduate College has additional explicit residence requirements that must be satisfied in order to obtain the MCS. For full details, see the Manual of Rules and Regulations of the Graduate College, Section X (D).

Academic Standing

To remain in good standing, an MCS student must demonstrate academic progress in their coursework. The faculty will meet each spring to review all aspects of each student's progress towards a degree, with student standing ultimately determined by the faculty.

MCS Plan of Study Form

Each student is responsible for maintaining an up-to-date MCS Plan of Study document on file with the Graduate Program Administrator. The MCS Plan of Study is used to track student progress throughout the program, and should be updated each semester in collaboration with the student's advisor. It is also used to prepare the Graduate College's Plan of Study summary document when preparing for graduation.

Departmental Probation

A student placed on departmental probation (The Graduate College mandates that each student maintains a minimum cumulative GPA of 2.75 or risk being placed on Graduate College probation (for details, see the Manual of Rules and Regulations of the Graduate College) shall be given a written explanation of the reasons for this action, along with a reasonable period of time (typically one year) within which the student shall take corrective action or be dismissed from the graduate program.

Petitions

Students may submit petitions to the Graduate Program Administrator for deviations from the requirements outlined here.

Academic Integrity

Work outside the classroom on assignments and programming projects plays a particularly important role in the learning process in computer science. It is essential that each student's work reflect his or her own effort. Our department treats cheating seriously. Instructors retain considerable latitude in the penalties they may invoke. For a first offense, an instructor can fail the student in the course. For a second offense, the Department can expel the student from the program. All offenses must be reported to the Department Chair. Students involved in research should understand that it is essential to give proper credit for other people's ideas and work when they present them in their own writing. The University's policy on ethics in research is included in Chapter 27.6 of the Operations Manual and should be thoughtfully considered by any student undertaking research, as well as Chapter IX Student Rights and Responsibilities included in the Student Academic Handbook, published by the College of Liberal Arts and Sciences.

Last modified: September 15, 2008