EEC 623/723 Software Quality Assurance

Syllabus (Spring 2009)

Instructor:Yongjian Fu	Office: SH 432	Phone: 216-687-5518	Email : mailto:yongjian@umr.edu
Prerequisites: EEC 521		Credit Hours: 4
Classes : TTh 4:00-5:50pm SH 324		Office Hours: TTh 1:30-3:30
WWW: http://academic.csuohio.edu/fuy/EEC%20623

Objective/Description:

This course introduces concepts, metrics, and models in software quality assurance. The course covers components of software quality assurance systems before, during, and after software development. It also discusses metrics and models for software quality as a product, in process, and in maintenance. The CMM developed by SEI will be introduced, as well as related ISO and IEEE standards. Students will develop an understanding of software quality and approaches to assure software quality .

Required Textbook:

Daniel Galin, Software Quality Assurance : From Theory to Implementation, Addison Wesley, 2003.

Reference Book:

Kan, S., Metrics and Models in Software Quality Engineering (2^nd Edition), Addison Wesley, 2002.

Other Materials:

Schulmeyer, G. Gordon and McManus, James, (eds), Handbook of Software Quality Assurance, 3rd Ed. Prentice Hall, 1999.

Grading:

Homework:                  20%
Lab:                       20%
Quiz:                      20%
Final exam:                40%

90%-100%                   A
87%-89%                    A-
83%-86%                    B+
80%-82%                    B
76%-79%                    B-
60%-75%                    C
0%-59%                     F

There will be three to four homework assignments. The homework assignments are due in a week, unless specified otherwise in the homework handout.
A number of quizzes will be held in class. Each quiz is counted equally for the grade. The date of quiz will be announced in class.
A few labs are planned for the class. The labs use various software.
The date for the final exams is decided by the CSU academic calendar.

Course Topics:

Date	Topic	Readings	Notes
1/20	Introduction	Galin, Ch. 1, 2
1/22	Software quality factors	Galin, Ch. 3	HW1
1/27	Components of SQA	Galin, Ch. 4
1/29	Pre-project components	Galin, Ch. 5, 6
2/3	SQA plan	Galin, Ch. 7	HW2
2/5-2/10	Defect removal effectiveness	Kan, Ch. 6
2/12-2/17	Reviews	Galin, Ch. 8
2/19-2/26	Testing	Galin, Ch. 9, 10	Lab 1
3/3	Maintenance, External participants	Galin, Ch. 11, 12	HW3
3/5-3/12	Configuration management	Galin, Ch. 18	Lab 2
3/24	Standards	Galin, Ch. 23, 24
3/26	Cost of software quality	Galin, Ch. 22
3/31-4/2	Software quality metrics	Galin, Ch. 21, Kan, Ch. 4	HW4
4/7-4/14	Rayleigh model	Kan, Ch. 7	Lab 3
4/16	Exponential and reliability growth model	Kan, Ch. 8
4/21-4/23	Metrics for OO projects	Kan, Ch. 12
4/28	Management	Galin, Ch. 25
4/30	Units	Galin, Ch. 26
5/5	Future	Galin, Epiloge
5/7	Review
5/12	Final

Note: the schedule and topics are subject to change. The dates for homework and labs are tentative and for guidance only.

Course Policies:

Attendance to all classes is required. Each student is responsible for his/her missed classes.
No makeup lab/quiz/exam will be given. No extra credit work will be given.
A student who misses two or more classes must see the instructor immediately with an explanation.
Class submissions are due in class on the specified date. Late reports will receive the penalty of 10% per day up to two calendar days. No submissions will be accepted two calendar days after the due date.
Talk to instructor for special cases, such as illness. Proper documents, such as a doctor's note, may be required as a proof.
Discussions on homework and labs are allowed, but all course work must be individually done. Any forms of cheating may cause penalties, from getting an F in the course to academic actions according to the department's policy. A copy of the policy is distributed in the class and is available on departmental web site http://www.csuohio.edu/ece/Ethics Policy.doc.