Home

Course description

Syllabus

Course policies

Lecture notes

Homework and Exam

Projects

Additional resources

Downloads

Discussions


Previous Courses

2007

 

Course Information

  • Course id: 21120550
  • Course name: Software Quality Assurance & Test
  • Terms: Fall, 2009

Instrutors

Class time and place

Course description

  • This course provides an elementary introduction to software quality assurance and test. Topics include: Why do software testing? The meaning of black-box testing and white-box testing; Software Testing throughout the Software Process; Software Testing and Extreme Programming; The Automation of Software Testing; Difficulties and Limitations of Software Testing; The Business of Software Testing; Implementing and Automated Testing.
  • Students at the end of course should be able to do the following:
    1)Understand the effectively strategies of testing, the methods and technologies of software testing;
    2)Design test plan and test cases;
    3)Do automatic testing;
    4)Establish a testing group and manage the whole testing project;
    5)Clearly and correctly report the software defectives;
    6)Asses the software product correctly;
    7)Distinguish relationship between the software testing and the quality assurance.

Syllabus

  • Prerequisite: Fundamentals of Software Engineering
  • Recommed Textbooks
    Software testing, Marc Roper, McGraw-Hill Companies, 1994. ISBN: 0077074661.
  • References:
    1) Software Engineering - A Practitioner's Approach (5th ED), Roger S. Pressman, Tshinghua Press, 2001.
    2) Software quality assurance, Daniel Galin, China Machine Press, ISBN:711116787, 2005.
    3) Software testing, R. Patton, China Machine Press, ISBN: 7111185269, 2006.
  • More details

Course policies

  • Grading: Grades for the course will be based on the following weighting
    1) Project: 40% 2) Final exam: 60%
  • Project:
    1)Students are divided into several groups, with each group up to 7 people. The groups are choosen by students themselves. Each group has one leader.
    2)The project is due in class as noted in the syllabus and web page. The report of project is turned in within 48 hours of the due dates will be penalized 20%. More than two days late may not get graded at all.

Go Home

 
© College of Computer Science