Editing CSSE376 - Software Quality Assurance

== Class Description ==

This is a class that teaches how to create quality code, and write test cases to ensure it remains that way. [https://wiki.rhlug.org//index.php/File:CSSE376_Syllabus_Hays.pdf View Syllabus]
{| class="wikitable"
|+ Quick Info
|-
| Reading || Required
|-
| Homework || Intermittent
|-
| Exams || 3
|-
| Final Exam || No
|-
| Final Project || Yes
|-
| Flipped Classroom || No
|}

== Advice for Students Taking CSSE376 ==
=== Project ===
The project is a very large portion of your grade, and takes a substantial portion of your effort for the class. Typically, you will implement a digital version of the board game of your choice in a group of 4 people. It is recommended that you purchase the game so you become familiar with it. The goal of the project is not to have a particularly great or good looking game, but to have well-structured, modular, and high-quality code.
=== Homework ===
Homeworks in CSSE376 are referred to as tutorials. The 7 tutorials in the class are as follows: 
1. Git and merge conflicts
2. Test Driven Development
3. Code Review
4. Code Coverage
5. Behavior Driven Development
6. Performance Profiling
7. Automated GUI testing
Generally, the tutorials are almost all coding, in Java, and help you practice the various code quality techniques discussed in class. It's important to pay attention to these, as most of this stuff shows up on the project as well. While an effort is being made to make the class compatible with IntelliJ, some of the tutorials won't quite work out of the box for it.
=== Dr. Hays ===
This class is often taught by Dr. Mark Hays. A lot is said about Dr. Hays, and much of that is often exaggerated. The key to success in any class taught by Dr. Hays is to pay attention in class. He is a very good lecturer, so if you pay attention and ask questions at the appropriate time (when the material is being taught, as opposed to days or weeks later), you will likely succeed in the class.