Objective Textbook Workload Schedule Grading Teamwork Porformance
CSE 5321. SOFTWARE TESTING
Instructor: Dr. David Kung
Objective Textbook Workload Schedule Grading Teamwork Porformance
CSE 5321. SOFTWARE TESTING
Instructor: Dr. David Kung
Chapter 8: Software Quality Assurance
Chapter 17: Software Testing Techniques
Chapter 18: Software Testing Strategies
Chapter 23: Object-Oriented Testing
Lecture 1: Introduction to software testing
Lecture 2: Software testing tools (JUnit, JavaScope/jcoverage, and perhaps HttpUnit)
Lecture 3: Software testing techniques
Lecture 4: Testing web applications
Lecture 5: Testing object-oriented software - ClassBench
Lecture 6: Testing object-oriented software - other methods
Lecture 7: Object-oriented software testing problems
Lecture 8: Testing component-based software
Lecture 9: Software testing in the life cycle
Lecture 10: Formal review techniques, active design review
Lecture 11: Software quality assurance in the life cycle
2 individual testing projects: 20% each
1 team project: 40%
1 midterm exam: 20%
| Total Score | >= 85 | >= 70 | >= 60 | >= 50 | < 50 |
| Grade | A | B | C | D | F |
The grades are computed by a program according to your scores. If you get 84.95 then you will get a ``B'', not an ``A'' even if the score is so close to 85.
Individual Assignments:
1) Correctness -- the solution adequately solves the given problem
2) Soundness -- the solution is well justified
3) Efficiency -- the solution is among the simplest ones possible
4) Organization -- the presentation of the solution is easy to
understand and logically organized
5) Clarity -- the solution is clearly stated
6) Grammar, spelling, and writing -- correct grammar and spelling, and
legible writing
1) -- 2) are worth about 60% of the weight and 3) - 6) about 40%.
Team Project:
1) Requirements -- identification, formulation and presentation of the requirements, evaluated in terms of completeness, consistency, validity and understandability. 15 %
2) Design -- fulfillment of the requirements, software design considerations, user interface design and component interface design, evaluated in terms of completeness, consistency, validity, user-friendly, effectiveness and efficiency. 15 %
3) Implementation -- evaluated in terms of correctness, efficiency, and coding style. 15 %
4) Teamwork -- teamwork spirit, evaluated in terms of cooperativeness, enthusiasm and unity. 15 %
5) Documentation -- professionally produced reports and models, evaluated in terms of report organization, completeness of standard report items, art work, expression and spelling. 15 %
6) Oral presentation -- evaluated in terms of informativeness to the audience, well-organized and well-prepared vugraphs and dynamic oral communication skills. Make sure that your demo will work in the classroom rather than in the lab. 15 %
7) Oral presentation attendance -- timely attending all the presentations and actively participating in the discussions (such as asking questions, making remarks, etc.) are an important part of the course project. Each absence (without prior permission) will result in 10 % deduction for the part of the project work. You can request only one or two permissions for the whole semester.
Requests for permission to go home before the final exam date will not be granted except for medical reasons and with a proof from a doctor.
If the course has a team project, please email the following to the TA and the instructor right after the census date:
Team project (with 1 -- 3 priorities) and team leader and team member names, email addresses and phone numbers.
Enclosed at the end of this syllabus is a team member evaluation form which must be submitted by every team member after each increment. The form is also available from ftp website.
Use this form to appraise those team members that you feel their contributions should be credited and provide the instructor information about team members who need improvement. I will keep this confidential.
I will broadcast using cse5321@homer important messages, homework assignments, project descriptions etc. to students of the class. The messages will be delivered to your omega account. If you do not receive such messages, please contact me immediately so that I can add you to the list. It is your responsibility to contact me when your omega account has changed.
After each assignment or test has been graded, I will distribute to each of you your scores and grade up to that assignment or test. You will also receive class performance statistics. Timely distribution of such information requires that the TA email me the scores in time. Please help me to remind the TA to email me such information.
(817) 272-3000, ext. 4938; email lsmith@library.uta.edu
http://www.uta.edu/library/research/rt-cse.html for CSE research information.
Most team members perform well in a project team. However some members perform extremely well and some very poorly. It is constructive to encourage the outstanding members and inform those who need improvements. This form allows you to convey such information to your team members whenever you deem there is such a need.
Please give an integer rating of -2 (poor), -1 (below average), 0 (average), +1 (above average), or +2 (excellent) for some of the aspects of the members you want to convey your assessment. Your evaluation might be reproduced (to hide your identity) and presented to the relevant members. The identity of the evaluator will be kept absolutely confidential in all cases.
| Member name | |||||
| Group meeting attendance | |||||
| Group discussion | |||||
| Individual assignment | |||||
| Technical contribution | |||||
| Organizational contribution | |||||
| Overall performance | |||||
Comments: (use additional sheets if needed)
Name: