Electrical Engineering & Computer Science School of Engineering University of Kansas

Transcription

1 Electrical Engineering & Computer Science School of Engineering University of Kansas Course Title EECS814: Software Quality Assurance Fall 2007 (14322) Thursdays, 7:10 10:00 PM, Regnier Hall 151 Course Web Site: saiedian/teaching Prerequisites/Expected Audience. Eligibility for upper division EECS courses, EECS810, EECS848 (or industrial experience in software development and programming). This course is intended for software engineers, software development managers, and graduate students in computer science. Graduate standing in computer science, introductory courses in software engineering or systems analysis, or industrial experience in software development is assumed. Instructor Professor Hossein Saiedian Primary Office: 125 Regent Center Research Office: 157 Nichols Hall Telephone (913) (Lawrence Campus: ) Fax: (913) (Lawrence Campus: ) WWW: saiedian Office Hours: Tuesdays & Thursdays, 1:00 3:00 PM any by Appointments Course Overview This course will focus primarily on the practical aspects of software quality assurance. Topics to be covered will include various testing techniques (and related test data generation strategies), static verification techniques (formal technical reviews and formal verification), standards, metrics and measurements, managing and controlling change, and developing quality assurance plans. 1/9

2 Textbooks Resources Paul C. Jorgensen, Software Testing: A Craftsman s Approach, 2nd Edition, CRC Press, Cem Kaner, James Bach, and Bret Pettichord, Lessons Learned in Software Testing, Wiley, Additional reading materials will be distributed during the class sessions. Evaluation Criteria (Subject to revision) Students will be evaluated as follows: Grade Distribution: Exams and Quizzes: 40% Assignments: 40% Special Project: 20% Grading Scale: A = 90%..100% B = 80%..89% C = 70%..79% D = 60%..69% No make-up quizzes are given. No late work will be accepted. (Certain exceptions may be made for family emergencies, religious observance, and illnesses.) All written work must be typed. It is OK to draw diagrams by hand, but they must be legible. Please see the guidelines for electronic submission of your class materials Special Projects The purpose of the special project is to provide a student with an opportunity for individualized study in a specific area of software quality assurance (to be approved in advance). The outcome of the individualized 2/9

3 study should either be a comprehensive workshop-type presentation on an approved topic or a quality term paper. For the workshop-type presentation, a student has two choices: (1) read one or more of the general books on quality (subject to approval) and then relate the read materials to the area of SQA, (2) provide a comprehensive tutorial on a topic or thoroughly review current development in an area or a specific technique that has been supported by practical implementation or evaluation. These include (but are not limited to): Testing object-oriented systems Testing web applications Practical software measurement/metrics for quality assurance Formal technical reviews/code inspection (e.g., Fagan s approach) Static program analysis and verification CMMI and its family of capability maturity models Those students who would like to do a term paper should visit with the instructor for topic approval. The guidelines for writing a term paper must be strictly followed. Attendance Attendance is important and required. If a student misses a class session, he or she will be entirely responsible for learnings the materials missed without the benefit of a private lecture on the instructor s part. Furthermore, the student will be responsible for finding out what assignments may have been given and when they are due. Class Organization There will be instructor, students, guest lecturer, and video tape presentations (subject to time availability). As part of their special projects, a student may make a comprehensive workshop-type presentation on an approved topic. Students are expected 3/9

4 to carefully read the Guidelines for Making a Presentation. Student presentations should simulate discussion. Plan your time to allow for a healthy and lively discussion. Presentation viewgraphs should be made available before the presentation. Students are expected to actively participate in all classroom discussions, presentations, and regularly make contributions such as offering comments, asking interesting questions, and responding with good answers. Instructor s Judgment. The instructor reserves the right to change a quantitatively-determined grade depending on their judgment of a student s understanding of the course topics; the judgment will be based partially on a student s ability to actively and constructively participating in class discussions. Additional Reading Recommendations Textbooks are excellent reference and tutorial resources. Most up-todate topics, discussion, and viewpoints on software quality and testing can be found in technical journals and recent conference proceedings. Students should develop a habit of regularly browsing such journals as IEEE Software, IEEE Computer, Communications of the ACM, IEEE Transactions on Software Engineering, Software Quality Journal, and Journal of Systems and Software. The proceedings of the International Conference on Software Engineering (ICSE) as well as the proceedings of the International Symposium on Software Testing and Analysis provide a wealth of information on recent state of the art research and practice results. Communication communication is fast, flexible, and efficient. Important classroom related items will be communicated via . At your earliest convenient time, please send your favorable address (preferably address) in an one-liner message with the following information only: EECS814 Fall 2005, FName LName, Address, Tel Number 4/9

5 Please exclude any other information (e.g., signature files) from your message. Telephone numbers will be helpful if we need to contact you in cases where may not be most effective, but if you do not wish to give out your telephone number, it is OK. Do not send in HTML format; it will not be processed. Unless you are specifically asked to send a document (preferably in PDF), send textonly s in ASCII format. See the Guidelines for Submitting Electronic Documents. Important Dates First Class Day: Thursday August 16th Labor Day: Monday September 3rd Exam 1: Thursday September 20th Fall Break: Thursday October 11th Sunday October 14th Exam 2: Thursday October 25th Thanksgiving Break: Wed. November 21th Sun. November 25th Last Class Day: Thursday December 6th Final Exam: Thursday December 13th, 7:00 10:00 PM Resources on SQA and Testing Software Quality Journal A journal devoted to SQA Software Testing, Verification and Reliability A journal devoted to software testing International Symposium on Software Testing and Analysis A conference devoted to software testing 5/9

6 Roger Pressman On-Line Resources Quality management Testing strategies Testing methods Software Testing and SQA Books B. Beizer, Software System Testing and Quality Assurance, Van Nostrand Reinhold, B. Beizer, Software Testing Techniques, Van Nostrand Reinhold, B. Beizer, Black-Box Testing, Wiley, I. Burnstein, Practical Software Testing, Springer, S. Kan, Metrics and Models in Software Quality Engineering. 2nd Edition, Addison-Wesley, J. McGarry, D. Card, C. Jones, B. Layman, E. Clark, J. Dean, and F. Hall, Practical Software Measurement, Addison-Wesley, G. Meyer, The Art of Software Testing, Wiley, 1979 (revised 2004). General Quality Books P. Crosby, Completeness: Quality for the 21st Century, Plume, P. Crosby, Quality Without Tears, Plume, P. Crosby, Quality is Free, Mentor, /9

7 W. Latzko and D. Saudners, Four Days with Dr. Deming, Addison-Wesley, K. Ozei and T. Asaka, Handbook of Quality Tools: The Japanese Approach, Productivity, T. Peters and R. Waterman, In Search of Excellence, Warner Books, Excellent Background Articles Static Analysis: Reviews and Inspections M. E. Fagan, Design and code inspections to reduce error in program development, IBM Systems Journal, 38(2&3), pp , H. D. Mills, M. Dyer, and R. C. Linger, Cleanroom Software Engineering, IEEE Software, 4(5), September 1987, pp A. Porter, H. Siy, C. A. Toman, and L. G. Votta, An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development, IEEE Transactions on Software Engineering, 23(6), June 1997, pp Dynamic Analysis H. Zhu, P. A. V. Hall, and J. H. R. May, Software Unit Test Coverage and Adequacy, ACM Computing Surveys, 29(4), December 1997, pp Assertions D. S. Rosenblum, A Practical Approach to Programming with Assertions, IEEE Transactions on Software Engineering, 29 (4), January 1995, pp Error Seeding A. J. Offutt, A Practical System for Mutation Testing: Help for the Common Programmer, 12th International Conference on Testing Computer Software, Washington, D.C., June 1995, pp Coverage Criteria S. Rapps and E. J. Weyuker, Data Flow Analysis Techniques for Test Data Selection, Proc. International Conference of Software Engineering, Tokyo, Japan, September 1982, pp /9

8 L. A. Clarke, A. Podgurski, D. J. Richardson and Steven J. Zeil, A Formal Evaluation of Data Flow Path Selection Criteria, IEEE Transactions on Software Engineering, 15(11), November 1989, pp Dependency Analysis M. Weiser, Program Slicing, Proc. International Conference on Software Engineering, San Diego, Ca 1981, pp D. W. Binkley and K. B. Gallagher, Program Slicing, Advances in Computers, Vol. 43, M. Zelkowitz, editor, Academic Press, 1996 pp Regression Testing G. Rothermel and M. J. Harrold, Analyzing Regression Test Selection Techniques, IEEE Transactions on Software Engineering, 22(8), August 1996, pp T. L. Graves, M. J. Harrold, J. M. Kim, A. Porter and G. Rothermel, An Empirical Study of Regression Test Selection Techniques, ACM Transactions on Software Engineering and Methodology, 10(2), April 2001, pp Software Verification S. King, J. Hammond, R. Chapman and A. Pryor, Is Proof More Cost- Effective Than Testing? IEEE Transactions on Software Engineering, 26(8), August 2000, pp Messages From the Writing Center The KU Writing Center is a free, university-wide service for all students, faculty, and staff on a drop-in basis or by appointment. Trained writing consultants, undergraduate and graduate students from a variety of disciplines, are available to work with writers on their writing projects, theses and dissertations, articles, grant proposals, etc. Satellite locations, called Writer s Roosts, are open on the Lawrence and Edwards Campuses. Writers may also submit writing via or make an appointment for a real-time consulting session... (please visit for current hours and locations). KU subscribes to a digital plagiarism detection program, turnitin.com, which may be used to check papers submitted in a course. You may be asked to submit your papers in a digital format ( attachment,..., 8/9

9 or on disk) so that your paper can be checked against web pages and databases of existing papers. Although you may never have engaged in intentional plagiarism, many students do incorporate sources without citations; this program can alert a faculty to your academic needs. 9/9