Termpaper Proposal

DUE Dates:
Draft (10 points): Mar 3, 2017, 11:59 PM
Final (15 points): Mar 20, 2017, 11:59 PM

1. Topics

Before you write your draft proposal, discuss your topic area and plans with me. Feel free to stop by my office (on-campus students) or send me email (distance students). Topics include, but are not limited to, the following:
  1. Data warehouse testing
    • Systematic Literature Review (SLR)
    • Focus on activities in specific domains (e.g., healthcare, e-commerce)
    • ETL (extract, transform, and load) testing
  2. GUI Testing
    • Android apps (or mobile apps in general)
    • Web application testing
    • UI testing
  3. Mutation testing (including higher order mutation)
    • Area: Web programming, Java
    • Efficient generation of mutants
    • Subsumption relationships between mutants/mutant classes
    • Automatically detecting equivalent mutants
    • Test case generation to kill mutants
  4. Fault localization
    • Functionality related faults
    • Performance bugs
  5. Test input generation
    • Dynamic symbolic execution
    • Search-based testing
  6. Automatic program repair
    • Functionality related faults
    • Performance bugs
  7. Regression testing
    • Model-based based regression test selection
    • Code-based regression test selection

2. Proposal document

The proposal must be 2-3 pages long, 11 pt font size, single column, and single spaced.

The proposal must have a title, author name and affiliations, and date at the top.

If you are proposing a new approach, then the body of the proposal should cover the following topics in numbered sections (though the list below need not match the section titles).

  • The background of the problem
  • A statement of the problem
  • Proposed approach of the problem
  • Proposed evaluation plan with specific metrics
  • Tasks and tools to be used
  • Schedule to be followed
  • References (2-3 to begin with)

If you are comparing approaches or applying approaches in a new setting (e.g., your work/research group), the structure will be a little different.

  • The background of the problem
  • A statement of the problem
  • Approach(es) to be used to solve the problem
  • Proposed evaluation or comparison plan with specific metrics
  • Tasks and tools to be used
  • Schedule to be followed
  • References (2-3 to begin with)

3. Initial Reading List (will be updated)

  1. Yue Jia, Mark Harman. An Analysis and Survey of the Development of Mutation Testing. IEEE Trans. Software Eng. 37(5): 649-678 (2011) Link
  2. Lee Naish, Hua Jie Lee, and Kotagiri Ramamohanarao. 2011. A model for spectra-based software diagnosis. ACM Trans. Softw. Eng. Methodol. 20, 3, Article 11 (August 2011). Link.
  3. Cristian Cadar, Koushik Sen: Symbolic execution for software testing: three decades later. Commun. ACM 56(2): 82-90 (2013). Link.
  4. Martin Monperrus. “Automatic Software Repair: a Bibliography”, Technical Report #hal-01206501, University of Lille. 2015. Link.
  5. Shin Yoo, Mark Harman: Regression testing minimization, selection and prioritization: a survey. Softw. Test., Verif. Reliab. 22(2): 67-120 (2012) Link.

4. Submission

Submit a document called EID_proposal.pdf. For example, I would submit my proposal as ghosh_proposal.pdf. Submit the file using Assignment Submission in Canvas. Two separate submissions will be set up for the draft and final versions. Draft submissions must be made by March 3, 2017. You will get feedback from the instructor. The final version must be submitted by March 20, 2017.