Answers to the questions students ask me most often about the Computer Science major: how the degree fits together, what order to take things in, and where to go when something goes wrong. If your question isn't here, email me.
Bo Sheng · Undergraduate Program Director · Department of Computer Science
Both are real Computer Science degrees with the same foundation. The BS is the more technical and more structured of the two, and it's what most of our students do.
The default choice · ABET-accredited
More flexible · room for a second field
Both degrees also require 120 total credits, at least 30 of them taken at UMass Boston, a 2.0 GPA in the major and a 2.0 overall, and at least six 300-, 400-, or 600-level CS or Math courses completed here. There are no exceptions to any of those. The BS requirements shown above apply to students who declared in Spring 2023 or later.
The College of Science and Mathematics Student Success Center maintains semester-by-semester plans to graduation for both degrees. Start from these when you're mapping out your years, then adjust with your advisor.
PDF Updated September 24, 2025
DOCX Updated September 24, 2025
These are samples. Your own path will differ based on transfer credit, placement, and how many courses you take per semester. That's fine, as long as you don't break the sequencing rules below.
This is the rule most likely to cost you credit you've already earned, and it's the one students most often haven't heard of. Please read it once, carefully.
If two courses are in sequence and you earn credit for the earlier course after the later one, you lose the credit for the earlier course. For example, a student who takes CS 310 and then, in a later semester, takes CS 210 loses the CS 210 credit.
CS 310 is a prerequisite for CS 444, but the two are not in sequence. So a student who takes CS 444 and then CS 310 later keeps the CS 444 credit. Still a bad idea, but not a credit-losing one.
You can take two consecutive sequenced courses in the same semester without breaking the rule, because the later credit isn't received strictly before the earlier one. That's a technicality rather than a plan. I strongly recommend against it, especially for the early courses.
CS 110 and CS/IT 115L are listed in both directions, which looks odd until you know the history: CS 110 was once offered as a split pair (114L + 115L) for students who wanted to take it more slowly. They cover the same ground, so whichever you take second is the one whose credit is lost. Treat them as alternatives, not as two courses you can stack.
This is the long one, and the one that catches the most students. CS 110 → CS 210 → CS 310 → CS 410 is common to every version of the chain.
WISER does not block a registration that violates a sequencing rule. It is your responsibility to make sure no violation occurs. If you're unsure whether a plan is safe, ask before you register. The fix afterward is much harder, and in most cases there isn't one.
Nothing stops you at registration, but you are warned, and the penalty is applied automatically at the end of the semester. Here's the sequence of events in a real case.
WISER accepts the registration without complaint. This is the step that fools people into thinking it's fine.
The degree audit report shows a message that this is an illegal repeat of a course, and that message stays there all semester. This is your warning. If you see it, act on it while you can still drop the course.
Once grades are in, the sequence limitation is applied and the credits and grade are reduced to zero. You did the work and it counts for nothing: not toward credit, not toward GPA. This is the rule working as designed, not an error to appeal.
Students in this situation are usually retaking a course to improve a grade, and the second attempt is usually the better one. It doesn't matter. If the retake violates a sequencing rule, that improved grade cannot be the one that counts for credit or GPA. Before you register to repeat any CS course, check it against the sequences above.
Math and Physics have their own sequencing rules, so consult those departments directly. The university-wide policy is on the Registrar's sequencing policies page.
Every undergraduate CS course and what it depends on, with each box linking to the department's course page. The shape is worth a look on its own: almost everything in the major funnels through CS310, which is why finishing that one on schedule matters more than any other single decision.
The department also maintains an interactive prerequisite chart that covers every program and lets you switch between them. Use that one if you're looking at the BA, the minor, or the IT courses.
Built from the department's course pages. Always confirm against the official course list before you register.
No questions match that search. Email me and I'll answer it, and probably add it here.
You're new, or thinking about switching into CS.
What you actually have to finish. These apply to students who declared Spring 2023 or later.
Sequencing, pacing, and the decisions that are hard to undo.
The rules that decide whether a course you sat through actually counts.
If you're off-track, unsure what to register for, or thinking about leaving the major, that's exactly what I'm here for. The earlier you ask, the more options we have.