Prerequisites

Advisory: Computer Information Systems 50.

Course Description

Analysis of types of software; software development life cycle; top down design and structured programming; modularization; standards and practices; software configuration management; software testing; documentation; software error types, causes; software quality assurance plans and procedures; software discrepancy reports, analysis; software visibility for managers.

Three hours lecture, three hours lab.

Course Objectives

The student will:

1. Describe the software process for Software Quality
2. Learn components of Software Quality
3. Apply Techniques for Product Quality Assurance
4. Explain Software Quality Standards
5. Describe the Software Test Cycles
6. Learn how to plan for Testing Software
7. Learn and apply concepts of measuring software quality
8. Learn how to create a software quality improvement roadmap
9. Learn how to use defect-reporting and test case management tools to aid in the testing effort

Instructor

Mary Ann May-Pumphrey
maypumphreymaryann@fhda.edu

Text

In order to make our study of the many concepts introduced in this textbook as engaging as possible, those classes devoted to a chapter of the book will take a variety of formats:

• Lecture. I talk, you ask questions!

• Quiz. I ask questions, you answer them.

• "Most Important Points Free-for-All." Each attendee takes a turn (3 minutes max) telling the rest of the class some point from the chapter which s/he found the most interesting/useful/important. (I'll record these and then post them on our class web site.)

• "Shared Lecturing." Each of you lectures on a short pre-assigned section of the chapter.

• "Class Competition." Although none of these are scheduled, the instructor may elect to replace a "Most Important Points Free-for-All" or "Shared Lecturing" event with a competition instead. In these events, two or more teams are created, and the material is reviewed via a game-show-style competition.

Lecture/Lab Schedule

Lab:	5:30 - 6:20 p.m.
Lecture:	6:20 - 7:45 p.m. (includes 10-minute break)
Lab:	7:45 - 8:10 p.m.

Attendance

Students may be dropped after the third unexcused absence from class. But don't count on this happening! If you need to disappear from the class, drop it yourself to be safe.

Grading:

• Bug reports - 15%
• Test plan - 15%
• Field trip - 5%
• Test case management project - 15%
• Quizzes - 10%
  • Closed-book/closed-notes
  • PARScore sheet & #2 pencil needed
  • Cover material from one chapter only
• Participation - 5%*
• Midterm - 15%
  • Closed-book/closed-notes
  • PARScore sheet & #2 pencil needed
  • Cover material from chapters 1-6 plus any non-text material discussed
• Final - 20%
  • Closed-book/closed-notes
  • PARScore sheet & #2 pencil needed
  • Cover material from chapters 1-12 plus any non-text material discussed
• Extra-Credit - 1-5 points on overall grade

* The "Participation" portion of your grade will be based upon your participation in the "Most Important Points Free-for-All," "Shared Lecturing," and "Class Competition" methods of text coverage discussed above under Text.

Final Letter Grade:

Depending on the grade breakdown, the instructor may lower the minimum percentage needed for some of these grades. Do not depend on this happening!

Cheating

In the "real world" inhabited by professional QA engineers, the more collaboration, the better. Thus, you are encouraged to collaborate with your classmates and other acquaintances in order to help you produce the best work possible on your assignments. But since this is still an academic setting, your final "hand-in" work must be your own. For example, you are encouraged to ask others for feedback on your test plan. But the actual writing and re-writing of the test plan must be done entirely by you. The same is true for your bug reports--gather as much feedback as you can on the quality of them, but make the actual improvements all by yourself.

If somebody else does the actual work handed in or presented, that will be viewed as an example of cheating, not collaboration. In addition, the midterm and final exam will be traditional academic exams, in which any collaboration will be viewed as cheating. Any student involved in an incident of cheating, even if serving only to provide work to another student, will be given a grade of "0" for that assignment or exam. No excuses, no exceptions!

Class Schedule
Date	Plan
Tuesday, 09/23	Introduction. Review of course outline.
Thursday, 09/25	Chapter 1 of text. Format: Lecture.
Tuesday, 09/30	Intro to Bugzilla.
Thursday, 10/02	Chapter 2 of text. Format: "Most Important Points Free-for-All."
Tuesday, 10/07	Bugzilla continued.
Thursday, 10/09	Chapter 3 of text. Format: Lecture.
Tuesday, 10/14	Chapter 4 of text. Format: Quiz.
Thursday, 10/16	Chapter 5 of text. Format: Lecture.
Tuesday, 10/21	Chapter 6 of text. Format: "Shared Lecturing."
Thursday, 10/23	Review for midterm.
Tuesday, 10/28	Midterm Exam.
Thursday, 10/30 ONLINE CLASS!	Go over midterm. Browser compatibility testing tool Link checker tool
Tuesday, 11/04	Chapter 7 of text. Format: Quiz
Thursday, 11/06	Testopia intro Due: Bug Reports assignment
Tuesday, 11/11	Testopia continued
Thursday, 11/13	Chapter 8 of text. Format: "Most Important Points Free-for-All."
Tuesday, 11/18	Field Trip to SSQA Meeting Due: Test Plan assignment
Thursday, 11/20	Chapter 9 of text. Format: Quiz. Hands-On Overview of Automated Web Page Testing with Selenium IDE.
Tuesday, 11/25	Chapter 10 of text. Format: Shared Lecturing. Due: Field Trip assignment
Thursday, 11/27	THANKSGIVING holiday - college closed
Tuesday, 12/02	Chapters 11 and 12 of text. Format: Lecture.
Thursday, 12/04	Review for final exam.
Tuesday, 12/09	Final Examination Due: Test Case Management assignment