1.1 Course Pre-requisites

2 Course Structure

2.1 Sessions

• Lectures: No regularly scheduled meetings

  Lecture materials for this course will be available on-line, primarily in printed/text form.

• Recitations: Tuesdays 3:50pm to 5:50pm or Thursdays 3:50pm-5:50pm (selected weeks)

  Refer to LeoOnline/BannerXE for your recitation time

  Recitations will be conducted by network conferencing.

  Attendance is mandatory in the scheduled weeks.

  Recordings will not be available.

2.1.1 Recitations

Recitations will be used for special topics and for meetings with teams once the semester project is underway.

• They will not meet every week.
• Meetings will be on-line.
  • You will attend from your “development machine”.

3 Activities

Each module in the course outline contains a variety of activities.

• Not all are graded.
• But unless specifically stated otherwise, all are required
• And should be completed by the end of that module

3.1 Readings

• lecture notes
• textbook chapters & web articles

All are online and available via the course Outline.

3.2 Assignments

Individual assignments will include:

1. Unit Testing
2. Version Control (git)
3. Test-Driven Development
4. Build Manager (gradle)
5. Continuous Integration (Github Actions)

3.3 Labs

There are a number of activities marked in the outline as “Labs”.

• These are ungraded activities.
• They are, nonetheless, required.
• Many of the later assignments will make direct use of files, code, and/or skills from an earlier lab.

3.4 Semester Project

A moderately large program on which you will work in teams of 4-6 people.

Five phases:

1. Writing Requirements
2. Planning for construction: writing user stories
3. Early construction: build management, version control, story tracking, project website
4. Later construction: project website, documentation management
5. Later construction: continuous integration, system testing

• In general, your team will be evaluated upon process as much as upon their ability to produce working code.

  The idea is to see if you have established a team process such that, if you had enough time, you would have eventually implemented the entire process.

• The team score will then be modified for individuals based on evidence of teamwork.

3.4.1 Project Teams

• Teams will be assigned randomly.
• Each Team will draft a contract defining their expectations of acceptable participation.
• There will be options for voluntarily leaving a team, and for being fired from a team.

3.4.2 Project and Recitations

Phases 3 and 4 will be evaluated in part via a team review meeting with the instructor.

• Held during recitation period
• The instructor will ask questions about team’s overall progress.
• The instructor may direct questions to specific team members to be sure that everyone shares an understanding of the project and required skills.

  • General rule is that if one member of a team does not know something, that’s a mark against that person. If two people don’t know something, that’s a mark against the entire team.

• At end of some meetings, you may receive a short test/assignment, which each team member must complete individually within a limited time period (a day or less).

3.4.3 Expectations

The team project is a integral part of this course.

• Students are expected to actively participate in and contribute to their teams.

  • This engagement with the team will be part of the grade.
  • It is possible to be fired from a team if your teammates believe that you are slacking.

• Procrastination and deadline-brinkmanship are detrimental to any team dynamic.

  • Students who work early and often will be rewarded.

4 Exams

• Midterm & Final
  • Administered on-line
  • Dates & times on the course calendar
• Final exam is cumulative.

5 Communications

Contact Info

Important: The course name “CS350” should appear in the subject line of all course-related email.

I try to respond to all (properly marked) messages before I leave campus each day (Monday through Friday). On weekends and holidays within 48 on weekends & holidays.