COEN 286: Software Quality Assurance and Testing -- fall, 2001

Course Information

Prof. John Noll

Santa Clara University

Syllabus. Integrity form. Code Review exercise. Risk Analysis Exercise. Test Design Exercise. Test Plan Exercise.

1. Overview

1.1 Objectives

In designing this course, I asked myself, if I were hiring a software test lead for a project, what would I want that person to know? The answer comprises the course objectives:

1. How to write a useful test plan.
2. How to construct test cases.
3. How to do inspections and walkthroughs.
4. How to write automated tests.
5. How to manage actual testing.

We will try to address each of these with readings and exercises.

Class will be devoted primarily to discussion of readings from the text and handouts; we will have some in-class exercises as well. As such, class participation is important and will be a part of the grade.

1.2 Assessment (Grading)

Grades will be computed as follows:

• Academic Integrity Statement 0-100% (if you don't submit this, it will count as 100% with grade zero.) To ensure that there are no misunderstandings about standards of academic integrity you are expected to meet this semester, please read the academic integrity statement, then print, sign, and return a copy to me by the beginning of the second week.
• Class Participation 20%. All of you have some experience developing software, either in academic or industrial settings. I expect you to contribute to the class by participating in discussions of issues presented in the readings. Thus, part of your grade will be based on how much you contribute. Class participation will be assessed periodically according to the following scale:
  1. Definitely participated: 2 points;
  2. Participated somewhat: 1 point;
  3. Did not participate: 0 points;
  4. Disruptive: -1 point.
• Exercises 80%. The exercises provide hands-on experience with the course concepts, and so serve as an important learning vehicle.
  1. Test exercise. (15%) This exercise introduces software testing.

  2. Risk Analysis exercise. (15%) This exercise explores a simple technique for assessing risk subjectively.

  3. Code Review exercise. (15%) This exercise involves homework and in-class participation in a software code review.

  4. Test Design exercise. (15%) This exercise examines test case design techniques like input equivalence partitioning and boundary value analysis.

  5. Test Plan. (20%) Having examined the pieces in previous exercises and readings, you will have a chance to put them together into a test plan.

• Final Exam 0%. I don't see why we need one. Do you?

1.3 Quality Standards

Each exercise will have specific requirements, which will be detailed in the exercise specification. In addition, I expect all deliverables to adhere to the following additional standards:

• Spelling, grammar, formatting: all documents should be correctly spelled and proofread. Typographic errors, misspellings, obvious grammar mistakes, and egregious formatting problems will result in exponential deductions from your score (2^^n points deducted for n infractions).
• Format: each exercise has a specific required format. This is to facilitate evaluation, so it is essential that you follow the specified format. Failure to do so will result in your submission being returned for reformatting, and will be considered late as a result.
• Name and identification: all submissions should have a cover page that includes your name, your student id (not your social security number), and the exercise title. Those that do not will be assessed a 20% penalty.
• Electronic submissions must meet the above requirements when printed. Electronic submissions must be in plain ASCII text or PDF; do not submit Word .doc files.

2. Logistics

Instructor

Dr. John Noll
Office: ENGR 244 , Monday and Wednesday 11:35-12:30, and Monday, 4:00-5:00.
Email: jnoll@cse.scu.edu

If you need to contact me, please send email; I only check voicemail when I'm actually on-campus.

Class Meeting

Monday, 5:10-7:00pm, ENGR 107.

Communication

This web site will be the primary source of information about the course. Check this page periodically for announcements. If you need to contact me directly, send email to the address above. Please do not leave voicemail for me, as I check it infrequently.

Textbook

Testing Computer Software, Second Edition, Cem Kaner, Jack Falk, Hung Quoc Nguyen. Wiley.

Additional handouts as required.

Syllabus

The syllabus lists the specific topics and associated readings for each meeting.

3. Fine Print

3.1 Prerequisites

Software development experience.

3.2 Late work and examinations

Assignments will be accepted up to one week late, with 20% penalty.

Examinations are mandatory and must be completed at the scheduled time on the scheduled day. If you miss an examination because of an emergency, as soon as you are released or ambulatory submit a copy of your hospital admission, accident report, arrest report, a signed note from your physician on his or her letterhead (which must include address and telephone number), or other verifiable documentation that you were unable to attend the scheduled examination.

Funerals are not considered emergencies and therefore require prior arrangements if they conflict with an exam.

Conference attendance and other work-related activities are not considered emergencies or reasonable excuses for missing an exam.

3.3 Grade Disputes

If you disagree with a grade on an exercise or examination, please follow the procedure outlined in the Grading Errors and Appeals policy document.

3.4 Attendance

A portion of your grade depends on class participation. While attendance is not mandatory, lack of attendance, if excessive, will adversely affect your participation score. Likewise, arriving late for class or other disruptive behavior will be considered ``anti-participation'' and result in a negative participation score.

3.5 Document submission via email

In cases where it is necessary to submit documents (exercises, inquires, etc.) via email, the following types are acceptable:

1. Plain, inline ASCII text with hard newlines.
2. PDF files as attachments, with Unix-convention file names (no spaces) and encoded using base 64 encoding. Be sure the file contents include a header or cover page with your name, course number, and the assignment to which they apply.

Do NOT send Microsoft Word documents, html, or other content formats without prior arrangement.

3.6 Mobile Communications Devices

The classroom is not the place to take telephone calls or receive paging messages. Please turn off your pagers, cellular telephones, etc. during class. If you simply cannot be out of touch f