|Instructor:||Dr. Adrienne Bloss||Office Hours:||Mon, Wed, Fri: 2:40-3:40|
|Office:||365-C Trexler||Tu, Th: 10:00 - 11:00|
|Phone:||375-2434||Also by appointment|
Course Objectives: This course is the first in a three course sequence designed to introduce students to the fundamental concepts of computer science including the underlying foundations from discrete mathematics. The course focuses on the design of algorithms to solve problems, the basics of mathematical logic, and the implementation of the algorithms in the programming language Java. Students will learn the basic control structures and data structures provided by the Java language, the concepts of objects, classes and procedures (methods), and will gain experience in the use of objects (Java classes) in programming and problem-solving. Students will gain familiarity with the UNIX operating system as they develop programs on systems running Linux, a version of UNIX for personal computers.
Text: Java Software Solutions: Foundations of Program Design, 3rd Edition, by John Lewis and William Loftus, Addison-Wesley, 2003.
Course Topics (Schedule Tentative)
|Week of||Topics||Lab||Sections in Text|
||Introduction to Linux, Netscape, and Emacs||1.0-1.2|
||Editing, compiling, and modifying elementary Java programs||1.0-1.4; 2.0-2.3|
||Writing simple programs using expressions||2.4-2.8|
||More programming with classes and objects; applets||3.0-3.4,|
Appendix B and
||Using selection statements in programs||3.0-3.4 and supplementary material|
||More programming using selection statements; circuit design||3.5-3.6|
|Oct 14||Fall Break !!!!|
||Introduction to programming with loops||3.7-3.10|
||More programming with loops, including graphics||4.0-4.2|
||Programming with classes and methods||4.3-4.7|
||More programming with classes and methods||5.0-5.4|
||Writing event-driven programs||5.5-5.7|
||Thanksgiving -- no lab|
||More practice programming with events|
Lab: This course has a required three-hour lab every Tuesday afternoon from 2:40 until 5:40. The purpose of the lab is to give the student a structured experience in software design, implementation, and testing, and to increase the student's ability to use and understand the tools available for software development in the Linux environment. For each lab, there will be a pre-lab assignment designed to prepare the student for lab. The assignment must be handed in at the beginning of lab. Unless otherwise specified, the lab itself must be done during the lab session and turned in before leaving. Associated with most labs will be a short post-lab assignment designed to reinforce lab concepts. Typically the post-lab assignment will be due the second class period following the lab. Late lab work (including pre-lab and post-lab hand-ins) will receive no credit.
Programming Projects: Programming projects are designed to give the student the opportunity to put into practice the problem solving and programming skills they have learned. As such they are one of the most important aspects of the course both for student learning and for assessment. There will be 4 - 6 projects during the semester to be handed in for a grade. You are encouraged to start on your projects immediately when assigned and get help from the instructor as needed.
Important: Projects are to be done individually. You may ask class members, lab assistants, and others for help with system questions (e.g., "How do I save a file in emacs?", "How do I run my Java program?") or general information about a topic covered in class (e.g. "What is the symbol for boolean AND?") provided you can do so without divulging or receiving information specific to the solution of the programming project. You may not discuss any aspect of the design or coding of a programming project with anyone except me. This policy will be strictly enforced; see the section on Academic Integrity below.
Late Policy for Projects: Unless otherwise specified, projects are to be turned in by 4 pm on the due date. Ten percent per calendar day (24 hours) will be deducted for late work; work more than 5 days late will receive no credit. If you anticipate being unable to meet a deadline, talk to me before the deadline; in extenuating circumstances we may be able to make special arrangements.
Attendance Policy: Class attendance is a very important aspect of a student's success in this course. The student is expected to attend every class and lab and is accountable for any missed classes and labs.
Grading Policy: The course grade will
be based on 3 tests, lab work (including pre and post lab assignments),
and a comprehensive final examination.
The course grade is
determined using the following
|Test Dates:||Test #1||Monday, September 23|
|Test #2||Monday, October 28|
|Test #3||Monday, November 25|
|Final Exam||Monday, December 9 (8:30 - 11:30 am)|
Make-up Policy: Everyone is expected to take tests and the exam and do labs at the scheduled time. Make-ups will be given only for legitimate, documented absences that the instructor has been notified of ahead of time. Make-up tests, if given, may be oral.
Academic Integrity: All tests, exams, and programming projects are to be the work of the individual student. You are encouraged to get help from the instructor if you need help with any aspect of the course including programs and assignments. Student assistants, tutors, and classmates may help you in the operation of the computer but not with the substance of any work, other than lab work, that is to be turned in for a grade. They may help you understand course concepts but may not show you how to do any particular aspect of a programming project. Students may discuss lab work (including the pre and post lab assignments) and help each other out but in all cases the work you turn in must be your own. Copying someone else's work or turning in someone else's work is NEVER allowed. Using someone else's work or ideas as your own is plagiarism and an academic integrity offense. Examples of academic integrity violations include copying a program or part of a program (even one line) from someone else, writing code for someone else, telling someone else how to solve a problem or having someone tell you how to solve a problem. Discussion among students about programming projects should be limited to general concepts, not specific aspects of how to complete the work.
Computer Use Policies: All students must abide by the Computer Use policies of Roanoke College. Failure to do so will result in involuntary withdrawal from the course.