MSSE640 - Software Quality & Testing: Syllabus

Instructor Information

Refer to Discussion Forum, Facilitator Introduction and Expectations

Course Title

MSSE640 - Software Quality & Testing

Course Description

Reviews the Software Quality Assurance (SQA) and Verification and Validation (V&V) processes. Addresses verification of the behavior of a program on a set of test cases selected from the execution domain.

Prerequisite Courses

MSSE 600 Object-Oriented Software Engineering

Course Overview

This course presents a practical approach to software testing as a sub-discipline of software engineering. It introduces software quality concepts, standards, measurements, and practices that support the production of quality software. It offers a solid foundation in testing fundamentals including test case design, test management, and test measurement strategies, which improve the effectiveness of software test processes. Software quality and software testing concepts are presented from managerial, technical and process-oriented perspectives. Software quality assurance is explored for both traditional, plan-driven software development processes and newer, agile development methodologies.

Course Outcomes

Upon completion of this course, learners should be able to:

Course Materials

Required Texts

Burnstein, I. (2003). Practical Software Testing. Springer-Verlag. ISBN: 0-387-95131-8.

Crispin, L. & Gregory, J. (2009). Agile Testing: A Practical Guide for Testers and Agile Teams. Addison-Wesley. ISBN: 0-321-53446-8.

Required Resources

None

Technology Tools

technical specifications

Pre-Assignment Due Dates

Course Assignments and Activities

Assignments for Online Course
Week Readings Graded Assignments (*see Summary of Assignments with associated percentages below)
1: Software Quality Assurance and Testing Fundamentals

• Burnstein (2003). Chapters 1, 2, 7

• Crispin & Gregory (2009). Chapters 1, 2

  • Introductions (required but not graded)
  • Discussion Questions
  • Weekly reading questions
2: Software Quality as an Organizational Activity

• Burnstein (2003). Chapter 8

• Crispin & Gregory (2009). Chapters 3, 4, 5

  • Discussion Questions
  • Weekly reading questions
  • Test Case Analysis: Equivalence Classes
  • Project Component: Test Plan Outline
3: Testing in PlanDriven Software Development

• Burnstein (2003). Chapters 3, 4, 5, 6

  • Discussion Questions
  • Weekly reading questions
  • Test Case Analysis: Boundary Values
4: Testing on Agile Teams

• Crispin & Gregory (2009). Chapters 6 – 12

  • Discussion Questions
  • Weekly reading questions
  • Test Case Analysis: Decision Tables
  • Project Component: Agile Story Cards & Acceptance Criteria
5: Software Quality Process Monitoring and Control

• Burnstein (2003). Chapters 9, 10

• Cohen &Teleki, Brown, (1978).

  • Discussion Questions
  • Weekly reading questions
  • Test Case Analysis: Pairwise Testing
6: Test Automation Tools and Techniques

• Burnstein (2003). Chapter 14

• Crispin & Gregory (2009). Chapters 13, 14

  • Discussion Questions
  • Weekly reading questions
  • Test Case Analysis: State-Transitions
  • Project Component: Formal Test Cases
7: Evaluating Software Quality Processes

• Burnstein (2003). Chapters 11, 12, 13

  • Discussion Questions
  • Weekly reading questions
  • Test Case Analysis: Control Flow
8: Software Engineering as a Profession

• Burnstein (2003). Chapters 15, 16 • Crispin & Gregory (2009). Chapter 21

  • Discussion Questions
  • Weekly reading questions
  • Project Component: Selenium Automated Testing
  • Final Exam
TOTAL:

*Summary of Assignments and Percentage Weight towards course grade.

Assignments Weighted Percentage
Discussion Questions/ Participation (Weeks 1-8) 20%
Weekly reading questions (Weeks 1-8) 20%
Test Case Analysis (Week 2-7) 20%
Project Components 20%
Final Exam (Week 8) 20%
Total 100%

CCIS Policies

Review the CCIS Policies on the Regis University website.

OTHER INFORMATION

NOTE TO LEARNERS: On occasion, the course facilitator may, at his or her discretion, alter the Learning Activities shown in this Syllabus. The alteration of Learning Activities may not, in any way, change the Learner Outcomes or the grading scale for this course as contained in this syllabus. Examples of circumstances that could justify alterations in Learning Activities could include number of learners in the course; compelling current events; special facilitator experience or expertise; or unanticipated disruptions to class session schedule.