Course Analytics

for Oregon State University's Computer Science Post-Bacc Program

Upper Division

Core Class

CS 362

Software Engineering II

Data Summary





Hours per Week


/ 5.0 Difficulty

Common Pairings

CS 344:

17 times

CS 372:

16 times

CS 325:

12 times

Tips from Students

Page 1 of 8

WI 20236-12 hours/week1 / 5 CS 340

This course was pretty easy, but extremely useful. It has been one of my favorite classes in the program.

Submitted Sun Oct 01 2023

SP20236-12 hours/week2 / 5

Make sure to follow requirements. The grading can be rough. I missed one little thing on one of the assignments and got an F. I still made it out with an A.

Submitted Sat Jun 17 2023

SP 20230-5 hours/week3 / 5 CS 325

Read the instructions and be diligent.

Submitted Wed Jun 14 2023

SP 20230-5 hours/week1 / 5

easy class.

Submitted Fri Jun 02 2023

WI 20230-5 hours/week1 / 5 CS 344CS 372

This class is the platonic ideal of an easy course. The explorations are short, but I also felt like I learned a lot. The instructor cares about doing a good job, and materials are well organized and written.

Submitted Fri Apr 21 2023

FA 20220-5 hours/week1 / 5 CS 344CS 361

Enjoyed this a bit more than 361, you do some unit testing in python, creating test suites, mess around with git, learn about different types of testing and finally doing some testing as a group with shared repos on GitHub. End up doing pull requests and code reviews. Similar to 361, this class but expanded could be a really cool course. As it stands it isn't that bad, but still is going to be looked at as a filler class until something changes, if it ever does.

Submitted Mon Dec 12 2022

FA 20220-5 hours/week1 / 5 CS 493

This is a great class. Important topics focusing on git, reading other peoples code, working with a codebase in parallel with other developers and code reviews. The unit testing is pretty good too, something that you don't do a lot of outside of this class in this program. A lot of these skills are really pertinent to actual work in the field. Reading other peoples code, working on a git with multiple contributors, testing your code (and other peoples) all are important in the work place. The actual work in the class is really light and easy, and often each week's material can be completed in a single day. I guess make your group early and make sure everyone is on the same page as far as who does what, committing, and reviewing commits. Don't leave it for the last day. Very easy class but really good stuff.

Submitted Sun Dec 11 2022

FA 20220-5 hours/week2 / 5 CS 340CS 372

Put in the effort on the assignments. There are very few points, the assignments are not very difficult, but losing points on the assignments doesn't put you in a great place for the final which is a decent chunk of the grade.

Submitted Thu Dec 08 2022

FA 20220-5 hours/week3 / 5 CS 325CS 340

Be careful! Yes, what you've no doubt heard is true, this class has a below average workload. The subject material is also pretty easy to absorb. However, don't let it lull you to sleep. There are very few total points you are able to earn in this class. As a result, a loss of a few points here and there can have a significant impact on your overall grade. This combined with relatively tedious grading criteria and a few pass/fail constraints on some assignments means you need to be careful!

Submitted Thu Dec 08 2022

FA 20220-5 hours/week1 / 5 CS 361CS 493

Finding the bugs in the first couple of assignments was actually really fun! Overall, this course might be one of the most useful in the program for your professional career, but it could definitely go more in depth.

Submitted Tue Dec 06 2022

Page 1 of 8


Course Analytics was developed for students of Oregon State University's online Computer Science program. The data on difficulty, time commitments, course pairings, and tips have been submitted by real students using this survey. Feel free to add your own reviews if you are a current student! The data is scraped from this spreadsheet.

Course Analytics is an open source project by Nic Nolan.
View the repository on GitHub