next up previous
Next: About this document ...

Department of Computer Science, Clemson University
CpSc 372:
Introduction to Software Development

Policies and Information
Brian Malloy, PhD
August 18, 2004

Office: 313 McAdams Hall Phone: 656-0808
Office Hours: Thu 3:30 to 5:00 e-mail:
No office hours on Mon or Fri URL:
No office hours during final exams TA: Me!

  1. Texts: The official text is UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition by Martin Fowler. You may also want to get a Python book, but there are a lot of them that are free on the web. I will place selected notes on my webpage.

  2. Tentative Grading Policy ( 15%):
    2 Exams 40% Dates: Sep 29th, Oct 27th
    Comprehensive Final Exam 20% Date: Thu Dec 9th, 8-11 AM
    Assignments 20%  
    Project 10%  
    Quizzes 10%  
    Fall Break   Nov 1st-2nd, Mon & Tue
    Last drop date w/out W   Aug 31st, Tue
    Last drop date   Oct 8th, Fri
    Final Exam Week   Dec 4th to Dec 11th, Sat - Sat

  3. Posting of grades: My web site contains a special page for this course. This page will include this policy statement, the syllabus, lecture notes & examples, previous exam questions, and a regularly updated list of your grades. This option of seeing your grades permits you to monitor your progress and validate the grade numbers that I keep. It is your responsibility to make sure that these numbers are correct and to inform the instructor within one week of each posting.

  4. Course objective: to master the art of software development using the object-oriented paradigm. Our study will include requirements solicitation and specification, software design including the use of design patterns, coding, testing and maintainence.

  5. Attendence: Many studies have found that the single factor that contributes the most to success in a course is class attendance. Failure to attend not only hurts you, but places an extra burden on the instructor and detracts from the overall quality of the course. If you have exceeded 2 unexcused absenses before the drop date you will be dropped from the course. If you miss a class, your absense will be excused if you: (1) send me email either before or after the class, (2) call me and speak to me or leave a voice message, (3) stop by before or after class, or in my office. If you arrive late, please stop by after class and make sure that I have marked your attendance.

  6. Classroom Behavior: please do not engage in side conversations during class.

  7. Venue. McAdams 114 on Mon & Wed from 2:30 until 3:45. If the instructor has not arrived by 2:45, you may assume that there is a problem and you may depart. But, if I have not arrived by 2:40, I sure wish you would come and get me!

  8. Classroom approach. I will present material that focuses on software development and I will demonstrate the material during lectures.

  9. Grading. The grading scale is: 90+ is an A, 80+ is a B, 70+ is C, 60+ is D. I will not offer extra credit: please do your best in assignments, exams & attendance.

  10. Exams. Any questions about grading must be addressed within one week of grade posting. The instructor reserves the right to regrade the entire exam.

  11. The option of auditing a course is not permitted in the computer science department.

  12. Dishonesty. Each student must do his or her own work independently. The university policies on academic dishonesty apply: "Therefore, we shall not tolerate lying, cheating, or stealing in any form".

  13. Assignments. There will be programming assignments as well as other kinds of assignments. These projects represent an important part of the course. It will be very difficult for you to pass this course without an in-depth knowledge of object technology and programming. The particular language vehicle that we will use is Python. You will probably be assigned 7 projects, including 5 programs that capture important concepts about software development, OO, GUIs and internet programming. However, I suggest that you write more programs, to help you understand the concepts well and to practice so that programming in Python becomes second nature.

    You may consult my web page to see your grade and individual feedback will be provided upon request during office hours.

    Assignments submitted late will receive a zero grade. However, assignments submitted on time will always receive more than zero. If you submit your assignment late you will always have a good excuse to explain your late submission and it will rarely be your fault. However, in fairness to others, I cannot accept a late assignment for any individual student even with a ``good'' excuse. The assignment grades will be weighted at the discretion of the instructor.

  14. Help If you encounter problems or difficulty with your Computer Science class, there are several places that you can go to get help and assistance.

    First, speak to your professor or TA about the difficulty you are having. Many times a brief discussion will clarify things enough to get you back on track.

    Second, if you are having recurring or consistent problems with the course content, go to the Academic Support Center (located in the Cooper Library) and take advantage of the tutoring and supplemental instruction opportunities they offer on a regular basis. If your specific class is not listed, the ASC will begin sessions for groups of three or more.

  15. This course policy and the syllabus are available on my web page:

next up previous
Next: About this document ...
Brian Malloy 2004-08-18