CS 520 introduces students to the principal activities and state-of-the-art techniques involved in developing high-quality software systems. Topics include: requirements engineering, formal specification methods, software design, software testing and debugging, program analysis, and automated software engineering.
This course will cover the following high-level topics:
Besides becoming familiar with Software Engineering principles and best practices, students will learn about cutting-edge research in Software Engineering, Security, and Human-Computer Interaction. The exercises and the group project provide additional hands-on experience in using state-of-the-art techniques.
|Lecture:||Tuesday and Thursday 10:00AM – 11:15 AM via Zoom|
office hours: Mondays 1:00 - 2:00 PM via Zoom, Thursdays after lecture for 30 minutes, Fridays 9:30 - 10:00 AM via Zoom, or by appointment
|Graders:||Sayantan Bhowmik, Anjali Ramaprasad, and Shashank Srigiri|
All assignment submissions are through Moodle. The Zoom links are also available there.
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. Requests for extensions will be considered in extenuating circumstances.
Students are responsible for submitting all assignments to receive a passing grade for the entire class.520
(subject to change; check regularly)
|Feb 2||Tu||Course introduction|
|Feb 4||Th||Software architecture and design|
|Feb 9||Tu||Best and worst programming practices||
Project topic selection
Due: Tue Mar 4, 2021, 9:00PM EDT
|Feb 11||Th||Object oriented design principles|
|Feb 16||Tu||Object oriented design patterns|
|Feb 18||Th||User interfaces||
Homework 1: Code review
|Feb 23||Tu||Version control|
|Feb 25||Th||In-class exercise: Advanced uses of git. Due Mar 3.|
|Mar 2||Tu||Software requirements|
|Mar 4||Th||Collaborative development|
|Mar 9||Tu||Software testing|
Homework 2: Implementation & testing
Project mid-point report (see last section)
|Mar 11||Th||In-class exercise: Software testing.|
|Mar 16||Tu||Model checking|
|Mar 18||Th||Model inference of processes|
|Mar 25||Th||In-class exercise: Debugging.||
Homework 3: Automated reasoning about programs
|Mar 30||Tu||Guest lecture|
|Apr 1||Th||Final project mid-point presentations|
|Apr 6||Tu||Final project mid-point presentations||
Final project completion
|Apr 8||Th||Automated theorom proving|
|Apr 13||Tu||Guest lecture|
|Apr 15||Th||In-class exercise: Automated reasoning about programs.|
|Apr 20||Tu||No class (Wednesday class schedule)|
|Apr 22||Th||Reasoning about programs|
|Apr 27||Tu||Guest lecture|
|Apr 29||Th||Final project presentations|
|May 4||Tu||Final project presentations|
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 her.
Students are allowed to work together on all aspects of this class. 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.The individual programming assignment policy generalizes from the above. Students are allowed to discuss the architecture and design with others. But each student must write their own code when implementing and testing. Whenever students use publically available resources (e.g., research papers, technical articles, Stack Overflow posts), they must clearly reference the materials in their code.
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 COMPCSI 520 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.
The students should familiarize themselves with the UMass Academic Honesty Policy and Guidelines for Classroom Civility and Respect. These policies and guidelines apply to this class.
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.
The following text books provide a more comprehensive discussion of the topics addressed in this class. Note that these text books are not a requirement for this class.
Students should have taken an intermediate course in software engineering and have built, in a team, a software system of roughly 10,000 lines of code or more. Students are expected to be familiar with an object oriented programming language, such as Java or C++. The ability to use linux and download and use off-the-shelf tools are expected.
Various materials used in this course have greatly benefited from materials developed by Yuriy Brun, Rene Just, Michael Ernst, David Notkin, Alex Orso, and Lee Osterweil. Thank you.