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. Professor's note: The course will attempt to prepare students to test software in structured, organized ways. This course should provide practical knowledge of a variety of ways to test software, an understanding of some of the tradeoffs between testing techniques, and a feel for the practice of software testing and the research in software testing.

PREREQUISITE NOTES:

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 small 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. I do not accept late homework unless arrangements are worked out in advance, and 10% per week will be deducted for late submissions.

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%).

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.

GRADING POLICIES:

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

© Jeff Offutt and Paul Ammann, 2005-2008, 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.