Instructor Information

Instructor:	Pete Nordquist
Phone:	552-6148
E-mail:	nordquip@sou.edu
Office:	CS215

Office Hours:	MW 10 – 11. Other times by arrangement – send email to arrange a time.

Website:	www.sou.edu/cs/nordquist/cs455

The web site contains lab assignments, class notes, and other useful information.

Class Times

Monday, Wednesday (CS 224) 4:00 to 5:50

Course Text

Practical Guide to Software Quality Management

2^nd Edition

John W. Horch

Artech House

2003

ISBN: 1-58053-527-5

The library has 1 copy of the book for library use.

Course Description

Introduces techniques for assuring software quality. Students use a variety of tools to build, configure, and test software. Topics include: creating tests from requirements, standards and reviews, build tools, configuration management, testing, defect tracking, risk management, and documentation.

Prerequisites: CS 367.

Tentative Schedule

Week 1	Ch 1 (Overview), Ch 10.2.1 (Requirements), Appendix D,
	Lab: Identify product Write product requirements specification.
Week 2	Ch 2 (Standards), Ch 10.3 (Test documentation), Appendix G
	Lab: Identify QA partner. Write product test plan and TTM.
Week 3	Ch 3 (Reviews), Ch 4 (Testing), Appendix H
	Lab: Write test cases for your product.
Week 4	Exam 1 over material in weeks 1-3 Build concepts (make) – not in book
	Lab: Submit source code tarball including single-command build for your project. Review partner’s lab 1 (their requirements document)
Week 5	CVS – not in book Ch 6: 6.3 - 6.5 (Configuration Accounting)
	Lab: Put product source and documents under CVS. Review partner’s TTM Tag a releasable configuration that is ready for testing. Submit tarball of entire cvs tree and release tag.
Week 6	Bug tracking.
	Lab: Do a test run of the version you released last week. Test your lab 5 release Modify your test cases as necessary as testing proceeds. Write basic defect reports for failed tests and reference test case in defect report. Write test coverage report, i.e., make a listing of tests run.
Week 7	Ch 5: 5.0 – 5.5 (Defect Analysis)
	Exam 2: Take home on make and CVS Possible lab on doing QA for security aspects of product.
Week 8	Ch 5: 5.6 – 5.8 (Defect Metrics) Ch 6: 6.0 - 6.2 (introduction to Configuration Management)
	Lab: Defect reporting Create bug tracking database. Create BOM of your product
Week 9	Ch 9 (Risk), Automated testing: e2 as simple example: need driver, oracle, analysis, accounting. Do it for regression testing. Secs. 7.0 – 7.3
	Lab: Write automated smoke test for your product.
Week 10	Rest of Ch 10 (Documentation), FURPS, automated testing

Course Grading

The lab assignments build on one another, so that by the end of the term you will have created a version-controlled tested release of a software product. Lab scores are worth 60% of your total grade. Labs can receive one of the following grades:

100 - your lab met all of the requirements.

95 - your lab failed to meet a minor requirement.

90 - your lab failed to meet a major requirement

80 - your lab failed to meet two major requirements

70 - your lab ran, but just barely

<=60 – your lab did not run

0 - you didn’t turn in a lab.

If you submit your lab after the due date, but within a week of the due date, you will receive a 5% late fee. I.e., I will grade your lab according to the schedule given above then subtract 5 points. If you submit your lab more than a week late, you will receive a 10% late fee. Labs that are more than two weeks late will not be accepted.

There will be two exams during the term. Make-up exams will not be given unless arrangements are made in advance, or you had a bona fide emergency on the day of the exam. Your exam scores are worth 25% of your total grade.

A comprehensive final will be given that is based on the exams and the topics covered in class. The final is worth 15% of your total grade.

In addition to the above requirements, students taking the class for graduate credit must prepare either: a) a 4 to 5 page paper or b) a 30 minute class presentation with powerpoint slides on some QA topic in which you are interested. The challenge is to find the topic, research it, and summarize the important points in a logically cohesive fashion.

Email

I expect that you read your student email every business day. I send all kinds of class announcements by email and expect that you get these announcements. I sometimes forget to make these announcements in class, so email is the only way you have to get this information.

If you find you are having trouble with a lab, get sick the day of an exam, or anything else that you think might affect your grade, send me email explaining the problem as soon as you can. Email gives us a starting point for discussing a solution and an official timestamp that indicates when you first took action to solve the problem.

If you are in need of support because of a documented disability (whether it be learning, mobility, psychiatric, health-related, or sensory) you may be eligible for academic or other accommodations through

Disability Services for Students.

For Detailed Information, call 541-552-6213 or visit the ACCESS Center in Stevenson Union, lower-level. The Disability Services website is:

http://www.sou.edu/access/dss/