Software engineering goes well beyond software development. It involves understanding customer needs, planning the development process, teamwork, maintenance, and analysis and evaluation tasks, such as testing, verification, and validation. In CS 521/621, we will explore the state-of-the-art research in techniques that make analysis and evaluation of software easier. Concurrently, student groups will engage in research to push forward that state of the art.
This term will cover the following topics: static, dynamic, and speculative analyses; model inference, model checking, and formal verification; bug localization; mutation and regression testing, and symbolic execution.
Becoming familiar, and a part of cutting-edge research will constitute a major part of this class. There will be three research aspects of the class:
The 621 students will be required to present an existing research paper once during the semester, and will complete the research project. Meanwhile, the 521 students will present an existing research paper twice during the semester, or may opt to complete a research project for extra credit, and in lieu of one of the presentations.
|Room:||142 computer science building|
|Lecture:||Monday and Wednesday 10:35AM–11:50AM|
office: 346 computer science building
office hours: Monday 12:00PM–1:00PM
office: CS lounge (1st floor, computer science building)
office hours: Wednesday 12:00PM–1:00PM
All assignment submissions are through Moodle.
Late policy: Assignment due dates and times are listed on the schedule. All deadlines are sharp and the submission site will be closed at the specified time. No extensions will be granted after the assignment is due. Early requests for extensions will be considered only in extenuating circumstances. No more than one extension will be granted per student.
Students are responsible for submitting all homework and project assignments. A student who fails to submit at least one of the homework or project assignments, or does not participate in the midterm, will receive the grade F for the entire class.521
|Paper summary and presentations||30%|
|Paper summary and presentation||15%|
The project's 25% are further broken down:
|project plan and presentation||7%|
|final report and presentation||11%|
|Sep 3||W||Course Introduction|
|Sep 8||M||Static and Dynamic Analyses Overview|
|Sep 10||W||Models, Tests, Bugs, and Symbols Overview||
Due: M Sept 29, 2014, 9:00AM EDT
|Sep 15||M||Extreme Programming (bring laptop to class): SimSE|
|Sep 17||W||No lecture today (work on HW1)|
|Sep 22||M20140922DynamicAnalysis.pdf||Dynamic Analysis||Dynamically discovering likely program invariants to support program evolution & Purify|
|Sep 24||W||Automated Test Generation||Korat: Automated testing based on Java predicates||
Paper Selection and Idea Proposal
Due: M Oct 06, 2014, 9:00AM EDT
|Sep 29||M||Reproducing Field Failures||Chronicler: Lightweight Recording to Reproduce Field Failures|
|Oct 1||W||Pair Programming (in-class activity)||video||
Due: T Oct 14, 2014, 9:00AM EDT
|Oct 6||M||Speculative Analysis||Early Detection of Collaboration Conflicts and Risks|
|Oct 8||W||Research idea presentations||
Due: W Oct 22, 2014, 9:00AM EDT
|Oct 13||M||Bartolomé day: no class|
|Oct 14||T||Monday schedule: Design exercise|
|Oct 15||W||Design exercise||
Due: M Oct 27, 2014, 9:00AM EDT
|Oct 20||M||Paper presentations on refactoring||RefaFlex: Safer Refactorings for Reflective Java Programs, Refactoring with Synthesis, and Drag-and-Drop Refactoring: Intuitive and Efficient Program Transformation.|
|Oct 22||W||Paper presentations on automated debugging||Are Mutants a Valid Substitute for Real Faults in Software Testing?, Automated Diagnosis of Software Configuration Errors, and Automatic Recovery from Runtime Failures|
|Oct 27||M||Paper presentations on analysis||Averroes: Whole-Program Analysis without the Whole Program, Be Conservative: Enhancing Failure Diagnosis with Proactive Logging, and Checking App Behavior Against App Descriptions||
Due: M Nov 3, 2014, 9:00AM EST
|Oct 29||W||Paper presentations on testing||Coverage Is Not Strongly Correlated with Test Suite Effectiveness, Guided Test Generation for Web Applications, and Sample Size vs. Bias in Defect Prediction||
Due: M Dec 1, 2014, 9:00AM EST
|Nov 3||M||Paper presentations on bug localization and repair||SemFix: Program Repair via Semantic Analysis, Using likely invariants for automated software fault localization, and Will You Still Compile Me Tomorrow? Static Cross-Version Compiler Validation|
|Nov 5||W||Midterm review and architecture||
Final project report
Due: Fr Dec 5, 2014, 11:59PM EST
|Nov 10||M||Midterm (in class)|
|Nov 12||W||Tuesday schedule: no class|
|Nov 17||M||Homework 4 part 1: Performance debugging (in-class exercise; Bring a laptop to class!)|
|Nov 19||W||Watch pre-recorded lecture on "Architectural Decay in Software Systems: Symptoms, Causes, and Remedies": Video|
|Nov 24||M||Homework 4 part 2: Execution visualization (in-class exercise; Bring a laptop to class!)|
|Nov 26||W||Snow day: no class|
|Dec 1||M||Paper and project presentations||Enhancing Symbolic Execution with Veritesting and Automatic patch generation learned from human-written patches|
|Dec 3||W||Security in software||sTile|
Software engineering is at its nature a collaborative activity and it benefits greatly from diversity. This class includes and welcomes all students regardless of age, background, citizenship, disability, sex, education, ethnicity, family status, gender, gender identity, geographical origin, language, military experience, political views, race, religion, sexual orientation, socioeconomic status, and work experience. Our discussions and learning will benefit from these and other diverse points of view. Any kind of language or action displaying bias against or discriminating against members of any group, or making members of any group uncomfortable are against the mission of this course and will not be tolerated. The instructor welcomes discussion of this policy, and encourages anyone experiencing concerns to speak with him.
Students are allowed to work together on all aspects of this class except the midterm. However, for the homework assignments, each student must submit his or her own write up, clearly stating the collaborators. Your submission must be your own. When in doubt, contact the instructors about whether a potential action would be considered plagiarism. If you discuss material with anyone besides the class staff, acknowledge your collaborators in your write-up. If you obtain a key insight with help (e.g., through library work or a friend), acknowledge your source and write up the summary on your own. It is the student's responsibility to remove any possibility of someone else's work from being misconstrued as the student's. Never misrepresent someone else's work as your own. It must be absolutely clear what material is your original work. Plagiarism and other anti-intellectual behavior will be dealt with severely. Note that facilitation of plagiarism (giving your work to someone else) is also considered to be plagiarism, and will carry the same repercussions.
Students are encouraged to use the Internet, literature, and other publicly-available resources, except the homework solutions and test (including quizzes, midterms, finals, and other exams) solutions, from past terms' versions of this course and other academic courses, whether at UMass and at other institutions. To reiterate, the students are not allowed to view and use past homework and test solutions, unless explicitly distributed by the CMPCSI 521/621 staff as study material.
Whenever students use Internet, literature, and other publicly-available resources, they must clearly reference the materials in their write ups, attributing proper credit. This cannot be emphasized enough: attribute proper credit to your sources. Failure to do so will result in a zero grade for the assignment and possibly a failing grade for the class, at the instructor's discretion. Copying directly from resources is not permitted, unless the copying is clearly identified as a quote from a source. Most use of references should be written in the words of the student, placing the related work in proper context and describing the relevant comparison.
Students who violate University standards of academic integrity are subject to disciplinary sanctions, including failure in the course and suspension from the university. Since dishonesty in any form harms the individual, other students, and the university, policies on academic integrity have been and will be strictly enforced.
There is no required textbook for the course. Reading assignments will come from publicly available research papers. Students who wish to read established textbooks beyond the assigned reading should consider:
Students should have taken an introductory course in software engineering or have the equivalent background. Students are expected to be familiar with an object oriented programming language, such as Java or C++. Some programming and the ability to download and use off-the-shelf tools are expected.
Various materials used in this course have greatly benefited from materials developed by Alex Aiken, Lori Clarke, Carlo Curino, Sebastian Elbaum, Michael Ernst, David Notkin, Nenad Medvidovic, Alex Orso, Lee Osterweil, Willem Visser. Thank you.