Instructor: William
S. Junk, Computer Science Dept., University of Idaho, PO Box 441010, Moscow,
ID 83844-1010
Telephone: 208-885-7530, 800-824-2889 Ext 7530 Fax:
208-885-9052
E-Mail: billjunk@cs.uidaho.edu
WWW: http://www.cs.uidaho.edu/~billjunk/
Engineering Outreach US Mail:
Bill Junk, Engineering Outreach, University of Idaho, PO Box 441014, Moscow,
ID 83844.
Engineering Outreach Fed Ex & UPS: Bill Junk,
Engineering Outreach, University of Idaho, Janssen Engineering Bldg Room 35,
Moscow, ID 83844-1014.
CS Dept US
Mail: Bill Junk, Computer Science
Dept., University of Idaho, PO Box 441010, Moscow, ID 83844-1010
CS Dept Fed Ex & UPS: Bill
Junk, Computer Science Dept., University of Idaho, Janssen Engr Bldg Room 234,
Moscow, ID 83844-1010
Office Hours: My
Schedule
This course will study some of the major areas related to software quality, including:
We will study software development from a perspective that places emphasis on achieving a high quality product, with particular concern for how user view the product. We will study many of the techniques currently being used in the development of medium to large scale software systems and assess what impact they have on software quality. This is not a programming project course.
UI Catalog Description: CS J484/J584 Software Quality Assurance (3 cr). Actions necessary to provide confidence that a software product conforms to established technical requirements; strategies for implementation and management of SQA, product reviews, test plans and procedures, audits, configuration management, and reliability assessment; concepts of software quality. Additional projects/assignments reqd for grad cr. Prereq: CS 381
Prerequisites: (CS Majors, CompE Majors, and CS Minors) Certified for upper division course work in computer science and completion of CS 381 Software Engineering. (Non-CS Majors) Experience in development of moderate sized programs in a structured, high-level language. Knowledge of C, C++, or Java programming is helpful and the ability to read and understand simple C or C++ programs is required. Examples in these languages will be used to illustrate some fundamental programming ideas.
Textbook: No textbook has been specified for this semester's course. Copies of PowerPoint slides will be made available to all class participants. Additionally I expect you to find relevant material in journals, magazines, conference proceedings, books, and on the Internet.
Class Meetings: The course schedule is a guide to the coverage of course material. In preparing for each class please use resources that you have available including those in libraries or on the Internet . We will also do in-class activities to explore or solidify concepts. Discussion is an important part of this course. Outside reading in trade and professional publications as well as locating material on the Internet is strongly encouraged. Some articles from professional journals may be provided for reading.
You will have a major role in determining your final grade for the course. How this will occur will be discussed during the first few class sessions. Some of the factors to be considered are shown here.
Homework: There will be many individual exercises given. Normally, exercises are due at the start of the next class session. If you are allowed additional time for a particular exercise it will be indicated in the instructions. Written exercises are to be computer printed. Hand written exercises will not be accepted. Drawings may be done by hand, if carefully prepared. If your response to the exercise requires more than one page, staple the pages together in the upper left corner. Make sure your name is on the first page of the exercise.
On-campus students: Do not e-mail your exercises! Bring the hardcopy to class or turn it in at the CS department office.
Off-campus students: When practical, submit your exercises by e-mail.
Submitted exercises will be reviewed for general adequacy, but not individually graded. Solutions will be discussed in class.
Class Participation: All students are expected to make a regular contribution to the class. You should be prepared to offer your comments regarding material presented, ask interesting questions during class, and respond with good answers to questions asked in class. You are especially encouraged to make contribution via e-mail. A significant contribution about every other week is considered a satisfactory participation level.
Exams: A mid-term and a final exam will be given. The exams will be given on the dates indicated in the course schedule. Exams will be used as a way of providing you with feedback on your progress in learning the course material.
Outside Reading: Each student will be required to read and report on published material that is taken from the body of work related to product quality. Students in CS 484 will be expected to review a journal article or technical report. Students in CS 584 will be expected to review a book.
Term Project: A term project on an approved topic in software quality assurance is required. The term project will allow you to demonstrate your depth of knowledge in areas covered by this course.
Academic Integrity: Suffice it to say that academic integrity is expected and academic dishonesty will not be tolerated. Specific guidelines will be distributed and discussed at the first class meeting. The penalty for a single breach of academic integrity can be as severe as receiving a failing grade in the course!
Grading: Final course grades will be based on the following percentage contributions:
| CS 484 | CS 584 / NTU | |
|---|---|---|
| Homework Exercises | 30% | 30% |
| Outside Reading | 10% | 10% |
| Mid-term Exam | 10% | 10% |
| Term Project | 25% | 25% |
| Final Exam | 20% | 20% |
| Class Participation | 5% | 5% |
