COURSE DESCRIPTION
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 1000-2000 lines of source code. Use of programming environments and tools to aid in the software development process.
COURSE TOPICS
- 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
PREREQUISITES
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.
COURSE GOALS
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.
INSTRUCTOR
Richard McKenna
Lecturer
Computer Science 1436
Office Hours: MW 12pm-2pm
Email: richard@cs.stonybrook.edu
Teaching Assistants (Grading Appointments & Code Reviews)
Omar Khazamov
okhazamov@cs.stonybrook.edu
Yaroslav Markov
ymarkov@cs.stonybrook.edu
HOMEWORK GURUS (Office Hours in CS 2110)
Chris Chen
Office Hours in CS 2110:
-Tuesdays & Thursdays 3pm-5pm
chenstopher@gmail.com
Matt Gruen
Office Hours in CS 2110:
-Wednesdays & Fridays 10am-12pm
mgruen@ic.sunysb.edu
Eric Kaggen
Office Hours in CS 2110:
-Tuesdays & Thursdays 1pm-3pm
ekaggen@gmail.com
Anthony Lomonaco
Office Hours in CS 2110:
-Mondays & Wednesdays 3pm-5pm
PMRAIDER00@YAHOO.COM
Jill Munson
Office Hours in CS 2110:
-Tuesdays 11am-12:30pm & 2pm-3:30pm, Thursdays 2pm-3:30pm
Jillian.Munson@stonybrook.edu
Jisu Son
Office Hours in CS 2110:
-Thursdays 10:30am-12:30pm & Fridays 9am-11am
jisubreeze@gmail.com
Office Hours Grid
| MONDAY | TUESDAY | WEDNESDAY | THURSDAY | FRIDAY |
|---|---|---|---|---|
| Richard McKenna (12pm-2pm) Anthony Lomonaco (3pm-5pm) |
Jill Munson (11am-12:30pm) Eric Kaggen (1pm-3pm) Jill Muson (2pm-3:30pm) Chris Chen (3pm-5pm) |
Matt Gruen (10am-12pm) Richard McKenna (12pm-2pm) Anthony Lomonaco (3pm-5pm) |
Jisu Son (10:30am-12:30pm) Eric Kaggen (1pm-3pm) Jill Munson (2pm-3:30pm) Chris Chen (3pm-5pm) |
Jisu Son (9am-11am) Matt Gruen (10am-12pm) |
LECTURE
Mondays & Wednesdays
2:20 pm - 3:40 pm
Javits 110
TEXTBOOKS
Object Oriented Design & Patterns, 2nd Edition
by Cay Horstmann
Published by Wiley, 2005,
ISBN 978-0471744870
AND
Core Java Volume 1 - Fundamentals, 8th Edition
by Horstmann
Prentice Hall, 2007.
ISBN 978-0132354769
COURSE PLATFORMS
This course will use the Java programming language. The programming environment for this semester will be the Open Source eclipse IDE, which includes a syntax-directed editor, run-time environment, debugger, unit tester, and additional software development tools. Go to the eclipse download page to get your own free copy. All software will also be provided for you to use in the Windows Lab.
Although you might have access to other Java programming environments installed on your PC or elsewhere, you are strongly encouraged to use the officially sanctioned programming environment for this course: because the assignments you submit must run on one of them, because the examinations will test you on your knowledge of the tools, and because these are the only environments for which the course staff will provide support.
Please note that regardless of how you do your programming for this course all code you submit for this course must compile and run under JDK 6.0.
COURSE COMPONENTS
- Final Exam - This will be a written, cumulative final exam on all material covered during the semester.
- Homework Assignments - You must turn in each assignment by noon on the day it is due. 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.
- Written Midterm Exam - This exam will be given in class during a scheduled lecture. The midterm and final examinations will attempt to assess whether students have understood the programming concepts presented in class.
GRADING BREAKDOWN
| 6 Homework Assignments - Programming Component | 40 % | (5 % each, HW 6 worth triple) |
| Homework Assignments - Tools & Coding Style Component | 10 % | (2 % each, no component for HW 6) |
| Midterm Exam | 25 % | |
| Final Exam | 25 % | |
| 100 % |
Note CEAS Policy: The Pass/No Credit (P/NC) option is not available for this course.
ACADEMIC DISHONESTY
Read This! 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. Those involved will be prosecuted to the fullest extent permitted by the University and College laws. 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.
SPECIAL ASSISTANCE
If you have a physical, psychological, medical or learning disability that may impact on your ability to carry out assigned course work, I would urge that you contact the staff in the Disabled Student Services office (DSS) in the ECC building (where the Computer Store used to be), 632-6748v/tdD. DSS will review your concerns and determine with you what accommodations are necessary and appropriate. All information and documentation of disability are confidential.
If you need general computer help, you can use the Computer Science Help Desk. Services offered include setting up an account on a department server, using Windows NT, using a browser, and connecting to the campus network. The Help Desk office is located in the SBCS Office - Room 2110.
Web page created and maintained
by Richard McKenna