Instructor: David Yang (Science South 433, dyang@csuhayward.edu)
Time: Tuesdays, Thursdays 10:00AM-11:50AM
Location: Science North 112 

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: You will be assigned various readings from the Internet.

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: 
Individual assignments : 20%.
Group assignments : 30%
The midterm : 20%.
The comprehensive final exam : 30%.

[grading note: Your exams must average (using the relative weights above) out to a C- or better in order to get at least a C- 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 semester is: 

• Tuesday, Thursday 1:30 PM - 3:30 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

Reading:
Bullseye's tutorial on code coverage
NIST's notes on Basis Path testing

Notes:
Code coverage notes

Reading:
The Software Engineering Institute at Carnegie-Mellon Univ. (intro)
Summary of the Capability Maturity Model for software
Standish Group's top 6 reasons for software project failure

Notes:
Software process, life cycle testing

Groups
Setting up your Blackboard account (by Thursday): forward email address if necessary.
Using the digital drop box: submit a list of

• CS courses taken (title, not number)
• programming languages you feel comfortable with

Reading: SEI article on test plans
Adapted version of IEEE Standard 829 (Applied Computer Technology) (IEEE standards homepage requires subscription)

Homework: Individual assignment #1 (due July 8 by 10am (strict) via digital drop box
testTree.exe (Windows executable for first question)

Choose groups

Reading: Software Requirements Specification for your group (check on Blackboard discussion board for your group)

Reading:
JUnit homepage

End of Add/Drop period

Reading:

Reading:

Reading: 1st part of 2-part article from Unix Insider by Cameron Laird and Kathryn Soraiz (stored on the ITWordl.com site)
Part 2

Reading:
Web site for Whittaker's enjoyable How to Break Software (ISBN 0-201-79619-8). Click on the link for How to Break Software and read the Preface, the Sample Attacks, and the FAQ. The best parts of the book, in my opinion, are the examples of errors found in actual software, but you'll have to buy/borrow the book for those. We'll go through some more examples in class.

Reading:

Reading:

Reading: Graphs related to Challenger O-rings

Last day to withdraw without approval is Monday, Aug. 11

Reading:

Reading:

Reading:

Reading:
TPC home page