Getting Started

Website: : http://www.cs.odu.edu/~zeil/cs330.html Syllabus: : All students are responsible for reading the course syllabus and abiding by the policies described there.

Details related to the use of the course website and to requirements for assignments and projects can be found on the Policies page. All students are expected to read these before the first assignment is issued.

1. Course Structure

1.1 Readings

• Chapters from text
  • Horstmann, Object-Oriented Design and Patterns, 2nd ed. (required)
  • Fowler, UML Distilled, 3rd Ed. (optional)
• Online Lecture Notes
• Other Online Materials
  • Oracle tutorials
  • CS 382

1.2 Assignments

• Programming assignments
  • Individual work
  • Focused on current lesson
  • Usually graded automatically - results available in 60 min or less
• Analysis assignments
  • Recommended to work in teams
  • Explore the process of moving from vague understanding of a problem toward design
• Roughly speaking, programming and analysis assignments will alternate
  • dates may overlap

1.3 Computer Accounts

• Top priority – make sure that you have a valid CS account - do it this week!
• Available machines:
  • CS Dept labs in Dragas and E&CS
  • Virtual PC lab – see CS Dept home page
  • Unix network (Linux machines - linux.cs.odu.edu)
  • some assignments will require use of this
  • avoid the older Solaris machines

1.4 Exams

• Midterm & Final
  • Administered on-line
  • Dates & times TBA
• Final exam is cumulative.

2. Related Courses

2.1 Pre-Requisites

• CS 250 or CS 333: Programming in C++
  • If you need review, the CS 333 site is a good choice
  • If you are not used to working with our PC network, pay special attention to the Labs
• CS 252: Introduction to Unix for Programmers

2.2 Other Related Courses

• CS361: Advanced Data Structures & Algorithms
• CS 382: Introduction to Java
  • Most of the reading material & labs from that course will be required in this one (in lieu of a Java textbook)
• CS 350: Software Engineering

3. Important Policies

3.1 Late Submissions

… are not normally accepted. Exceptions may be made in cases of

• documented emergencies
• arranged prior to the due date when possible.

Extensions to due dates will not be granted due to

• difficulties “porting” from one system to another
• transient system crashes
• system overloaded

3.2 Academic Honesty

ODU is governed by a student honor code.

• Everything you turn in for grading must be your own work.
• Detailed policy statement is in the syllabus.

Academic Honesty (cont

• Aiding a fellow student to copy someone else’s work (including your own) places you equally in violation.
  • Includes leaving work world-readable on the computer system!
• Failure to report observed violations of the honor code is also a violation.

3.3 Grading

• Expect an assignment roughly every 2–3 weeks.
  • Most of these will be programming assignments;
  • Two will be analysis/design assignments.