Meets:

• Lectures: Tues & Thurs 11:00–12:15, Dragas 1117
• Recitations: Fri 1:00–1:50, 2:00–2:50, Dragas 1105

Recitations will be used for special topics and for meetings with teams once the semester project is underway. Until then, they will not meet.

Website: https://secweb.cs.odu.edu/~zeil/cs350/s14/

1. Basic Course Information

1.1 Objectives

This course explores the software development process. It will discuss the major activities common to software development processes, and some of the ways in which those activities are organized and managed.

Heavy emphasis will be placed on the day-to-day skills required during software construction. The course will explore lessons and tools offered by the major successful open-source software efforts.

The course requires each student to participate as a member of a team in a significant team project. Each student will be required to demonstrate proficiency in several software development tools.

1.2 Required Text:

• Zeller, Essential Open Source Toolset, Wiley, 2005, 0–470–84445–0

2. Topics:

Topics will include:

• Software development processes, including the waterfall, unified OO, and extreme programming models.
• Revision management: local, centralized, & distributed approaches
• Configuration Management: project configuration, managing external libraries
• Documentation tools
• Build Management
• Test-driven development
• Unit & Integration Testing: coverage, self-checking, mocking, designing for testability
• Debugging: local & remote, monitors, reverse debugging
• Regression Testing
• Issue tracking
• Software Forges & Repositories

3. Course Pre-requisites

• CS 330 (Object-Oriented Programming and Design), or
• CS 361 (Advanced Data Structures and Algorithms)
  • Students who have not taken CS 330 are encouraged to take CS 382 (Introduction to Java) as a pre-requisite or, at the very least, to work through that courses’s website during the first few weeks of the semester.

4. Communications

4.1 Contact Info

When possible, students should use the course Forum for communications rather than email.

4.2 Office Hours

Office hours are posted online at http://www.cs.odu.edu/~zeil/officehours/

5. Course Policies

5.1 Due Dates and Late Submissions:

Late assignments and make-up exams will not normally be permitted.

Exceptions will be made only in situations of unusual and unforeseeable circumstances beyond the student’s control, and such arrangements must be made prior to the due date in any situations where the conflict is foreseeable.

“I’ve fallen behind and can’t catch up”, “I’m having a busier semester than I expected”, or “I registered for too many classes this semester” are not grounds for an extension.

5.2 Academic Honesty:

Everything turned in for grading in this course must be your own work, or, for team projects, the work of your own team. Opportunities for teamwork will be clearly identified as such.

Students are expected to conform to academic standards in avoiding plagiarism.

The instructor reserves the right to question a student orally or in writing and to use his evaluation of the student’s understanding of the assignment and of the submitted solution as evidence of cheating.

Students who contribute to violations by sharing their code/designs with others may be subject to the same penalties. *Students are expected to use standard Unix protection mechanisms (chmod) to keep their assignments from being read by their classmates. Failure to do so will result in grade penalties, at the very least.

This policy is not intended to prevent students from providing legitimate assistance to one another. Students are encouraged to seek/provide one another aid in learning to use the operating system, in issues pertaining to the programming language, or to general issues relating to the course subject matter. Student discussions should avoid, however, explicit discussion of approaches to solving a particular programming assignment, and under no circumstances should students show one another their code for an ongoing assignment, nor discuss such code in detail.

Violations of this policy will be reported to Student Judicial Affairs for consideration for punitive action.

5.3 Attendance:

Attendance at lectures is not generally required, but students are responsible for all material covered and announcements made in class.

Exceptions to this policy may be announced by the instructor.

5.4 Grading: