Development of the basic concepts and techniques from Computer Science I and II into practical programming skills that include a systematic approach to program design, coding, testing, and debugging. Application of these skills to the construction of robust programs of thousands of lines of source code. Use of programming environments and tools to aid in the software development process.


  • Programming style and its impact on readability, reliability, maintainability, and portability.
  • Decomposing problems into modular designs with simple, narrow interfaces.
  • Determining the proper objects in an object-oriented design.
  • Selecting appropriate algorithms and data structures.
  • Reusing code, including external libraries designed and built by others.
  • Learning systematic testing and debugging techniques.
  • Maintaining a repository of code during incremental development of a software project.
  • Learning how to use threads to synchronize several tasks.
  • Improving program performance.
  • Making effective use of a programming environment, including:
    • Syntax-directed editor
    • Build tools
    • Debugging tools
    • Testing tools
    • Source code management tools
    • Profiling tools


You must have taken CSE 214 and received a grade of "C" or better in order to take this course. In more detail, you are expected to have the following knowledge and skills at the beginning of the course:

  • Ability to write programs of a few hundred lines of code in the Java programming language.
  • Understanding of fundamental data structures, including lists, binary trees, hash tables, and graphs, and the ability to employ these data structures in the form provided by the standard Java API.
  • Ability to construct simple command-based user interfaces, and to use files for the input and output of data.
  • Mastery of basic mathematical and geometric reasoning using pre-calculus concepts.


At the end of the course you should have the following knowledge and skills:

  • Ability to systematically design, code, debug, and test programs of about two thousand lines of code.
  • Sensitivity to the issues of programming style and modularity and their relationship to the construction and evolution of robust software.
  • Knowledge of basic ideas and techniques of object-oriented programming.
  • Familiarity with the capabilities and use of programming tools such as syntax-directed editors, debuggers, execution profilers, documentation generators, and revison-control systems.


Tuesdays & Thursdays




Richard McKenna
Office Hours:
--Tuesdays10:30am - 12:30pm
--Thursdays10:30am - 12:30pm
Richard McKenna Profile

TEACHING ASSISTANT (Office Hours in CS Commons)





This course will use the Java programming language, version 8. The programming environment for this semester will be the NetBeans IDE. The current version is 8.2. This IDE has a syntax-directed editor, run-time environment, debugger, unit tester, and additional software development tools. Note that the following references will be helpful to students while completing the Java programming assignments:

  • Java 8 API - this reference provides a summary of all the Standard Edition classes, many of which we'll make use of.

  • JavaFX 2.2 API - this reference is for JavaFX classes and interfaces specifically.

  • The Java Tutorial - walks one through programming in Java, including the new features of Java 8.

  • JavaFX Tutorial - a good reference for learning how to make User Interfaces using JavaFX, which is new with Java 8. Note that JavaFX is replacing Swing as the Java framework for making user interfaces.

TEXTBOOKS (both are online via provided links below)

Head First Object Oriented Analysis and DesignHead First Object Oriented Design and Analysis
by Brett McLaughlin, Gary Pollice, David West
Published by O'Reilly Media, Inc. 2006
Print ISBN-10: 0-596-00867-8
Print ISBN-13: 978-0-596-00867-3


Head First Design PatternsHead First Design Patterns
by Eric T Freeman, Elisabeth Robson, Bert Bates, Kathy Sierra
Published by O'Reilly Media, Inc. 2004
Print ISBN-10: 0-596-00712-4
Print ISBN-13: 978-0-596-00712-6


  • Recitations - Students will attend weekly recitations that will introduce use of essential development tools and will require completion of an exercise for submission.

  • Homework Assignments - The assignments will develop a students ability to design and implement object-oriented systems. Grading will be based on functionality and proper use specific tools. Submitted code that does not compile will receive no credit. Late submissions will NOT be accepted. Programming assignments will be handed in electronically, instructions for which will be provided early in the semester.

  • Exams - Exams will cover all lecture, recitation, and homework materials covered during the semester.


Recitation Exercises 5%
5 Homework Assignments 25 % (5 % each)
Final Project (i.e. HW 6) 20 %
Exams 50 %
100 %

Note CEAS Policy: The Pass/No Credit (P/NC) option is not available for this course.


You may discuss the homework in this course with anyone you like, however each student's submission, including written material and coding, must be his or her own work, and only his or her own work. Any evidence that written homework submissions or source code have been copied, shared, or transmitted in any way between students (this includes using source code downloaded from the Internet or written by others in previous semesters!) will be regarded as evidence of academic dishonesty. Additionally, any evidence of sharing of information or using unauthorized information during an examination will also be regarded as evidence of academic dishonesty.

The College of Engineering and Applied Sciences regards academic dishonesty as a very serious matter, and provides for substantial penalties in such cases, such as receiving an `F' grade, or expulsion from the University. For more information, obtain a copy of the CEAS guidelines on academic dishonesty from the CEAS office.

Be advised that any evidence of academic dishonesty will be treated with utmost seriousness. If you have a situation that may tempt you into doing something academically dishonest, resist the urge and speak with your instructor during office hours for help.

SUNY Korea Attendance Policy

Per the SUNY Korea Academic Bulletin:

  1. All students of SUNY Korea are required to attend every class.
  2. Unexcused absences will seriously affect the student’s final grade in the course.
  3. If a student has over 20% unexcused absences in a course, the student’s final grade in the said course will be an ‘F’. For Example:
    1. If the class is a 150 minute class, and is held once a week, the 4th unexcused absence will lead to an F grade in the course.
    2. If the class is a 75 minute class, and is held twice a week, the 7th unexcused absence will lead to an F grade in the course.
    3. If the class is a 50 minute class, and is held three times a week, the 10th unexcused absence will lead to an F grade in the course.
    4. In the Intensive English Course (IEC), if a student misses more than 40 hours of the class in a semester, the student will receive an F grade in the course.
  4. Students should report the reason for the absence to the instructor in advance, or immediately after the absence.
  5. When a student gets an excused absence, the student must provide documentation for the said reason for the absence to the instructor.
  6. The instructor of the course reserves the right to excuse absences.
  7. The course instructor may excuse the absence if the submitted documentation fulfills the conditions below:
    1. Extreme emergencies (e.g. death in the family)
    2. Severe medical reasons with doctor’s diagnosis (Not a slight illness)
    3. Very important events (e.g. national conference, official school event)
  8. At the end of the semester, the course instructor should submit a copy of the attendance sheet to the Academic Affairs Office.

SUNY Korea Disability Support

If you have a physical, psychological, medical or learning disability that may impact your course work, please contact One-Stop Service Center, Academic Building A201, (82) 32-626-1117. They will determine with you what accommodations, if any, are necessary and appropriate. All information and documentation is confidential.

In addition, this statement on emergency evacuation is often included, but not required: Students who require assistance during emergency evacuation are encouraged to discuss their needs with their professors and One-Stop Service Center.

Stony Brook CS

Web page created and maintained
by Richard McKenna