General information

The Class
Projects

Facade
FreeSpace

Instructor

Christopher Haynes (Chris), phone 855-3376, office LH230F, email chaynes@indiana.edu

Associate Instructors

        Leena Unnikrishnan (Leena), email lunnikri@indiana.edu
 

Credit Hours

4

Lecture

Section 8240 11:15A-12:30P in LH115

Laboratory

Section 8241 10:10A-11:00A in LH115

Office Hours

• Chris: Monday and Wednesday from 2:00P to 3:30P in LH230F
• Leena: Monday from 10:00A-11:00A in LH301E and Friday from 11:00A-12:00P in LH016

We are here to help you learn: talk to us after class, and come to office hours with your questions or comments about any aspect of the class. No appointment is necessary to see us during office hours.  If our office hours are not suitable for you, please contact one of us to make an appointment.

Class Web Site

www.cs.indiana.edu/classes/h212 This page is the root of this web. Check here often for updates.

Class Newsgroup

ac.csci.h212.8240 Check here frequently for class announcements and useful information. Email this address to post messages to this newsgroup.

C212 Introduction to Software Systems (4 cr.) NMMC P: C211. Design of computer software systems and introduction to programming in the environment of a contemporary operating system. Topics include the C++ [sic] systems programming language and its data structure facilities; building and maintaining large projects; and understanding the operating system interface, including shell tools and system calls. Introduction to object-oriented programming. Credit not given for both C212 and H212, or A592; credit not given for both C212 and A306, A502 (discontinued), or A512. Lecture and laboratory.
 

Further Course Description
 

The Java programming language will be used throughout, not C++ as stated in the catalog. There will also be a heavy emphasis on object-oriented programming and design principles. A graphic programming environment, suitable for programming games and other moving-object simulations, will be developed in detail as an extended case study. Clarity of program design and presentation will be emphasized throughout.

Topics include operators, control structures, actors, encapsulation, scope, inheritance, subtyping, method invocation, object creation, design patterns, exception handling, graphic user interfaces, multithreading and synchronization, common data structures and associated algorithms, remote procedure calls, distributed computation, and client-server protocols.

---

Relation to other courses

This course is the honors version of C212, the second course for prospective computer science majors. You do not need to be an "honors" student in any other way to take this course, though you should expect to be challenged somewhat more than you would be in C212. The "with a grade of A- or better" clause of the catalog description is not enforced strictly, though there remains the expectation that honors courses are for students of above average achievement.  If you have not had C211 or H211, see the instructor: this prerequisite is fairly firm. Please do not hesitate to see the instructor if you are in doubt about whether you belong in this course for any reason.

---

Materials

• Several double-sided, high density (DS HD) 3.5" disks. Bring them to all lecture and lab sessions.
• A network ID and password. If you do not have a Network ID, you can create one during the first lab session if you know your Student ID Number and your Registration PIN. You will need an NT Domain account immediately and a Ships or Nations cluster account later in the course.
• The text Java Software Solutions, by John Lewis and William Loftus, Addison Wesley Hongman, 1998.  We will be covering most of this book. References to chapters, sections, pages, exercises, and so on, refer to this book unless otherwise indicated. Since this book is for beginning programmers, some of it will be covered quickly.
• Recommended: Java in a Nutshell, Second Edition (with online quick reference) by David Flanagan, O'Reilly, 1997. This is the most popular Java reference book on the market. You will probably find it quite valuable now and in the future to have at least one Java reference, but you may prefer a different one. Particularly if you have your own implementation of Java complete with extensive on-line documentation, and you love looking things up on-line, you may get by without a reference book at all.  There are a number of differences between Java 1.0 and Java 1.1, and most books claiming to cover Java 1.1 still do a poor job.  This recommended reference covers 1.1 thoroughly.
• Recommended: Learning the UNIX Operating System, by Grace Todino, John Strang, and Jerry Peek, O-Reilly, 1993. Though most of the course work will be done using Symantec Cafe 1.8 on the NT operating system, for a (rather small) part of the course we will also be using Unix. In future computer science courses Unix is used extensively and you will be expected to be familiar with its basics. This little book contains about the minimum that you will need to know for this and future courses. If you are already familiar with Unix or have another Unix book, you do not need this one.
• Recommended: A Little Java, A Few Patterns, by Matthias Felleisen and Daniel P. Friedman, MIT Press, 1998. This little book provides a gentle and enjoyable introduction to object-oriented programming concepts and a few very important O-O design patterns. It will be on reserve in the Swain library and is especially recommended for anyone having difficulty gaining an intuition for object-oriented design. It also emphasizes functional programming techniques in Java that make a nice bridge from the C211 material.

---

Schedule

A detailed schedule of lecture topics, reading assignments, and programming projects will appear here as the course proceeds. For collaborative learning to succeed in class, it is vital that assigned reading and exercises be done, or at least diligently attempted, before class on the indicated date.
 

• 1/12: Read chapter 1. Course overview and system introduction.
• 1/14: Read chapter 2. Practice using Cafe.  Introduction to animation package. Notes on using Cafe.
• 1/16: Assignment 1 due 1/28.
• 1/21: Read chapter 3 (you can skim the material on input for now).
• 1/26: Read chapter 4 through section 5. Assignment 2 due 2/6.
• 1/28: Read the rest of chapter 4.
• 2/2: Read chapter 8 through section 3.
• 2/4: Read the rest of chapter 8.
• 2/9: Quiz (answers) on chapters 1, 2, 3, 4, and 8.
• 2/11: Read chapter 5 through section 2. Quiz makeup assignment. Protection modifier table.
• 2/13: Read the rest of chapter 5 and encapsulation essay by Gregory Rawlins
• 2/16-18: Read chapter 9. Assignment 3 due 2/27.
• 2/20: Read chapter 6 (you can skim section 6.3 for now).
• 2/23: Read chapter 12.
• 3/4: Mid-term exam covering chapters 1-6, 8, 9, and 12: open book and notes, answers.
• 3/9: Read chapter 10. Assignment 4, due 3/13.
• 3/11: Assignment 5, due 3/25.
• 3/25: Read chapter 14. Study Demo.java, with examples of exceptions, visitor pattern, and inner classes.

Also study Total2.java, which demonstrates inner classes for constructing scalable GUI components based on a view-controller-model design.
Assignment 6, due 4/1.
• 3/30: Read chapter 7 and the file animation/Animation.java.
• 4/1: Study the tasks.txt handout.
• 4/3: Read chapter 11. Project pre-proposal (about half a page), due 4/6.
• 4/6: Assignment 7, due 4/15, based on the TimeClient.java, EchoServer.java, and ThreadedEchoServer.java handouts.
• 4/13: Read chapter 15. Remote method invocation with RmiBox.java example. CRC Cards for VMC pattern.
• 4/20: Read chapter 13, study Sort.java.
• 4/27: Read chapter 16, and learn a neat enumerated type hack.
• 5/1: Projects due, project reports. Circles of Death and FACADE
• 5/6: Final exam, LH115, 12:30-2:30 pm. Ring.java

---

Grading

Grades will be based on programming projects, due every one to three weeks (about 50%) and midterm and final examinations.  Examinations will be open notes, reference materials, and computer system (but no outside help). If conditions warrant, the percentage based on examination may be decreased substantially. More details will appear here as they are determined.

Assignments may be done with the help or collaboration of others, providing the nature of all collaboration and help (other than from the instructor or associate instructor) is credited by names at the top of the project listing. Code by others may not be directly incorporated into a project unless from a co-collaborator.  The general nature work sharing in a collaboration should be stated.

There are three opportunitites each week to turn in assignments: at the beginning of each class and discussion section (leave them on Leena's table on the way in). The late penalty is 5 points for each missed opportunity on or after the due date. Assignments will not be accepted more than a week after the due date.

---

Administrivia

• Incompletes: An incomplete (I) final grade will be given only by prior arrangement in exceptional circumstances conforming to departmental policy in which the bulk of course work has been completed in passing fashion.
• Possibly Important Dates
• W March 11 -- Last day to drop the course on your own.
• R April 23 -- Last day to drop the course with a Dean's approval.
• Attendance: Formal attendance will not be taken in lecture or laboratory sections, but little time will be available to assist those who have missed relevant lectures without justification.
• Academic integrity: The standard penalty for any form of academic dishonesty in this course is failure in the course. Providing or receiving help during exams or laboratory tests, or submitting the work of another as your own, both constitute academic dishonesty. There are no "small" offenses. The Computer Science Department statement on academic integrity provides further information.

---

Course Evaluation

Before the end of the course, please complete the electronic course evaluation forms for Chris Haynes and your laboratory section AI.  Stay tuned to this point on the web for further information.

---

Chris Haynes / chaynes@indiana.edu