CSC 224 Java for Programmers
This course covers the basics of programming in Java. Specific features of the Java language covered include variables, input and output, data types, various flow of control constructs, arrays, strings, methods and classes, exception handling, file I/O, and database access.
This is a program-intensive class. Programs will be assigned almost every week. The due date (usually one week later) will be given with the assignment. Programs are due at the beginning of class on the due date. Programs received after the day and time due will be considered late and will be assessed a late penalty (10% for every week that it is late). No program will be accepted if it is more than two weeks late. There are no exceptions to these rules.
Unless instructed otherwise, for each programming assignment hand in hardcopy of the source code, input, and output. Never turn in a
floppy disk and do not submit assignments by email.
If your program does not produce output (because, for example, it
does not compile), do not turn it in. If you do, it will receive a
grade of zero and you will not be allowed to resubmit it. A program
is worth more late and correct than on time with errors.
There is a substantial amount of material to be covered within a fairly short period of time. Be careful not to fall behind. Completion of the programming assignments will require (possibly extensive) work outside of the classroom. While no prior computer experience is required, you should have some level of comfort with PCs.
You may develop your programs anywhere you like. Sun JDK 1.3 (Java Development Kit) is recommended, and will be discussed in class. JDK 1.3 is provided on the CD-ROM included with your textbook.
Each program is worth a maximum of 100 points. Programs must be properly indented; that is, each logical level must be indented an additional amount. The text shows how to properly indent programs. Pick a style and be consistent. Indentation should be to a consistent level. Popular indentations are: 3, 5, and 8 spaces.
Reviewing and debugging code will be done during office hours only, not via email. Beyond my normal office hours, I can meet with students most Saturday early afternoons by appointment.
Required: , J. Lewis and W. Loftus, Java Software Solutions: Foundations of Program Design, 2nd ed., Addison-Wesley, Reading Mass., 2001. ISBN 0-201-75052-X
Grades will be determined from percentage of total points earned on a series of programming assignments as well as the midterm and final exams. The grade breakdown will be as follows:
Programming Assignments : 30%
Midterm : 35%
Final : 35%
Cutoffs for grades will be no higher than the following:
Pluses and minuses will be given at the high/low ends of each grade range (no A+'s or D-'s).
Course Policy on Incompletes
In addition to the University Policies described below on Incomplete grades, this course has the following additional comments:
Under no circumstances will I consider an incomplete request within one week of the final exam. The request must be approved by me and by the Dean of the School of Computer Science, Telecommunications and Information Systems or the dean's representative. In particular, an incomplete is not given for any of the following reasons:
If I don't get an incomplete, I'll fail the course.
The company won't pay for the course if I get ___.
My grade point average will suffer if I get ___.
It's past the drop date and I'll have to pay for the course if I withdraw now.
In the unlikely case that an incomplete is given, it must be made
up with me. It is not possible to "sit in" on another faculty
member's course and have that person give me the grade to turn in.
(Any student attending any DePaul course must be registered for the
course he/she is attending.) As a result of university and school
rules concerning incompletes, incompletes in the School of Computer
Science, Telecommunications and Information Systems are rarely
See the academic calendar for the last date to withdraw. Under no circumstances will I write a letter supporting a withdrawal after the official withdrawal date.
The programming environment. A Hello World example. Overview of course. Introduction to classes. Tyes, variables, expressions. Simple I/O and using predefined classes. Installing the Java Software Development Kit.
Branching (if statement). Looping (for and while statements).
Writing simple classes and methods. Parameter passing and return values.
More about classes.
Arrays, vectors, and collection classes. Arrays of objects. Stacks and queues.
Inheritance and polymorphism.
Exceptions and I/O streams. Database connectivity.
Graphical components, events, and listeners.
Practice problems. Review for final exam.
Evaluations are a way for students to provide valuable feedback regarding their instructor and the course. Detailed feedback will enable the instructor to continuously tailor teaching methods and course content to meet the learning goals of the course and the academic needs of the students. They are a requirement of the course and are key to continue to provide you with the highest quality of teaching. The evaluations are anonymous; the instructor and administration do not track who entered what responses. A program is used to check if the student completed the evaluations, but the evaluation is completely separate from the student’s identity. Since 100% participation is our goal, students are sent periodic reminders over three weeks. Students do not receive reminders once they complete the evaluation. Students complete the evaluation online in CampusConnect.
Email is the primary means of communication between faculty and students enrolled in this course outside of class time. Students should be sure their email listed under "demographic information" at CampusConnect is correct.
This course will be subject to the academic integrity policy passed by faculty. More information can be found at http://academicintegrity.depaul.edu/
The university and school policy on plagiarism can be summarized as follows: Students in this course should be aware of the strong sanctions that can be imposed against someone guilty of plagiarism. If proven, a charge of plagiarism could result in an automatic F in the course and possible expulsion. The strongest of sanctions will be imposed on anyone who submits as his/her own work any assignment which has been prepared by someone else. If you have any questions or doubts about what plagiarism entails or how to properly acknowledge source materials be sure to consult the instructor.
An incomplete grade is given only for an exceptional reason such as a death in the family, a serious illness, etc. Any such reason must be documented. Any incomplete request must be made at least two weeks before the final, and approved by the Dean of the College of Computing and Digital Media. Any consequences resulting from a poor grade for the course will not be considered as valid reasons for such a request.
Students who feel they may need an accommodation based on the impact of a disability should contact the instructor privately to discuss their specific needs. All discussions will remain confidential.
To ensure that you receive the most appropriate accommodation based on your needs, contact the instructor as early as possible in the quarter (preferably within the first week of class), and make sure that you have contacted the Center for Students with Disabilities (CSD) at:
Student Center, LPC, Suite #370
Phone number: (773)325.1677