Announcements: Welcome to Software Testing!

CS 4320 Spring 2003 Home Page
CS 4320 Spring 2003 - Software Testing - 4 Credits 

Instructor: David Yang (Science South 433, dyang@csuhayward.edu)
Time: Mondays, Wednesdays 4:00-5:55 PM
Location: Science South 125 

Blackboard -- notes, submitting work and grades: Lecture notes will be posted on Blackboard after each class. You will be submitting your work on Blackboard and will be able to check your grades there. If you have never used Blackboard before, note that you are automatically given an account. To get started, go to the Support Page . You should find the Getting Started page for Students especially helpful. Note that I do sometimes send information to your email address listed on Blackboard. If you should change email addresses, please update it on Blackboard (the FAQ tells you how).

Text:
Lewis, Software Testing and Continuous Quality Improvement, Auerbach, 2000, ISBN 0-8493-9833-9.

Goals:

  • to develop an understanding of the concepts and techniques of software testing and quality analysis
  • to further develop habits and methods appropriate to the discipline and to scholarly inquiry in general
  • to further your ability to work with others

Calculation of your grade: 
The assignments will count for 45%.
The midterm will count for 25%.
The comprehensive final exam will count for 30%.

[grading note: Your exams must average (using the relative weights above) out to a B or better in order to get at least a B in the course.]

Final grades will be given according to the following scale:

93-100 A, 90-92 A-, 87-89 B+, 83-86 B, 80-82 B-, 77-79 C+, 73-76 C, 70-72 C-,67-69 D+, 60-66 D, 0-59 F 

Attendance:
Remember that standard policy dictates that students who do not attend can be removed in favor of students on the waiting list who do show up. Also, not being prepared for an exam is not an excuse to not show up -- if you do not have a verified excuse, you will be given a zero for the exam. If you find out in advance that you will not be able to be present on the day of the exam, you should (as in all your courses) let me know as soon as possible.

Academic Honesty: This course will follow the University's standard policy on academic dishonesty. In particular, note that regardless of whether you copy work from another student or allow another student to copy your work on an exam, you are both equally guilty and equally penalized. Copying text/files off the internet without properly giving credit is also cheating. Any cheating on an exam results in an F for the course. Cheating twice also results in an automatic F. All instances of cheating will be reported to the Dean's office.

Remember that the University may inflict further penalties than listed here under the provisions of the published Academic Dishonesty Policy. 

Office Hours: My office is in room 433 of the South Science Building. My schedule for office hours this spring semester is: 

  • Monday noon-1 PM, 2:45 PM-3:45 PM
  • Wednesday 2:45 PM-3:45 PM 


I will also be available at other times by appointment, and you should feel free to drop by unannounced -- I'll let you know if I'm busy. 

Tentative Schedule All days in red are mandatory. Days in green are holidays

    Week  Monday  Wednesday 
    Week 1 03/31/2003 
    Cesar Chavez Day -- no classes
    04/02/2003 
    Introduction
    first class notes

    Reading:
    Lewis, Introduction, pp. 1-18
    Eric Raymond's "The Cathedral and the Bazaar" The whole article is enjoyable and informative, but testing is described mostly in the first 5 sections

    Groups
    Setting up your Blackboard account (by Friday): correct your email address if necessary, submit a list of

    • CS courses taken (title, not number)
    • programming languages you feel comfortable with
    via the digital drop box

    Also, dig up whatever software engineering project you had for CS 4310. If you have not taken 4310 yet, do not worry -- you will be grouped with someone else who has for group assignments.

    Week 2 04/07/2003 
    Overview, Deming and Plan-Do-Check-Act cycle
    overview notes

    Reading:
    Lewis, pp. 19-40

    Homework:
    homework 1
    Examples of wrong code

    04/09/2003 
    Life Cycle Testing
    Life Cycle Testing overview notes

    Reading:
    Lewis, pp. 41-60

    Week 3 04/14/2003 
    Life Cycle Testing

    Reading:
    Lewis, pp. 61-76

    04/16/2003 
    Life Cycle Testing

    Reading:
    Lewis, pp. 77-86

    Week 4 04/21/2003 
    Spiral testing

    Reading:
    Lewis, pp. 87-105

    04/23/2003 
    Information Gathering, Test Planning

    Reading:
    Lewis, pp. 107-121

    Week 5 04/28/2003 
    Test Planning

    Reading:
    Lewis, pp. 122-137

    04/30/2003 
    Test Planning and Test Case Design

    Reading:
    Lewis, pp. 138-154

    Week 6 05/05/2003 
    Test Case Design, Development and Execution

    Reading:
    Lewis, pp. 155-172

    05/07/2003 
    Midterm
    Week 7 05/12/2003 
    Preparing for next spiral, System Testing

    Reading:
    Lewis, pp. 173-190

    05/14/2003 
    System and Acceptance Testing

    Reading:
    Lewis, pp. 191-208

    Week 8 05/19/2003 
    Reporting Test results

    Reading:
    Lewis, pp. 209-223

    Last day to withdraw

    05/21/2003 
    Evaluating Testing Tools

    Reading:
    Lewis, pp. 273-281

    Week 9 05/26/2003 
    Testing and Maintenance

    Reading:
    Lewis, pp. 283-297

    05/28/2003 
    Maintenance, enhancements and defects

    Reading:
    Lewis, pp. 298-319

    Week 10 06/02/2003 
    Revisiting the cathedral vs. the bazaar
    06/04/2003 
    Review
    Week 11 06/09/2003 
    Final exam, 4 PM-5:50 PM
     

     
    This webpage's layout is originally from Bill Parkinson, who used to teach in the evening program at St. Joseph's University.