SEG 3203 Summer 2007:   Software Quality Assurance

Links within page

• Course Description
• Schedule
• Text
• Course Materials
• Professor and TA
• Lab material
• Tutorial material
• Evaluation

Course Description

[4 credits]

[Compressed summer course:  per week:  4 hours lectures, 2 hours lab, 2 hours tutorial]

The following topics will be covered, although not necessarily in this order:

• Overview of software quality

• Aspects of quality:  functionality, regression, capacity, reliability, performance, security, ...

• Software models for testing and quality analysis

• Control and data flow graphs
• State machines

• Test coverage
• Testing, verification and validation techniques

• Inspections and reviews
• Testing from an external view of the system
• Testing with internal system knowledge
• Testing using a fault model
• Analysis and verification
• Test execution
• Tools:
1. Test execution tools
2. Other tools:  coverage measurement, profilers, etc.
• Results reporting and tracking

• Quality processes

• Process models
• Planning and documentation
• Risk analysis
• Metrics
• Phases of testing:   unit, integration, system

Schedule

Lectures:

Monday, 10:30 – 12:30, CBY B012

Wednesday, 08:30 – 10:30, CBY B012

Tutorial:

Monday, 13:00 – 15:00, STE 2060

Lab:

Monday, 15:00 – 17:00 STE 2060

Text:

• For this course, the plan is that the source material for the lectures will generally follow reference [1] with some material based on [2] and other sources.  For the labs, the material will be somewhat based on [2].
• Reference [1] is strongly recommended but not required.  References [2] and [3] are optional; they cover similar material to each other.

M. Pezzè, M. Young, Software Testing and Analysis:  Process, Principles, and Techniques, Wiley, 2008 (really!)

This book has been ordered at the Agora book store.  It is a new book just released in April 2007.

   V. Massol, JUnit in Action, Manning, 2004

   J.B. Rainsberger, JUnit Recipes, Manning, 2004

Some alternate references (not required):

R. Patton, Software Testing, 2^nd Edition, 2006

G.J. Myers, The Art of Software Testing, Wiley, 2^nd Edition, 2004.

B. Beizer, Software Testing Techniques, VNR, 1990 (out of print, available second-hand).

R.V. Binder, Testing Object-Oriented Systems, Addison-Wesley, 1999.

H.Q. Nguyen, B. Johnson, M. Hackett, Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems, Wiley, 2003

Lecture notes:

Course introduction (May 2)

Introduction to software quality assurance (May 2)

Principles of testing (May 7)

Software models (May 9, 14)

Flow graph test coverage (May 14, 16)

State machine test coverage (May 23)

Equivalence class partitioning and decision trees (May 28)

Equivalence classes for the triangle example (May 28) [Excel spreadsheet]

Combinatorial Testing (June 6)

Mock objects (June 18)

Testing object-oriented software (June 20)

Integration Testing (June 20)

Web application testing, part 1:  clients and in-container testing (June 25)

Web application testing, part 2:  databases and web page content (June 27)

System testing (July 4, 9)

Process Maturity Models and Quality Metrics (July 11)

Additional material:

Code coverage tools (Clover, Emma, Coverlipse, Cobertura) (May 16)

Capture and replay tools (May 30)

Midterm information (May 30)

Pre-exam information (July 11)

Professor and TA:

Professor:  Alan Williams

Office:  STE 5007

Phone: 562-5800 x6914

E-mail:  awilliam@site.uottawa.ca

Office hours:  Thursdays, 14:00 – 16:00

TA: M. Shamim Hossain

E-mail:  shossain@site.uottawa.ca

Tutorial Material:

Tutorial 1:  JUnit (May 7)

Tutorial 2: Code Instrumentation Tools (May 14)

Tutorial 3:  Problems from summer 2006 midterm and exam (May 28)

Tutorial: Sample test cases for the project (July 9)

Lab Material:

Lab 1:  JUnit introduction (May 7)

• .zip file with May 7 tutorial + lab instructions

Lab 2:  JUnit and code coverage with Clover (May 14)

• .zip file with May 14 tutorial + lab instructions + source code for lab

Lab 3:  Testing with databases (May 28)

• Extra information on Java, JDBC, database connections, and the code in the lab.

Lab 4: Mock objects (June 18)

Evaluation

• Project (P) is worth 20 marks in total
• Midterm (M) is worth 25 marks
• Midterm is Mon. June 4, 10:45 – 12:05, CBY B012
• Exam (E) is worth 55 marks
• Exam is Tues. July 17, 09:00 – 12:00, STE F0126

• You must get at least 32.5 marks from M + E:

If you do, your final grade is A + M + E.

If you do not, your mark will be 100/65 * ( M + E ).  Note that this means that you will get less than 50% for the course.

---

Most recent update to this page:  Wednesday, July 11, 2007 08:25