TEXT:

Introduction to Software Testing, Ammann and Offutt, Cambridge University Press, 2008
  Book website

CATALOG DESCRIPTION:

Concepts and techniques for testing software and assuring its quality. Topics cover software testing at the unit, module, subsystem, and system levels, automatic and manual techniques for generating and validating test data, the testing process, static vs. dynamic analysis, functional testing, inspections, and reliability assessment.

COURSE OUTCOMES:

Students who complete this course will be able to test software in structured, organized ways. Programmers will learn effective, practical ways to design high quality tests during unit and integration testing. System testers will learn how to efficiently design effective tests. Students will learn how to practically apply theory to design tests based on test criteria.

PREREQUISITES:

Knowledge of discrete math, programming, data structures and a 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.

READING:

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:

There will be 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. Update 31-October: You should submit homework on paper and in class if possible. If you miss class, you may submit on blackboard or via email. No zip files please! Unless arrangements are worked out in advance, 10% per week will be deducted for late submissions. Per GMU policy, all homeworks and projects must be submitted before the beginning of final exams (December 13).

QUIZZES:

We will have weekly quizzes and no midterm exam. Quizzes will be given during the first 15 minutes of each class and no makeup or late quizzes will be given. You are allowed to miss up to three quizzes (the lowest three quiz grades will be dropped). The 10 quizzes with the highest scores will be used to calculate the final grade (10 * 3% = 30%).

BLACKBOARD USE:

All students have blackboard accounts. Login with your George Mason University account (email). Participation on the Blackboard discussion threads will count for 5% of your grade, which you can earn in several ways.

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. (Check the textbook errata page before posting an error.)
4. Post questions to an appropriate thread and they will be answered by your instructor, TA, or classmate. (Basic questions are encouraged, but only "interesting" questions will earn credit. Correct answers will also earn credit.)

DE OPTION:

Lectures will be broadcast simultaneously with classroom lectures via Elluminate (student instructions) on Blackboard. If you will attend half or more of the lectures via DE, you may request the DE option from the professor. The DE option will replace the quiz portion of your grade (30%) with either (1) an in-depth paper on a topic to be chosen with the professor, or (2) a project to test a realistic software system usng test criteria from chapters 2-5 at the unit, integration, and system testing levels. Submission details will be negotiated on a person-by-person basis. DE students are still required to take the final exam in the classroom with the rest of the students.

IN-CLASS COMPUTERS AND COMMUNICATION:

Phone calls, text messages, instant messages, email, and general web surfing are not allowed during class time. Computers may only be used to follow the material in class. Violators will have their devices confiscated or asked to leave the room.

HONOR CODE STATEMENT:

As with all GMU courses, SWE 637 is governed by the GMU Honor Code. In this course, all assignments, exams, and project submissions 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.

DISABILITIES:

If you are a student with a disability and 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/mudge/IM/IMRef.html
Counseling and Psychological Services (CAPS): (703) 993-2380; http://caps.gmu.edu

GRADING POLICIES:

• Blackboard participation: 5%
• Weekly homework assignments: 30%
• Weekly quizzes: 30%
  The lowest three quiz grades will be dropped; allowing for missed classes.
• Closed book, in-class, comprehensive final exam: 35%

© Jeff Offutt and Paul Ammann, 2005-2011, all rights reserved. This document is made available for use by GMU graduate students of SWE 637. Copying, distribution or other use of this document without express permission of the author is forbidden. You may create links to pages in this web site, but may not copy all or part of the text without permission of the author.