Winter CS193D 2005/2006
CS193D Course Information
Scott J. Kleper
[e-mail] [e-mail]
Handout 01 January 11, 2006
Instructor: Email: Staff Email: Office phone: Cell phone: Office: Office hours: TA:
650-725-3378 650-281-5537 Gates B28 Mondays, 11:00am 12:00pm Wednesdays, 2:15pm 3:30pm Dan Wilson (office hours TBA)
Lectures:
MW 12:50pm 2:05pm, Gates B01
Prerequisites: The prerequisite for the class is programming and problem solving at the CS106B/X level. Experience with C++ at the CS106 level is assumed. If you havent done any C++ but you have significant Java experience, you should be fine with a little extra reading. You will be expected to produce elegant, welldecomposed, commented code as taught in the CS106's. New in 06: CS193D was last offered in Winter 2004. This years CS193D has been rearchitected to reflect the changes in the Computer Science curriculum and the interests of students. The most important parts of the C++ language are still covered, but the class is also about programming in professional environments. Topics like How to Write Production Quality Software are given equal attention as How to Use Multiple Inheritance. Since this is the first time the class is being taught this way, I ask for your patience as we work out the kinks. And most importantly, I ask for your feedback. Let me know how things are going as the quarter progresses and Ill do my best to tune the class along the way. Readings: The official class text is Professional C++ by Solter and Kleper. Im not here to sell books, so if you already have another C++ book for reference and feel that you can pick everything up from the lectures and handouts, thats fine. However, you should be aware that Ill be using examples from the book in class so it may be handy. There are a ton of C++ books out there if youre looking for additional reading material. Stroustrups The C++ Programming Language is the standard reference. 1
2 Eckels Thinking in C++ and Meyers Effective C++ both contain excellent coverage of real world applications. Web site: The web site for this class is http://cs193d.stanford.edu. I will post all handouts and assignments there. Ill also periodically update it after lectures with notes and clarifications. The site has an RSS feed so you can stay up to date using an RSS newsreader. Its very important that you subscribe to the feed it takes the place of the traditional class email list. If you dont have a newsreader or are unfamiliar with RSS, see the instructions on the class web page. The projects for the class should be portable in that the C++ code required should work with any modern C++ compiler. We will concentrate our efforts on supporting gcc on Unix. You are welcome to use other compilers or computers, but bear in mind that compilers differ from machine to machine and C++ compilers are actually still evolving. If you are using an unsupported platform and run into difficulties, be prepared to switch to the one I'm supporting. No which matter platform you use, you are responsible for ensuring your final program will compile and run on the e l a i n e workstations, since thats where youll submit code. If you do not already have an account on a campus computer from which you can send email, open an account on leland. Handouts available at Sweet Hall and Tresidder computer clusters explain the procedure used to open an email account. You can send questions to [e-mail], and the first available staff member will get back to you. For questions that seem to recur (or are particularly funny), we will post the answers to the feed. There may or may not be a legacy newsgroup named su.class.cs193d. If there is such a group, in the spirit of simulating a professional development environment, you can use it to chat with your classmates about any class topic, including assignments, subject to the Honor Code section below. Your grade will be based on homework assignments, a midterm, and the final. The breakdown is: Assignments Midterm Final Exams: 40% 25% 35%
Software:
Email:
Staff email:
Newsgroup:
Grading:
The midterm date is February 15th, 2006 in class. It will be closed book and closed note. Local SITN students are expected to come to campus for the exam. The final is on Wednesday, March 22nd, 2006 at 8:30am (sorry, I'm not a morning
2
3 person either). If you have a conflict with either exam, please let me know ASAP. Late Policy: If the class truly simulated a professional software development environment, I would probably only accept late assignments! But since this is a class and I need to give you a grade (and to mimic the realities of late software coming with a penalty), there will be a 5% penalty for each day (not class actual day) that an assignment is late. Of course, if you have a special circumstance (illness, etc.), let me know and well work something out. Honor Code: Although you are encouraged to discuss ideas with others, your programs are to be completed independently and should be original work. Whenever you obtain significant help (from other students, the TAs, students in other classes) you should acknowledge this in your program write-up, e.g. The idea to use an insertion sort to alphabetize the names came from a discussion with my roommate, Eltefaat Borergaard. Any assistance that is not given proper citation will be considered a violation of the Stanford Honor Code. The Honor Code is taken very seriously in this class; any problems will be swiftly referred to the Office of Judicial Affairs. To be even more specific, you are not allowed to collaborate on the coding of your programs, nor are you allowed to copy programs or parts of programs from other students. The following three activities are among what I consider to be Honor Code violations in this course: 1. Looking at another students code. 2. Showing another student your code. 3. Discussing assignments in such detail that you duplicate a portion of someone else's code in your own program.
3