COMP 180

Software Engineering, Spring 2020

Staff

Name Office E-mail Office Hours
(also available by appointment)
Jeff Foster zoom
(email me if you need the password)
jfoster@cs.tufts.edu T 11am-12pm; W 1:15-2:00pm
David Zabner Zoom (see pinned post on campuswire) david.zabner@tufts.edu Su 5-7pm; Mo 5:30-7:30pm; Th 1-2:30pm

Information

LocationAnderson 112
Cohen Auditorium
zoom
(email me if you need the password)
TimeMW 3:00-4:15
MidtermWed, Mar 11, in class TBA
FinalMay 1, 3:30-5:30pm (tentative)
Textbooks There are no required textbooks

The scale of modern software systems is truly amazing. We regularly use software that is hundreds-of-thousands to millions of lines of code, and that software, while certainly not bug-free, mostly does what it is supposed to. Achieving this kind of scale has been the result of steady progress in software engineering over the last several decades.

In this class, we will study the foundations of software engineering, focusing on the core principles and ideas that enable us to build large-scale software systems. Our focus will be on the coding side of software engineering. Equally important, but deferred to a different course, is the people/team side of software engineering. We will explore ideas such as abstraction, modularity, architecture, specification, testing, and debugging, among others.

The course will be conducted in Java, and will include a short introduction to Java at the beginning. During the course, students will complete a number of programming assignments, and the course will also include some reading assignments.

Prerequities: COMP 40, graduate standing, or instructor consent. If you are not sure whether you meet the prerequisites for the course, please contact the instructor.


WeekMondayWednesday
Jan 13(No class)Introduction
Java
Reading #1
Jan 20MLK Day
No class
(Monday)
Java
Project 1
Jan 27JavaJava
LL.java, AL.java, List.java, Main.java
Feb 3Java
Reading #2
Java
Project 2
Feb 10Reading #2 Discussion
Design Patterns
Design Patterns
Feb 17(Wed, Feb 19)
Design Patterns
(Thu, Feb 20)
Design Patterns
Feb 24Reflection
Testing
Project 3
Testing
Mar 2TestingTesting
Mar 9TestingRefactoring
Mar 16Spring break
No class
Spring break
No class
Reading #3
Mar 23Spring break
No class
Chocolate
Symbolic Execution
Mar 30Software Architecture
Project 4
Software Architecture
Concurrency
Apr 6
Apr 13
Apr 20
Apr 27Last class!

  1. (Due Jan 22) James Gosling and Henry McGilton, The Java Language Environment: A White Paper, chapters 1, 2, and 4.
    • Q1: There were several design goals in the development of Java. Pick one goal that you find most compelling and explain why you personally think it's an important goal.
    • Q2: Section 4.3.1 of the paper says that Java has strict compile- and run-time type checking, in contrast to C/C++. Do you think this is a good design choice? If possible, explain your thinking with examples from your personal experience programming in C/C++.
  2. (Due Feb 10) D.L. Parnas, On the Criteria To Be Used in Decomposing Systems into Modules
    • Q1: Briefly describe one important lesson about modularity that the paper describes and that you think is still relevant today.
    • Q2: Computing has advanced significantly since this paper was written. Briefly describe one challenge (not necessarily with modularity) or perspective that, while realistic in 1972, does not apply today.
  3. (Due Mar 25) Cadar et al., KLEE: Unassisted and Automatic Generation of High-Coverage Tests for Complex Systems Programs
    • Q1: Symbolic execution was originally proposed as an alternative to testing. Briefly, what are some similarities and differences between symbolic execution and testing?
    • Q2: Based on reading the paper, what do you expect is the most difficult part of using KLEE in practice?



Syllabus subject to change until the start of the semester

Prerequisites

COMP 40, graduate standing, or instructor consent. If you are not sure whether you meet the prerequisites for the course, please contact the instructor.

List of Topics (Tentative)

Below is an approximate list of topics for class. The exact topics will be determined based on the pace of the class.

Office Hours and Web Forum

Office hours for the instructional staff will be posted on the course web page a few days into the semester.

While we will provide assistance with assignments during office hours, you are responsible for developing and debugging your own programs. Do not rely on the instructional staff to make your project work.

Important announcements will be made in class or on Campuswire. Please make it a habit to check Campuswire daily, and/or sign up to receive email when updates are posted to Campuswire. You may also use the class web forum to ask general questions of interest to the class as a whole, e.g., administrative issues or project clarification questions. Please do not post any information that would violate the University's Academic Integrity Policy.

Grading

You are responsible for all material discussed in class and posted on the class web page, including announcements, deadlines, policies, etc. Your final course grade will be determined according to the following percentages:

Projects/homework50%
Readings9%
Midterm20%
Final20%
Meet your professor1%

Any request for reconsideration of any grading on coursework must be submitted within one week of when it is returned. Exam regrading requests must be made in writing. Any coursework submitted for reconsideration may be regraded in its entirety, which could result in a lower score if warranted.

Final course grades will be curved as necessary, based on each student's total numeric score for all coursework at the end of the semester. Important: Completing the programming assignments is an essential part of the course. Therefore, we may fail any student who does not make a good-faith attempt on all course projects, regardless of the student's performance or scores on the other coursework.

Programming Projects

Projects must be submitted electronically following the instructions given in class. Projects may not be submitted by any other means (e.g., please do not email your projects to us). It is your responsibility to test your program and verify that it works properly before submitting. All projects are due at 11:59pm on the day indicated on the project assignment, according to the submission server's internal clock. Your project score will be for the last version of the project you submit.

You have two late tokens that you can use during the semester. Using one late token allows you to submit one project up to 24 hours late with no penalty. You may also use your two late tokens together to submit one project up to 48 hours late with no penalty. Contact the TA if you need to check the status of your late tokens.

Exam Scheduling

The class includes a midterm and a final exam. Tentative dates for the exams will be posted on the class web site. The exact dates will be confirmed later. We will let you know the exact dates well in advance.

Academic Resources

The Academic Resource Center offers a range of services for students.

Accommodations for Students with Disabilities

Tufts University values the diversity of our students, staff, and faculty, recognizing the important contribution each student makes to our unique community. Tufts is committed to providing equal access and support to all qualified students through the provision of reasonable accommodations so that each student may fully participate in the Tufts experience. If you have a disability that requires reasonable accommodations, please contact the Student Accessibility Services office to make an appointment with an SAS representative to determine appropriate accommodations. Please be aware that accommodations cannot be enacted retroactively, making timeliness a critical aspect for their provision.

Please also contact the instructor to discuss any necessary accommodations.

Excused Absences

You are expected to attend class regularly, complete course assignments on time, and take exams at the scheduled times. If you are unable to fulfill these requirements due to absence for a good reason, the instructor will excuse the absence and provide accommodation. Events that justify an excused absence include:

It is your responsibility to inform the instructor in advance of intended religious observances. Notice must be provided immediately upon an exam date being announced or confirmed for an absence to be excused.

The policies for excused absences do not apply to project assignments. Projects will be assigned with sufficient time to allow students to carry out the work even with other responsibilities. In cases of extremely serious documented illness of lengthy duration or other protracted, severe emergency situations, the instructor may consider extensions depending on the specific cirucmstances.

Absences stemming from job interviews, traffic or transportation problems, personal travel, and similar will not be excused.

Academic Integrity

The university's Academic Integrity Policy will be strictly enforced.

Unless otherwise specified, programming projects are to be written individually. Therefore, cooperation or use of unauthorized materials on projects is a violation of the Academic Integrity Policy. Project solutions may not be posted online. Any evidence of this, or of unacceptable use of computer accounts, use of unauthorized materials or cooperation on exams or quizzes, or other possible academic integrity violations will be reported.

For learning the course concepts, students are welcome to study together or to receive help from anyone else. You may discuss with others the project requirements, the features of the programming languages used, what was discussed in class and in the class web forum, and general syntax errors. Examples of questions that would be allowed are "Does a Java class definition end in a semicolon?" or "What does a 'class not found' error indicate?", because they convey no information about the contents of a project.

When it comes to actually writing a project assignment, other than help from the instructional staff a project must solely and entirely be your own work. Working with another student or individual, or using anyone else's work in any way except as noted in this paragraph, is a violation of the Academic Integrity Policy. You may not discuss design of any part of a project with anyone except the instructor or teaching assistants. Examples of questions you may not ask others might be "How did you implement this part of the project?" or "Please look at my code and help me find my stupid syntax error!". You may not use any disallowed source of information in creating either their project design or code. When writing projects you are free to use ideas or short fragments of code from published textbooks or publicly available information, but the specific source must be cited in a comment in the relevant section of the program.

Violations of the Code of Academic Integrity may include, but are not limited to:

  1. Failing to do all or any of the work on a project by yourself, other than assistance from the instructional staff.
  2. Using any ideas or any part of another person's project, or copying any other individual's work in any way.
  3. Giving any parts or ideas from your project, including test data, to another student.
  4. Allowing any other students access to your program on any computer system.
  5. Transferring any part of a project to or from another student or individual by any means, electronic or otherwise.

If you have any question about a particular situation or source then consult with the instructor in advance. Should you have difficulty with a programming assignment you should see the instructional staff in office hours, and not solicit help from anyone else in violation of these rules.

Right to Change Information

Although every effort has been made to be complete and accurate, unforeseen circumstances arising during the semester could require the adjustment of any material given here. Consequently, given due notice to students, the instructor reserves the right to change any information on this syllabus or in other course materials.