CS 312 Software Development

CS 312 - Course Information

ProfessorChristopher Andrews
Office215 75 Shannon Street
Office hoursM 4:00p-5:00p, T 10:00a-11:30a, R 1:00p-2:30p, F 10:00a-11:00a, or by appointment
Class meetingsRm 203 75SHS -- Section A: MW 8:40a-9:55a & F 8:00a-8:50a, Section B: MW 12:15p-1:30p & F 12:30p-1:20p

Course Objectives

At the completion of the course you should be able to:

  1. Describe and employ modern methodologies for managing SW development, specifically Agile and Scrum
  2. Use tools and services that support those processes, such as version control, GitHub, continuous integration, etc.
  3. Describe and employ SW development principles, patterns and best-practices, such as design patterns, SOLID, test-driven development (TDD), etc.
  4. Describe, evaluate and employ technologies for full stack web development and single page web applications (SPAs)
  5. Complete a large software development project as part of a team

Class deliverables

There will be four different kinds of deliverables in this class:

Practical exercises: Throughout the semester, there will be a collection of in-class exercises where you will work through examples yourselves. The purpose of these is to give you practice working through concrete examples of the things you see in lecture.

Assignments: In the first half the semester there will also be a collection of homework assignments. These will be longer, more involved, and will require more thought ans synthesis on your part. These are designed to both deepen your understanding and allow you to demonstrate your understanding of the material.

Weekly assessments: Every week, we will do a short assessment exercise. These will primarily consist of short answer questions about the material covered up to that point in the class. Each will be marked as belonging to one of the three major topic areas of the class: "skills" (technical implementation, e.g., writing a short function or debugging an implementation), "concepts" (more theoretical questions, e.g., demonstrating knowledge of different patterns, describe pros and cons of different kinds of databases), and "process" (questions about the software development process, e.g., writing user stories, describing the pros and cons of different kinds of testing).

Project: The focus of this class is the final project. In the second half the semester you will undertake a large software development project as part of team of approximately 6 students (depending on class size). You will need to be in frequent contact with your group and actively contributing as a software developer each week.


In this class, we are going to follow a practice called Ungrading. You may have encountered the practice in other classes, though the implementation tends to vary professor to professor and class to class.

In this class it means that I will not grade any of the work that you turn in. I will provide feedback and indicate if I think the work needs to be revised. The practicals and assignments will be run through an autograder to see if they meet the stated requirements. Any work that fails a test should be revised until it passes. You will be able to revise any work any number of times. That said, to the best of your ability you should submit something by the deadline. You do not want to be still working through the homework assignments and practicals when we get into the project.

At the heart of ungrading is a desire to refocus your mental energies from questions like "what grade am I going to get?" to questions more like "do I really understand this concept yet?" and "did I really put my best effort into this work?". As such, we are going to adopt a more reflective practice. When you turn in assignments, you will be asked to provide a self-evaluation of how the assignment went for you and where you think the work and your understanding could be improved.

Unfortunately, at the end of the semester, I still need to record a grade in Banner (unless you all opt for CR/NCR). So, I will ask each of you to write an assessment of your progress over the semester. You will reflect on the work you completed and your contributions to the project. We will then have a short meeting and you will tell me what grade I should record for you. We will discuss your decision and I will retain ultimate veto power if I feel that you have significantly under- or over- valued your contributions, but in most cases your decision will stand.

Getting help

We are going to be using Slack for our class discussions outside of class. Rather than emailing questions to me, please post the questions on Slack. This will allow other students to answer questions and to benefit from the answers you receive. This system will only work if you use it, so please do so.

Honor code and collaboration

Short version Help each other, but do not share solutions.

Long version In computer science, we build on the work of developers before us. Most of us learned to code by copying code and finding ways to tweak it to do what we want. Almost no computer programs are built without building on the work of others, either in the form of algorithms, libraries, or even just short snippets of code. In the computer science department, we recognize the value of forming study groups, helping each other debug code, and working together.

On the other hand, there are questions of intellectual property and academic integrity. These are considerably murkier waters than you may face, for example, writing a history paper, or doing a problem set in math. With code, you can "accomplish" spectacular things by copying the right chunks of code without ever knowing how it works.

For the most part, navigating these waters is on your head. I encourage you to help classmates to debug misbehaving code. I encourage you to post questions (and answers!) on Slack. But you need to do so in a way that respects other people's work and in a way that contributes to your intellectual development rather than hindering it (or trying to mask your lack of it). With no grades, there is no benefit to turning in correct work that you don't understand, so please do yourself a favor and don't just go looking for code you can turn in to satisfy and assignment.

Policies: Do not work collaboratively unless indicated by the assignment. You can help one another, and work together, but you cannot work jointly on the same assignment. I do not want to see identical assignments that differ only in the name at the top. If someone does show you code (as an explanation or asking for debugging help), do not copy it. Retain ideas, and go away and write your own version later. Attribute any ideas, etc, that you pick up (this goes for classmates, books, online resources, etc). Be explicit. Tell me where you got the idea, approach, technique, etc. Explain what your contribution was. Make sure that your contribution demonstrates that you understand what was not your work alone. Finally, if you have any doubts, ask me first.

Fostering an inclusive environment

As part of the Middlebury community, I support an inclusive learning environment where diversity and individual differences are understood, respected, appreciated, and recognized as a source of strength.

I expect that students in my class will respect differences and demonstrate diligence in understanding how other people's perspectives, behaviors, and world views may be different from their own. Should you experience or witness any behavior that opposes this idea, we hope you will let us know so that it can be addressed.

If you are comfortable reporting such incidents, you can use our anonymous CS departmental climate feedback form (which goes to the CS department) or fill out a Bias Incident Report (which goes to the Middlebury Community Bias Response Team).

You belong in this class and in the computer science department. Thank you for being here and for contributing to this course.

Accommodations for disabilities

Students who have Letters of Accommodation in this class are encouraged to contact me as early in the semester as possible to ensure that such accommodations are implemented in a timely fashion. For those without Letters of Accommodation, assistance is available to eligible students through the Disability Resource Center (DRC). Please contact ADA Coordinators Jodi Litchfield and Peter Ploegman of the DRC at ada@middlebury.edu for more information. All discussions will remain confidential.

Loaner Laptops

If you ever find yourself temporarily in need of a laptop, the Computer Science department has 10 rotating Dell laptops available to our students. These come pre-installed with software for most of the courses in the major. They are available to be loaned out short-term or long-term based on your need (as determined by you). Feel free to ask me ahead of time if you think you need one for just a class period, or you can send an e-mail to rlichenstein@middlebury.edu directly.

The college also provides laptops to those who need them where “need” is based on Student Financial Services calculations. If you anticipate needing a laptop for the whole term, we encourage you to inquire with Student Financial Services and the library first due to our smaller pool of equipment. However, our department commits to meeting the needs of every student, so do not be afraid to reach out if you believe you need one of our laptops for any length of time.