1 Basic Course Information

1.1 Catalog Description

Laboratory work required. The techniques and idioms of object-oriented programming in C++ and Java. Methods of object-oriented analysis and design with the Unified Modeling Language. Multi-thread programs, synchronization, and graphic user interfaces

1.2 Overall Description

Throughout this course we will discuss various best practices and object-oriented design patterns. As part of this journey… we will endeavor to do the following:

1. develop the skill set to learn new languages on the fly based on existing knowledge

2. leverage existing knowledge to reason about code written in an unfamiliar language

3. analyze design patterns that are common between languages

4. identify emergent properties of object-oriented code

1.3 Prerequisites

The prerequisites for this course are:

1.3.1 General Programming Knowledge

Students should be familiar with certain basic programming techniques that are largely independent of any specific programming language:

• using editors, compilers and other basic software development tools.
• basic software design (i.e., stepwise refinement and top-down design)
• software testing, including the use of scaffolding code (stubs and drivers), selection of test cases for black-box testing, and head to head testing.
• debugging, including the use of debugging output, the use of automatic debuggers to set breakpoints and trace program execution, and the general process of reasoning backwards from failure locations to the faulty code responsible for the failure.

1.3.2 C++ Knowledge

I will assume that you are familiar with the basics of C++. This includes:

• the various C++ statements and control-flow constructs,
• the built-in data types,
• the use of arrays, pointers, pointers to arrays, and linked lists,
• the use and writing of functions, and
• the basic use of structs and/or classes for implementing abstract data types.

1.3.3 Java Knowledge

No prior knowledge of Java is assumed.

1.3.4 Python 3 & Rust Knowledge

1.3.5 Unix/Linux

All students in the course will receive accounts on the CS Dept. network, and knowledge of how to work with the Linux servers is part of the course prerequisites. This course does not require familiarity with shell scripting. All other topics in CS 252 are required.

Some assignments will require the use of software available only on the Linux servers. Others may require (or, at least, be simplified by) use of the X windowing system.

1.3.6 General Computer Literacy

You will be studying techniques in this course for preparing professional-quality software documentation. The key embedded word in “software documentation” is “document”. Students taking this course should be able to use word processors and other common tools to produce good quality documents, including mixing text and graphics in a natural and professional manner.

1.4 When and Where

I am teaching two sections of CS 330, one live and one online. Both sections use the same syllabus and course materials.

1.4.1 Live Section

• CRN 30665 - On Campus

Meets: Monday and Wednesday from 4:30pm to 5:45pm, Dragas 2117.

1.4.2 Web Section

• CRNs 23464, 23465, and 23466

This course is online and has no regularly scheduled lectures.

1.5 Instructor

Important: All email related to this course should have the phrase CS 330 somewhere in the subject line. This flags your message in my mailbox for faster attention.

I try to respond to all (properly marked) messages

• before I leave campus each day (Monday through Friday)
• within 48 on weekends & holidays.

Any delays in replying to email will be noted in a Canvas Announcement.

1.5.1 Office Hours

2 Required Materials

2.1 Textbooks

Most assigned reading will be from books and other sources available on-line.

Required:

2.2 Supplemental Materials

All supplemental resources and materials will be available in Canvas.

2.3 Technology Requirements

2.3.1 Computer Accounts

Students will need an account on the CS Dept. Linux network to participate in this class. This account is unrelated to any University-wide account you may have from ODU’s Information Technology Services (ITS).

2.3.2 Compilers and Interpreters

The “official” environment in which students’ programming assignments will be evaluated is defined by our Dept. Linux servers. It is the student’s responsibility to be sure that their code compiles and executes using the compilers and run-time environment provided there. As of this writing, the compiler versions used are

• C++: g++ 9.3.0
• Java: 11.0.12
• Python: 3.11

3 Course Objectives

This course will explore the techniques of object-oriented programming, analysis, and design. The emphasis will be upon the development of clean interfaces that permit easy modification and reuse of software components. Other techniques, drawn from outside the object-oriented approach, that significantly contribute to this goal will also be discussed.

Students will gain facility in an object-oriented programming language and will learn the constructs that differentiate such languages from others. This course will explore the idioms and styles of object-oriented programming in C++ and Java, with emphasis upon how these contribute to reusable software components.

Students will learn how to use object-oriented techniques in support of programming. In particular, students will be introduced to the process of object-oriented analysis as a means of understanding an unfamiliar problem domain. Students will learn to build and use models, expressed in the Unified Modeling Language (UML) to codify and evaluate that understanding and to evolve system requirements. Students will learn how to use those models to facilitate a smooth transition from analysis to design and from there to implementation.

4 Course Schedule

5.1 Assignment Drop vs Midterm Exam Drop

All final grade computations are based on 4pt grades as listed under Grades in Canvas. The computation for dropping an assignment grade is

((sum of all assignment grades) - (lowest assignment grade)) / (number of assignments - 1)

The result is used as the assignment average (50% of your final grade). The computation for dropping the Midterm Exam is

0.20 * (Final Exam grade) + 0.30 * (Final Exam grade)

5.2 Assignments

Assignments for this course will include programming assignments, which must be done on an individual basis.

5.2.1 Assignment Grading

5.2.2 Auto-Grader & Testing

Test driven development is a topic of particular import–not only in academia, but in industry.

You will be expected to make use of Blackbox Testing. This is a topic of particular import. Blackbox testing is covered in CS 250–a prerequisite for this course. You will also need to make use of white-box testing and unit testing.

All tests are designed by me–the instructor. The Auto-Grader runs tests that I use to evaluate my solution. These tests evaluate mechanics of import–e.g., dynamic binding and function overloading.

Be systematic in all changes to your assignment solution and modifications to your tests. Do not haphazardly make changes to an assignment and resubmit hoping for a better grade. Treat each submission attempt as your final submission. Ask for guidance before each subsequent submission.

5.3 Exams

The Midterm Exam and Final Exam will be administered online via Canvas.

5.4 Incomplete Grades

6.1 Assignment Expectations

It is my expectation that you have completed approximately 70% of each assignment once half the allotted time has passed. For a two week assignment this would be one week. This will allow you sufficient time to address any issues, refine your testing process, and discuss your solution with me during my office hours.

I expect every student to discuss each assignment with me at least once.

6.2 Review Recordings (Recorded Lectures)

7 Course Policies

7.1 Due Dates and Late Submissions

Late papers, assignments, projects, 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.

Extensions to due dates will not be granted simply to allow “porting” from one system to another. “But I had it working on my home PC!” is not an acceptable excuse.

7.2 Academic Honesty

Everything turned in for grading in this course must be your own work. If an assignment is explicitly described as a team assignment, it must be the work of the team members only.

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. Violations will be reported to the Office of Student Conduct & Academic Integrity for consideration for possible punitive action.

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.

Students 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.

Use of Online Resources

You may not post details of course assignments, projects, or tests at online Forums, Bulletin Boards, Homework sites, etc., soliciting help.

You may use information that you have not solicited but have located, subject to the following restrictions:

• Just as when writing a paper, if you use someone else’s ideas, you must cite your sources appropriately. Within code, such citations appear in comments.

  Example:

  ⋮
  double x = 23.0;
  double xsqrt = sqrt(x);
  // Search algorithm based upon code by S Zeil at
  // https://www.cs.odu.edu/~zeil/cs361/latest/Public/functionAnalysis/index.html#orderedsequentialsearch
  int loc = 0;
  while (loc < arraySize && numbers[loc] < xsqrt)
  ⋮
  

• Just as when writing a paper, if you use someone else’s words (code), you must cite your sources appropriately and mark the quoted text. Within code, such citations appear in comments.

  Example:

  ⋮
  double x = 23.0;
  double xsqrt = sqrt(x);
  
  // Begin quoted code from  S Zeil at
  // https://www.cs.odu.edu/~zeil/cs361/latest/Public/functionAnalysis/index.html#orderedsequentialsearch
  int loc = 0;
  while (loc < listLength && list[loc] < searchItem)
  {
      ++loc;
  }
  // End quoted code
  
  ⋮
  

• Failure to appropriately cite any such “found code” will be taken as evidence of plagiarism.

• The overall principle stated in the first sentence of this section remains in effect. “Everything turned in for grading in this course must be your own work.” If the bulk of your assignment, project, test answer, etc., are copied, even with appropriate citation, to the degree that, in the judgment of the instructor, you have not demonstrated your own knowledge of the course material, you will receive a zero for that submission.

7.3 Attendance

The Attendence section of the syllabus only applies to the live section.

Lecture attendance is not required, but you are responsible for all material covered and announcements made in class. If you are going to miss lecture, be sure to get notes, handouts, etc., from another class member.

8 University Policies

8.1 Code of Student Conduct and Academic Integrity

8.2 Honor Pledge

By attending Old Dominion University, you have accepted the responsibility to abide by the Honor Pledge:

I pledge to support the Honor System of Old Dominion University. I will refrain from any form of academic dishonesty or deception, such as cheating or plagiarism. I am aware that as a member of the academic community it is my responsibility to turn in all suspected violations of the Honor Code. I will report to a hearing if summoned.

8.3 University Email Policy

8.3.1 Student Email

8.3.2 Email Account Activation

It is the responsibility of every eligible student to activate MIDAS, the Monarch Identification and Authorization System, in order to obtain email access.

8.3.3 Expectations Regarding Use of Email

8.3.4 Educational Uses of Email

University offices and instructors cannot validate that a communication coming by email is from an ODU student unless it comes from a valid ODU email address. If students send mail from non-ODU email accounts (e.g., Hotmail or Yahoo), faculty and staff are not obligated to respond and may request that official e-mail accounts be used.

8.4 Withdrawal

8.5 Educational Accessibility

Old Dominion University is committed to ensuring equal access to all qualified students with disabilities in accordance with the Americans with Disabilities Act. The Office of Educational Accessibility (OEA) is the campus office that works with students who have disabilities to provide and/or arrange reasonable accommodations.

• If you experience a disability which will impact your ability to access any aspect of my class, please present me with an accommodation letter from OEA so that we can work together to ensure that appropriate accommodations are available to you.

• If you feel that you will experience barriers to your ability to learn and/or testing in my class but do not have an accommodation letter, please consider scheduling an appointment with OEA to determine if academic accommodations are necessary.