Instructor: Dr. Jeff Carver
Email:
carver@cse.msstate.edu
Phone:
(662) 325-0004
Office:
Butler 329
Office hours: TBD
Catalog Description
Topics include methods of testing, verification
and validation, quality assurance processes and techniques, methods and types of
testing, and ISO 9000/SEI CMM process evaluation.
Course Goals
The student will be able to describe the state of the practice verification and validation techniques.
The student will demonstrate proficiency in managing a software project to customer requirements.
The impact of ISO 9000 and the capability maturity model on software quality and testing will be addressed.
Required readings:
The Midterm Exam will cover lectures, discussion in class and homework up to that point in the semester. The entire normal class time will be allowed for each exam.
Midterm Exam Monday,
February 19
Final exam Friday,
April 27, 12:00--3:00pm, as
scheduled by the University
No one may take the final exam early.
The Final Exam will be
--- Comprehensive
Please notify Dr. Carver of the circumstances for each absence/tardiness by email. Whenever possible, notify him in advance of expected absence/tardiness.
All auditors must be authorized by the Dean and the Registrar per University
regulations. Auditors are expected to attend classes and to participate
in discussions. Auditors may not turn in assignments or take exams.
Collaboration on homework is not allowed.
Due date Assignment
TBD
All homework will be submitted via email to Dr. Carver. Relevant files will be attachments. Graded homework will be returned via email or in class.
Each homework assignment is due prior to midnight on the due date, according to the date of the email.
All homework reports will conform to the Dept. of CSE style
for theses and will consist of title page and body of the report.
See the Dept. of CSE Web site for detailed
style requirements and example
references. In contrast to a thesis, the front matter is omitted,
and the report does not have chapters (sections are the top level).
You may use any word-processing tool you prefer. Attach all files
needed to read your report to your email. For example, if you use
MS-Word, attach a *.doc file. If you use LaTeX, attach a *.ps file that
includes text and diagrams, or an equivalent *.pdf file.
Due date Milestone
TBD Topic and outline (not graded)
Abstract and references (not graded)
1st Review Version (not graded)
Final Version (graded)
Presentation in class (graded S/U)
Milestones will facilitate timely feedback to each student.
All term paper authors are required to get someone who is a native-English speaker to review the English of the 1st Review Version and suggest improvements for the Final version. The reviewer shall be thanked by name in the Acknowledgments section at the end of the paper. (Hint: The best reviewer is someone who does not have a technical background.) In order to give your reviewer sufficient time, give your reviewer the Complete version as soon as it is done, prior to grading.
Each term paper author will make a presentation to the class at the end of the semester
on the content of the paper. A Satisfactory grade is
prerequisite to getting credit for the Final term paper.
For CS 4283:
30% Midterm Exam
30% Final Exam
30% Homework
10% Quizzes and participation
For CS 6283:
25% Midterm Exam
25% Final Exam
20% Homework
20% Term Paper
10% Quizzes and participation
The standard scale for grades will be used, namely the following
A 90--100%
B 80--89%
C 70--79%
D 60--69%
F 0--59%
Late assignments will be penalized; assignments more than one week late
will not be accepted, except for excused absences. If necessary, submit
an incomplete assignment on-time, promptly discuss the situation with Dr.
Carver, and submit a complete assignment later by the agreed date.
This strategy will result in a better grade than submitting the entire
assignment late without consultation.
All students must have access to the class web pages.
Copying ideas, sentences, tables, or figures without citation is plagiarism, a form of academic dishonesty. This is a very serious offense, because you make it appear to be your own work, but in fact, it is not. You must include citations and references when you copy.
Receiving unacknowledged help is considered academic dishonesty. When you receive help, other than from faculty, or course materials, you must include citations and references in your work. For example, if you find a useful web page that was not specified in the assignment, then you must include a citation and reference for it. Similarly, if a discussion with someone is helpful, you should thank them by name in the Acknowledgments section, even if collaboration is not allowed on the assignment. (Their discussion may not be considered "collaboration".) Citations and references are optional for informal discussions.
Giving unacknowledged help is also treated as academic dishonesty.
| Date | Topic | Assignment due |
| Jan 8 | Introduction/Overview/What is Software Quality | |
| Jan 10 | Quality Assurance | |
| Jan 15 | NO CLASS - HOLIDAY | |
| Jan 17 | Quality Assurance in Context | |
| Jan 22 | Quality Engineering | |
| Jan 24 | Testing: Concepts, Issues and Techniques | |
| Jan 29 | Test Activities, Management, and Automation | |
| Jan 31 | Coverage and Usage Testing Based on Checklists and Partitions | |
| Feb 5 | Input Domain Partitioning and Boundary Testing | |
| Feb 7 | Coverage and Usage Testing Based on Finite-State Machines and Markov Chains | |
| Feb 12 | Control Flow, Data Dependency, and Interaction Testing | |
| Feb 14 | Testing Techniques: Adaptation, Specialization, and Integration | |
| Feb 19 | MIDTERM EXAM | |
| Feb 21 | NO CLASS | |
| Feb 26 | ||
| Feb 29 | ||
| March 5 | Defect Prevention and Process Improvement | |
| March 7 | ||
| March 12 | NO CLASS - SPRING BREAK | |
| March 14 | NO CLASS - SPRING BREAK | |
| March 19 | Software Inspections | |
| March 21 | ||
| March 26 | Formal Verification | |
| March 28 | Fault Tolerance and Failure Containment | |
| April 2 | Comparing Quality Assurance Techniques and Activities | |
| April 4 | ||
| April 9 | ||
| April 11 | Feedback Loop and Activities for Quantifiable Quality Improvement | |
| April 16 | Quality Models and Measurements | |
| April 18 | Defect Classification and Analysis | |
| April 23 | Risk Identification for Quantifiable Quality Improvement | |
| April 25 | Software Reliability Engineering | |
| April 27 | FINAL EXAM 12:00 - 3:00 |