• January 22, 2004:
  CHIANTI: A Change Impact Analysis Tool for Java
  
  Presenter:Barbara Ryder
  Slides
  

• January 29, 2004
  Overview of Testing Methodology
  
  Presenter:Tom Marlowe
  Slides Prepared for DFA
  Slides Prepared for Testing
  

• February 5, 2004:
  An Applicable Family of Data Flow Testing Criteria
  P.G.Frankl, E.J. Weyuker
  IEEE Transactions on Software Engineering,Octobor 1988.
  
  Presenter:Shwetha Nagaraj
  
  
• February 12, 2004:
  Dynamically discovering likely program invariants to support program evolution
  Michael D. Ernst, Jake Cockrell, William G. Griswold, and David Notkin.
  IEEE Transactions on Software Engineering Feb. 2001
  
  Presenter: Xiaoxia Ren
  Slides
  
  
• February 19, 2004:
  Adequate testing and object-oriented programming
  D. Perry and G. Kaiser
  Journal of Object-Oriented Programming, 2(5):13--19, Jan. 1990.
  
  Background paper:
  Axiomatizing Software Test Data Adequacy
  Elaine J. Weyuker
  IEEE Transactions on Software Engineering,Dec,1986
  Presenter: Brian Russell
  Slides
  
  
• February 26, 2004:
  A System to Generate Test Data and Symbolically Execute Programs
  CLARKE, L
  IEEE Transactions on Software Engineering SE-2, 3 (September 1976), 215-222.
  Only hard copy available.
  
  Refining Data Flow Information Using Infeasible Paths
  Proceedings of the Sixth European Software Engineering Conference (ESEC/FSE 97)
  Rastislav Bodik, Rajiv Gupta, Mary Lou Soffa
  
  Presenter: Chen Fu
  
  
• March 4, 2004:
  Break
  
  
• March 11, 2004:
  A Formal Model of Program Dependences and Its Implications for Software Testing, Debugging, and Maintenance
  Andy Podgurski, and Lori.A.Clarke
  IEEE Trans. on Software Engineering Sept.1990.
  You can go and get the paper through Rutgers libraries website to get the free access to the paper.
  Presenter: Weilei Zhang
  Slides
  
  
  
• March 18, 2004:
  Spring Break
  
  
• March 25, 2004:
  Prolangs research talk.
  Presenters: PROLANGSers
  
  
• April 1, 2004:
  Exploiting Purity for Atomicity
  Cormac Flanagan (University of California, Santa Cruz) , Stephen Freund (Williams College), Shaz Qadeer (Microsoft Research)
  
  Please come to PROLANGS to get a copy for the paper.
  Presenter: Thomas J Marlowe
  Slides
  
  
• April 8, 2004:
  Invited Speaker : Larry Kovad
  Beyond Code Generation: Using compiler technology for security and software defect identification
  Compiler and optimization technology has a rich history. Traditional use of the technology has been for code generation through a variety of intra- and inter-procedural code analyses. We have been exploring the use of the same basic techniques to address hard problems in security and software defect identification. A number of factors make the analysis problems more challenging. A significant trend in software development is the reuse of components -- from libraries to entire applications. Often the source code for these components is not available. The size and complexity of the software to be analyzed can be quite large, making the analysis even more challenging. This talk will give a high level overview of two of our projects that use whole program control and data flow analyses:
  We have been developing a variety of security analyses of Java applications (e.g., servlets, applets, applications). For example, one of the most difficult challenges for an application developer or system administrator is identifying the security authorization requirements of Java applications ("Permissions" to grant the application). The traditional approach is either to turn off security or to run test cases to observe authorization failures and add the required Permissions to the authorization database until the application no longer fails. This talk describes a better approach that automatically computes the authorization policy for an application.
  Another project, called SABER, uses whole program analysis to identify coding defects in application code. Saber identifies code that may result in performance problems, outright failure of an application, or violates "best practices" (coding conventions). For example, a performance may result when an application uses a class or method that is known to result in poor performance when used in a particular context (e.g., calling the garbage collector during garbage collection). This talk will give an overview of the types of defects that SABER can discover.
  
  papers to be covered:
  OOPSLA 2002 paper
  A tech report describing the SABER project
  ISSTA 2004. Please come to PROLANGS to get a copy for this paper.
  
  
• April 15, 2004:
  The Chaining Approach for Software Test Data Generation
  Roger Ferguson,Bogdan Korel
  ACM Transactions on Software Engineering and Methodology (TOSEM), Jan, 1996
  Presenter: Kien Le
  
  
• April 22, 2004:
  Research Talk
  Presenter: Max Stoerzer
  
  
  
• April 29, 2004:
  Break
  
  
• May 6, 2004:
  Tool support for testing concurrent java components
  Brad Long,Daniel Hoffman,Paul Strooper
  IEEE Transactions on Software Engineering, June,2003
  Presenter:Tuan Phan
  
  

For any broken links or other mistakes, please email to , thanks!

Last updated by zwl on April 21 , 2004.