Programming Methologies, Spring 2021
Chiu and Marius Minea
TAs: Shreyas Kulkarni, Chetan Manjesh, Hieu Huy Phan, Edward Schneeweiss, Shiv Shiv Shankar
UCAs: Nicolas Asnes, Eli Bildman, Arya Chaughule, Seth Franklin, George Jiang, RiuLong Jiang, Elisavet Phillipakis, Advait Sharma, Shruti Shelke, Thomas Williams
This course will not make use of a textbook. Materials will be provided electronically.
As a successful student, by the end of this course, you will be able to::
- Write programs that use abstractions such as higher-order functions (for example: map, filter, and reduce), and object-oriented programming.
- Employ an accurate mental model of programming languages that support mutable state, assignable variables, objects, higher-order functions, and garbage collection, as well as understand fundamentals of their implementation.
- Design test cases to detect errors in code by applying systematic criteria, and write code predicates to validate the inputs and outputs of a potential solution to a programming problem.
- Select and use appropriate design patterns such as builders, fluent APIs, publish/subscribe, state, memento, and promises for handling errors.
- Reason about the correctness of code by establishing pre- and postconditions, and loop invariants.
To succeed in COMPSCI 220, students should already understand:
- Variables (declaration and scope)
- First-order functions
- Recursive functions with integer arguments
- A few algorithms and data structures including lists, trees, and recursion
Students who complete COMPSCI 220 understand the following topics:
- Programming with abstraction (higher-order functions, and object-oriented
- Programming with recursively-defined data structures (e.g., trees and
- An accurate mental model of programming languages that support mutable
state, assignable variables, objects, higher-order functions, and garbage
- Given a problem statement and a solution in code, students can write 1)
test cases that catch bugs in the solution; and 2) test cases that pass
despite the presence of bugs.
- Property-based testing: given a problem statement in prose, students can
write predicates in code to validate the inputs and outputs of a potential
- Design patterns
- Higher-order list processing functions. For example, map, filter, and reduce.
- The Publish-subscribe pattern
- Builders and fluent APIs
- The Observer pattern
All assignment in this course are individual assignments. You should not work with any other students. As a guideline, to distinguish discussion from plagiarism, feel free to discuss problems verbally or via temporary written means (e.g., whiteboard) but do not share written matter. If you have questions about this matter, please ask.
As members of the College of Information and Computer Sciences at UMass Amherst we expect everyone to behave responsibly and honorably. In particular, we expect each of you not to give, receive, or use aid in examinations, nor to give, receive, or use unpermitted aid in any academic work. Doing your part in observing this code, and ensuring that others do likewise is essential for having a community of respect, integrity, fairness, and trust.
If you cheat in a course, you are taking away from your own opportunity to learn and develop as a professional. You also hurt your colleagues, and this will hurt people you will work with in the future, who expect an honest and responsible professional.
As faculty, we pledge to use academic policies designed for fairness, avoiding situations that are conducive to violating academic honesty, as well as unreasonable or unusual procedures that assume dishonesty.
We will follow the university's academic honesty policy. This means we will report instances of dishonesty, which may lead to formal sanction and/or failing the course.
Several factors determine your grade in this course. They are weighted as follows:
|Homework: programming component
|Participation in Discussion Sessions
|Lesson questions (associated to videos)
Topics (subject to change)
||First class functions, more higher order functions
||Higher order functions with data structures
||Property based testing, garbage collection
||Design patterns: Builders; Streams
||Error handling; Publish-subscribe design pattern
||Programming programming languages
||Programming programming languages part 2, Design patterns: States
||Objects vs. functions; Design patterns: Memento
||Proving program correctness; Design patterns: Visitor
Equity and Inclusion Statement
We are committed to fostering a culture of diversity and inclusion, where everyone is treated with dignity and respect. This course is for everyone. This course is for you, regardless of your 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, or work experience.
Because of that, one of the things we all need to realize is that we will be bringing different skills to the course, and we will all be learning from and with each other. Some of us are great artists, some of us aren't. Some of us have had previous experience with community organizing, and for some of us that may be something new. Some of us have very definite plans for our professional careers, some of us are still exploring. Each of these skills will help us succeed, both individually and as a group.
Please be kind and courteous. There's no need to be mean or rude. Respect that people have differences of opinion, and work and approach problems differently. There is seldom a single right answer to complicated questions. Please keep unstructured critique to a minimum. Criticism should be constructive.
Disruptive behavior is not welcome, and insulting, demeaning, or harassing anyone is unacceptable.
We follow the university's guidelines for classroom civility.
In particular, we don’t tolerate behavior that excludes people in socially marginalized groups. If you feel you have been or are being harassed or made uncomfortable by someone in this class, please contact a member of the course staff immediately, or if you feel uncomfortable doing so, contact the Dean of Students office.
This course is for all of us. We will all learn from each other. This is our welcome.
The University of Massachusetts Amherst is committed to making reasonable,
effective and appropriate accommodations to meet the needs of students with
disabilities and help create a barrier-free campus. If you have a documented
disability on file with Disability
Services, you may be eligible for reasonable
accommodations in this course. If your disability requires an accommodation,
please notify your instructors as early as possible in the course so that we
may make arrangements in a timely manner.
If you require any special services or accommodations during this course, you
must register with Disability Services within the first two weeks of this
course. This will give us time to plan accordingly to ensure that you get the
help you need before it is too late. If you contact us after the two weeks we
may not be able to provide you the help you need.