The objective of this course is to give a hands-on introduction to:
By the end of the semester, you should be able to
The topics covered in this course include:
This text gives a very detailed explanation of UNIX network applications programming and along the way covers most other aspects of the UNIX applications programming, such as process creation, job control, signals, and I/O. However, the coverage of network programming is more detailed than we will need for this course, and the coverage of other aspects of the UNIX API is more diffuse than would be ideal for this course. However, there is probably no other book that would be better, and this is an excellent reference book. In class, we will only approximately follow the order or presentation of topics of the textbook, but you will be expected to read the entire book in parallel. In class we will digress from the text to fill in some background information on some aspects of the UNIX API earlier than they appear in the book.
The final letter grade for the course will be given based on four components: 4-5 individual programming assignments (tentative), one term group project, one midterm, and one final. It is expected that half of the class will get A/A- grades. The grade point distribution among the four components is as follows:
Grading of programming assignments will be based not only on functionality, portability, and correctness, but may also on your understanding of your program. Late assignments will be accepted with 10% penalty each day for up to two days. The following grading policy will apply to all programming assignments unless explicitly modified:
A [90-100] A- [88-90) B+ [85-88) B [80-85) B- [78-80) C+ [75-78) C [70-75) C- [68-70) D [60-68) F <60
Attendance Policy:The university requires attendance in all classes, and it is also important to your learning. The attendance record may be provided to deans who request it. If your grade is just a little below the cutoff for a higher grade, your attendance will be one of the factors that we consider, in deciding whether to "bump" you up to the higher grade. Missing three or fewer lectures will be considered good attendance.
Excused absences include documented illness, deaths in the immediate family and other documented crises, call to active military duty or jury duty, religious holy days, and official University activities. Accommodations for these excused absences will be made and will do so in a way that does not penalize students who have a valid excuse. Consideration will also be given to students whose dependent children experience serious illness.
You should let me know in advance, when possible, and submit the documentation I seek if you miss a class. You should make up for any materials missed due to absences.
Missed exam Policy:A missed exam will be recorded as a grade of zero. We will follow the university rules regarding missed final exams (see http://registrar.fsu.edu/dir_class/fall/exam_schedule.htm), for all the exams, including the final exam.
Late Assignment Policy:
- An assignment that is turned in no more than 24 hours late will be scored with a 10% penalty.
- An assignment that is turned in more than 24 and no less than 48 hours late will be scored with a 20% penalty.
- An assignment that is turned in more than 48 hours late will receive the score of zero, though we will review it and comment on it.
Incomplete Grade (Grade of 'I') Policy:The grade of 'I' will be assigned only under the following exceptional circumstances:
- The final exam is missed with an accepted excuse for the absence. In this case, the final exam must be made up during the first two weeks of the following semester.
By turning in work for a grade in this course you are representing it as being entirely your own individual work. Unless otherwise specified in writing, all programming projects are individual projects. If any assignment permits teamwork, it will be explicitly stated so in the assignment, and then the work is required to be only the work of the people on the team.
What does ``individual work'' mean? An intelligent person searches publications (including the web) for information, ideas, and code. If you use information or ideas obtained from the work of another person you must at least give credit via comments in your code stating what you have used, where you obtained it, and who is the person to whom credit is due. (Beware: If an idea is patented the above is not enough; you should not use it at all without a license.) If you use any code written by another person you must first obtain permission from the author or copyright owner, then mark the beginning and end of the quoted code using appropriate comments, and include a comment giving where you found the code and the the name of the author or copyright holder. Failure to follow these rules will be considered a violation of the Academic Honor Code.
Students with disabilities needing academic accommodations should:
This syllabus and other class materials are available in alternative format upon request.
For more information about services available to FSU students with disabilities, contact the Assistant Dean of Students:
Student Disability Resource Center
874 Traditions Way
108 Student Services Building
Florida State University
Tallahassee, FL 32306-4167
phone: (850)644-9566 (VOICE) | (850)644-8504(TDD)