Syllabus Schedule My home page
I have not failed. I’ve just found 10,000 ways that won’t work.
-Thomas Edison
August, 2017

SWE 637 : Software Testing
Course Syllabus—Fall 2017
Effective Fall 2017, software testing will be a qualifying exam for the PhD-CS program. Software modeling and architecture is being phased out of the qualifying exams.

Professor: Jeff Offutt
Office: 4430 Nguyen Engineering Building, 703-993-1654
Email: offutt +=+=+ gmu.edu
URL: http://cs.gmu.edu/~offutt/
Twitter: @jeffoffutt
Class Hours: Mondays 4:30-7:10, MH D023 (just renamed to James Buchanan Hall)
Prerequisite: SWE 619 and SWE Foundation material, or CS 540 and CS 571
Office Hours: Anytime electronically, Wednesdays 3:30-5:00, or by appointment
GTA: Rasika Mohod, rmohod@gmu.edu, Office Hours: Tuesdays 4:00-6:00, ENGR 4456

TEXT
Introduction to Software Testing (edition 2), Ammann and Offutt, 2017, Cambridge University Press.   Book website

CATALOG DESCRIPTION
Students learn to test software effectively. Programmers learn practical ways to design high quality tests during all phases of software development. Students learn the theory behind criteria-based test design and to apply that theory in practice. Topics include test design, test automation, test coverage criteria, and how to test software in cutting-edge software development environments.

COURSE LEARNING OUTCOMES
  1. Students who complete this course will be able to test software in structured, organized ways.
  2. Programmers will learn effective, practical ways to design and automate high quality tests for unit and integration testing.
  3. System testers will learn how to efficiently design effective tests. Students will learn how to apply theory in practical ways to design tests based on test criteria.

PREREQUISITES
You must have knowledge of discrete math, programming, data structures and general knowledge of software engineering. You will need a basic familiarity with some of the subjects and terms of software engineering. You will need an in-depth understanding of the syntax and semantics of multiple programming languages. Most examples will be in Java and some assignments will require JUnit tests. If you did not take the prerequisites, please do not ask for “permission.” Read my thoughts instead.

READINGS
I expect you to read the relevant material before lecture. The lectures may not cover everything in the readings and will often include material not found in the readings.

HOMEWORK ASSIGNMENTS
We will have computer and homework assignments for most of our topics. Some will require pencil and paper and others will require modest programming or use of tools available from the Web. You should submit homework on paper and in class if possible. If you miss class, you may submit via email. No zip files please!
Timeliness: Homework assignments must be submitted at the beginning of class on the day they are due to be counted as on time. Late submissions will receive a 10% per week. Per GMU policy, all assignments must be submitted before the beginning of final exams (December 13).

COLLABORATION
You may work on homework assignments individually if you wish.
However, not only is collaboration how real software is built, but also the best way to learn. Therefore, collaborative assignments will receive a 5% bonus credit. If you work collaboratively, list every collaborator and a short summary of what each person did. You can submit one assignment with multiple names or work together to analyze the problem and develop the solution, then complete the assignment separately. You can collaborate in teams of up to three students with as many classmates as you want, but only other students in SWE 637 this semester. You may work with different partners with different homework assignments. (Updated 15-September)
Note: You are NOT ALLOWED to include “guest names.” Every person listed as a collaborator must contribute. If someone is listed as a collaborator but did not contribute, all will be given a zero on the assignment and reported to the university honor committee.

QUIZZES
Instead of midterm exams, we will have weekly quizzes. Quizzes will be given the first 10 or 15 minutes of class and will cover material from the previous class meeting and occasionally from the reading assigned for that day.
New re-take policy: Instead of dropping quizzes (as in past semesters), students who miss or perform badly on a quiz can have one retake.
  • Scoring: The maximum score on a retake quiz is 80%.
  • Replace: If you take the retake, your new score will count and the first score is dropped.
  • Scheduling: Retake quizzes will be offered immediately before class or during the instructor’s or the TA’s office hours. Students who want a retake a quiz must send an email to me and the TA telling us which quiz and when you want to take it.
  • Content: The retake quiz will be different from the one given in class, but will cover the same topics.
  • Timing: The retake quiz must be taken before the second class meeting after the in-class version.

IN-CLASS EXERCISES
We will do in-class exercises during most class meetings. Some will be done as a class, some will be done in small groups, and a few may be individual exercises. They will be graded on a pass/fail basis and will count toward your overall grade. They will be announced during class. Important: Credit can only be received if done in class, although if you miss class, you should do the posted assignments on your own to prepare for the quizzes or final exam.

DISCUSSION BOARD USE
All students will be enrolled in the discussion forum for SWE 637 on Piazza. You will receive an invitation to this free resource via your Mason email. We will use the discussion board throughout the semester. Participation on piazza will count towards your participation grade.
  1. Real-life software failures: Start a discussion about a real-life software failure. Tell us what happened and how it affected users.
  2. Describe how one of the ideas from our testing class could have found a real-life software failure before the software was released.
  3. Start a thread about an error in the book or slides, or about a topic that goes beyond what we discuss in class.
  4. Post questions to an appropriate thread and they will be answered by your instructor, TA, or classmates. Basic questions are encouraged, but only “interesting” questions will earn credit. Correct answers will also earn credit.
Participation must occur during the semester, not after final exams start.

IN-CLASS COMPUTER USE
Lectures in this class will be computer free. Computers, whether in the form of laptops, tablets, or mobile phone/pocket-computers, may not be used while I am lecturing. I have a detailed explanation why, but here is the short summary: Computers interfere with your classmate's ability to concentrate on the educational material, my concentration, and your learning. Multitasking is a myth promulgated by inefficient people. Taking notes by hand is much more effective than typing notes on a computer. If you have to check your email or text messages, or take a phone call, please sit near the door so you can unobtrusively step out. I will ask you to close your computers, and if that doesn’t work, will ask you to leave the classroom. (Computers will be used extensively during in-class exercises, discussions, and examples.)

OFFICE HOURS
Office hours are times that I commit to being in my office, door open, first come, first served. You do not need an appointment, and no appointments are made. If you cannot make my office hours, then we can try to set up an appointment. Please note that I have family commmittments, so I am seldom available after 5:00 pm. I will inform you in class or on the discussion board if I have to miss office hours.

ELECTRONIC PRESENCE
I always accept linkedin requests from current and former students—we clearly have a professional relationship. I tweet random thoughts irregularly about software engineering @jeffoffutt. Out of respect, I do not initiate facebook requests from students, but usually accept them.

HONOR CODE STATEMENT
As with all GMU courses, SWE 637 is governed by the GMU Honor Code. In this course, all quizzes and exams carry with them an implicit statement that it is the sole work of the author, unless joint work is explicitly authorized. Help may be obtained from the instructor or other students to understand the description of the problem and any technology, but the solution, particularly the design portion, must be the student’s own work. If joint work is authorized, all contributing students must be listed on the submission. Any deviation from this is considered an Honor Code violation, and as a minimum, will result in failure of the submission and as a maximum, failure of the class.

OFFICE OF DISABILITY SERVICES
If you need academic accommodations, please see me and contact the Disability Resource Center (DRC) at 993-2474. All academic accommodations must be arranged through the DRC.

OTHER USEFUL CAMPUS RESOURCES
Writing Center: A114 Robinson Hall; (703) 993-1200; http://writingcenter.gmu.edu
University Libraries “Ask a Librarian”; http://library.gmu.edu/ask
Counseling and Psychological Services (CAPS): (703) 993-2380; http://caps.gmu.edu

EMAIL
I occasionally send important announcements to your Mason email account, so you must read it regularly. Professors are required to use your Mason email, not a personal email accounts. Email sent to the professor or TA should have a subject that starts with “swe 637.” If not, we may not notice it. General class questions should be posted on the discussion board, not sent through email.

GRADING POLICIES

Top