The goal of this course is to introduce how various analysis techniques can be used to manage the quality of a software application. Students will acquire fundamental knowledge of program abstraction, features, verification, testing, analysis, concurrency, reliability, aspect orientation, and fault detection. The course will also discuss how to carry out the empirical experimentation for program analysis. Wherever applicable, concepts will be complemented by tools developed in academia and industry. This enables students to understand the maturity and limitations of various analysis techniques.
The intent of this course is to offer the in-depth introduction to graduate students on a wide range of software analysis concepts and techniques. The topics can be explored at different levels of depths depending on the interests of the class. The content of the course is roughly divided into two general themes: program representation and program analysis. Following the first theme, we study different abstractions, representations, and interpretations of a software program itself. Following the second, we study how analysis techniques and algorithms can help interpret the runtime meaning of the program and, in turn, help us monitor and improve the quality of the software programs..
If you are interested in doing research in the area of software analysis, this course can help you get started; if you are currently involved in research in other areas such as operating system, networking, security, and database, this course can help you apply the techniques learned in this course to your research area.
Workload and Evaluation
This course will have three homework assignments, a number of paper readings and a paper presentation, a final project. There is no final exam. The following grading policy will be used:
|Paper review and presentation:||20%|
Late Policy: The late submission will have 2% penalty for each hour after the due time.
We'll have three homework assignments. These assignments will help you understand some basic principles of program analysis. Checkout more details at Assignment and Project.
We will discuss a few important research papers selected from top programming language, software engineering, and system conferences. For each paper, one student will be the designated presenter and start off the discussions. Each presentation should be within 20 minutes to cover the following key points of the paper:
- What problem is the research trying to solve? Is it important? Why?
- How does the technique work?
- How is the technique/algorithm evaluated?
- What are the primary contributions of the paper as the author sees it??
- How could this research be extended, or applied in other contexts?
- Questions and Discussion Topics?
Everyone is expected to read all papers that will be discussed and participate actively in the discussions. Course participants will be able to indicate their preferences for papers that they want to present, and an effort will be made to respect everyone's preferences.
You are required to write a short summary for each paper you read. The summary can include:
- Problem domain: background, motivation, why this problem is important/novel/interesting.
- Idea of the paper: assumption, main technique, result.
- Comparison with related work.
- Possible future work/direction.
- Pros, cons of the paper (your conclusion).
- What can we do based on this work: lesson learned from this work? stimulate new related problem? flawed assumption/technique can be improved/extended? technique can be used to other domains? ...
The final project is the key of this course. It is essentially a mini research project that may involve building a new system, designing a new algorithm, improving an existing technique, applying an existing technique to a new domain, or performing a large case study. You are encouraged to come up with a topic of your own, which I'll help refine; alternatively, you can choose one of the projects I suggest. You must work on your project individually. The timeline of the project is as follows:
- 9/26 -- Proposal. Choose a topic and submit a 1-page proposal (due 9/25 11:59 pm). You will give a 5-minute presentation of your project proposal in class.
- 11/7 - 11/9 -- Project progress report. Give a 10 minute presentation on the progress of your project.
- 11/28 - 12/7 -- Project presentation and demo.
- 12/11 11:59 pm -- Final report. Submit a 6-page final report, your source code, and all relevant data (share your git repo with me).
There are no formal prerequisites, but it will help to have some background in programming languages, compilers, software engineering, and/or operating systems in general; and program analysis, parallel/concurrent programming, and/or software reliability in particular.
The enrollment is open to PhD and MS students. If you are an undergraduate and would like to take the course, please email the instructor for special permission.
All relevant materials will be made available online. See Course Syllabus.
There is no required textbook, but the following two books are recommended:
Ethics & Academic Integrity
We will study/discuss threats and attacks in the class/lab. You should be fully aware of ethics when studying these techniques. If in any context you are not sure about where to draw the line, come talk to me first.
"An Aggie does not lie, cheat, or steal or tolerate those who do." For additional information, please visit: http://aggiehonor.tamu.edu.
Upon accepting admission to Texas A&M University, a student immediately assumes a commitment to uphold the Honor Code, to accept responsibility for learning, and to follow the philosophy and rules of the Honor System. Students will be required to state their commitment on examinations, research papers, and other academic work. Ignorance of the rules does not exclude any member of the TAMU community from the requirements or the processes of the Honor System.
Americans with Disabilities Act (ADA) Statement
The Americans with Disabilities Act (ADA) is a federal anti-discrimination statute that provides comprehensive civil rights protection for persons with disabilities. Among other things, this legislation requires that all students with disabilities be guaranteed a learning environment that provides for reasonable accommodation of their disabilities. If you believe you have a disability requiring an accommodation, please contact Disability Services, in Cain Hall, Room B118, or call 845-1637. For additional information visit http://disability.tamu.edu.
|8/31||Static and Dynamic Analyses||Coverity, AddressSanitizer, Static and Dynamic analysis||Dr. Huang|
|2||9/5||Syntax, Grammar, Parsing||Dragon book (Ch 4-5)||Dr. Huang|
|9/7||Program Analysis Frameworks||Soot, WALA, LLVM, Pin||Dr. Huang|
|3||9/12||Data-flow Analysis||PPA (Ch 2)||Dr. Huang|
|4||9/19||Pointer Analysis||Points-to Tutorial||Dr. Huang|
|9/21||Call Graph Construction||Call Graph Tutorial||Dr. Huang|
|9/28||Symbolic Execution||Symbolic Execution: Three Decades Later, KLEE||Dr. Huang|
|6||10/3||Taint Analysis||Dynamic Taint Analysis and Forward Symbolic Execution||Dr. Huang|
|10/5||Concurrency||Concurrency bug study||Dr. Huang|
|7||10/10||Paper Presentation||RacerX, RaceFuzzer||Bozhen, Bowen|
|10/12||FastTrack, DataCollider||Gang, Sungkeun|
|8||10/17||Pointer Analysis using BBD, Program Analysis via Graph Reachability||Patrick, Shiyou|
|10/19||Efficient Path Profiling, Memory Leak Detection||Raaja, Yi|
|9||10/24||DART, CHESS||Anuj, Siddhant|
|10/26||Delta Debugging, Statistical Debugging||Zhen, Vivek|
|10||10/31||Project week||Happy hacking!|
|11||11/7||Project Progress Report||Action time!|| Vivek, Zhen, Siddhant,
Anuj, Yi, Raaja
|11/9|| Shiyou, Patrick, Sungkeun,
Gang, Bowen, Bozhen
|12||11/14||Project week||Happy hacking!|
|13||11/21||Project Experience Sharing|
|14||11/28||Final Project Presentation||Exciting project demos!||Bozhen, Sungkeun, Shiyou|
|11/30||Vivek, Anuj, Zhen|
|15||12/5||Patrick, Yi, Raaja|
|12/7||Siddhant, Gang, Bowen|