CS 49000 Software Testing
Spring 2011
Project Team/Test Tools
[Teams and assignment to projects to be announced at this site on January 20, 2011. Tools assignment revised: April 5,, 2011]
| Teams | BSOD: Microsoft | SEGFAULT: Microsoft |
yoADO: Microsoft |
Team 4: AEC | ||||||||||||||||||||||||
| Team Leader | Christopher Ruderschmidt | Jaideep Singh | Timothy Jarzombek | Sanmeet Kanhere | ||||||||||||||||||||||||
Team members |
Steve Gall |
Ankit Buti
|
Ka Hang Jacky Lok Dustin Gahimer |
|||||||||||||||||||||||||
| Test tools/Presentation date [Tools in red are yet to be presented.] |
|
|
|
|
About team projects:
Team projects allow students to learn planning, report writing, teamwork, preparing and making presentations, and interacting with a customer.
Students are asked to form teams of five to six. The maximum team size will depend on class enrollment, higher enrollment leading to larger team sizes with a limit of six. An early lecture will be devoted to familiarizing the students with what is involved in team projects and how they will be graded.
Each team will be assigned a commercially or instructor sponsored project that offers an opportunity to learn about the practice of software testing throughout the software life cycle, and relate it to the topics covered during lectures. A variety of companies will be requested to offer projects. While the instructor will grade each project, a representative from the sponsoring company, and the instructor, will regularly interact with the corresponding team to resolve any technical issues related to the project. This procedure has been used successfully since 1991 in CS 406 Software Engineering (now CS 307).
Team progress will be evaluated on a regular basis through in-class presentations, demonstrations, and written reports. Final grade for each team member will be computed using the Individual Contribution Index (ICI) determined at the end of the semester. The ICI is a number between 0 and 1 that determines the relative contribution of a team member towards meeting the overall project objectives. A 0 indicates no contribution while a 1 indicates the highest contribution. A detailed procedure for computing the ICI has been successfully used for many years to evaluate team projects in Software Engineeringand Software Testing classes. Students have been generally satisfied with this student- as well as instructor- centered procedure.
Last update:April 12, 2011