CSCI 221 - 01, Spring 2019 — Software Development I

MWF 2:30-3:30p LBC 322; pre-reqs: CSCI 142

Implementation of the Object Oriented paradigm using C++ and the Unified Modeling Language (UML). An introduction to the components of the C++ compiler, and the software development life cycle.

About me


There is no textbook for this class.


  • Attendance on work days (Fridays, plus all class days Apr 1 - May 6): 10%
  • Homeworks (6 of them): 30%
  • Proficiency exam 1: 2.5%
  • Proficiency exam 2: 2.5%
  • Test 1: 15%
  • Test 2: 20%
  • Group project: 20%

Late work is penalized 20% for each day that it is late. Submissions more than 3 days late receive no credit. Tests cannot be made up unless a doctor’s note is provided.


Homework will be submitted via Bitbucket. Create an account on Bitbucket and, for every assignment, create a new repository and add me (username ‘joshuaeckroth’) as a reader. Always name the repository csci221-HW01 (homework # changes).

See the individual assignments for the grading rubric. Homeworks are always out of 5 points.

Proficiency exams

You are required to learn a wide variety of techniques for Linux, git, vim, emacs, etc. I will not lecture about these techniques. See the list of techniques. You cannot use notes while being examined. The grading rubric is as follows, out of 3 points:

  • answer at least 75% of the questions: 3 pts
  • answer at least 50% of the questions: 2 pts
  • answer at least 25% of the questions: 1 pt
  • answer fewer than 25% of the questions: 0 pts


The grading rubric for attendance is as follows, out of 3 points:

  • attended at least 75% of work days: 3 pts
  • attended at least 50% of work days: 2 pts
  • attended at least 25% of work days: 1 pt
  • attended fewer than 25% of work days: 0 pts

Group project

In the last five weeks of the course, all students will be working on a single group project. I will define the project requirements and assign each student to a subgroup with a specific set of tasks. We will collaborate as a class to decide the deliverables after I have explained the project goals.

Grades for the group project will be determined primarily on whether or not the class meets its deliverables. 25% of your group project grade will be determined by an average of your team members’ and your own ratings of your performance. These ratings will be private and anonymous.

The group project grading rubric is as follows, totalling 20 points (for 20% of final grade):

  • Deliverable 1: 4 pts
  • Deliverable 2: 4 pts
  • Deliverable 3: 4 pts
  • Deliverable 4: 4 pts
  • Average peer rating: 4pts


Proficiency exam dates

  • Proficiency exam 1: Wed Feb 13
  • Proficiency exam 2: Wed Feb 27

Test dates

Both tests are take-home. Tests will be made available a few days before these due dates:

  • Test 1: available Wed Mar 13, due Mon Mar 18, 11:59pm
  • Test 2: available Wed Apr 10, due Mon Apr 15, 11:59pm

Group project deliverables

Requirements for the group project will be established later. The project will have five deliverables. Each deliverable is a set of features (to be decided when the project begins), plus a presentation (~10 minutes).

  • Deliverable 1: Wed Apr 19
  • Deliverable 2: Wed Apr 26
  • Deliverable 3: Wed May 3
  • Deliverable 4: Mon May 6, 5pm


  • Week 1: Basics of C++, Linux, git
  • Week 2: Makefiles
  • Week 3: Debugging
  • Week 4: Pointers, memory management, references
  • Week 5: Structs, classes, operator overloading
  • Week 6: Linked lists
  • Week 7: Trees
  • Week 8: no class (break)
  • Week 9: Polymorphism, inheritance, destructors
  • Week 10: Templates, Standard Template Library
  • Week 11: Boost library
  • Week 12: Group project start
  • Week 13: Group project deliverable (presentation)
  • Week 14: Group project deliverable (presentation)
  • Week 15: Group project deliverable (presentation)
  • Week 16: Group project deliverable (presentation)
  • Final exam time (May 6, 5-7pm): Group project deliverable and retrospective

Honor code

I am strongly in agreement with the Stetson University Honor Code. Any form of cheating is not acceptable, will not be tolerated, and could lead to dismissal from the University. In this class, cheating is defined as copying code from the internet (except this website), copying code from other students, or working together on assignments or tests. Only in the context of the group project may students work together; even then, code cannot be copied from the internet. Please consult with me if you find a solution to a problem on the internet and wish to make use of it; we can arrange an appropriate solution.

Academic success center

If a student anticipates barriers related to the format or requirements of a course, she or he should meet with the course instructor to discuss ways to ensure full participation. If disability-related accommodations are necessary, please register with the Academic Success Center (822-7127; www.stetson.edu/asc) and notify the course instructor of your eligibility for reasonable accommodations. The student, course instructor, and the Academic Success Center will plan how best to coordinate accommodations. The Academic Success Center is located at 209 E Bert Fish Drive, and can be contacted using the email address asc@stetson.edu.

CSCI 221 material by Joshua Eckroth is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. Source code for this website available at GitHub.