Important Dates for Sponsors of a Team Project

Monday October, 18, 2010 Instructor sends email to potential sponsors inviting them to sponsor a project in CS 490
Monday October 25, 2010 A "Yes" or a "No" from the potential sponsor expected by this date.
Monday November 1, 2010 A 1-paragraph description of the proposed project due to the instructor. This could be sent via email.
Friday November 5, 2010 Instructor's feedback to the sponsor due by this date.
Monday November 15, 2010 First draft of the project requirements document due by this date. Word or pdf formats are acceptable. Sample requirements documents from a previous class on Software Engineering are available (Motorola Telllabs). Your document need not be as detailed. Please ensure that your project is directly in the area of Software Testing.
Friday November 19, 2010 Instructor's feedback on the requirement document due.
Friday December 3, 2010 Final draft of the requirements document due.
Monday December 6, 2010 Requirements documents from all sponsors available to potential CS 490 students via the course web site.
Types of projects:
  1. Empirical study: Evaluate a technique, a test tool, a model, or some test related artifact.
  2. Development: (a) Develop a prototype tool for a specific testing task. (b) Develop and evaluate a set of tests for a specific product.
  3. Each team will consist of 3-4 students.

Project areas:

No constraints on the area..make sure that your project falls in the area of software testing (unit, integration, system, acceptance, etc.). The project could be related to random testing, stress testing, performance testing, security testing, WEB services testing, database testing, medical device testing, audio device testing, combinatorial designs, model based testing, coverage analysis, black box testing, while box testing, etc., etc.

Licensing

Please try to assign projects that do not require any special licensing requirements. The project is educational in nature and open to all registered students in the course. We will protect any equipment or software available you make available to us for use by the students and course personnel.