Course Syllabus:
- Principles of Programming II
- Computer Science 1321
- 12:30-1:20 Halsell 340
Instructor:
Office:
Spring 2012 Office Hours:
- MWF 9:00am-9:30am
- MWF 10:30am-12:30pm
- MWF 2:30am-4:30pm
- Others by appointment
Spring Meeting Hours and Room:
- 2321-1: 9:30-10:20 MWF, Halsell 340,
- 1321-3: 12:30-1:20 MWF, Halsell 340,
- 2324-1: 1:30-2:20 MWF, Halsell 340
Textbook:
- Bradley N. Miller and David L. Ranum, "Problem Solving with Algorithms and Data Structures using Python" Franklin Beedle and Associates, 2006.
Course
- This course is the second course for computer science majors, following
the guidelines established by the Association for Computing Machinery. This
course also partially satisfies the requirements for the common curriculum,
specifically the "Using the Scientific Method" category. It will build on the
material presented in the prerequisite course, CSCI 1320. The course will
teach object oriented programming techniques including how to design and
implement programs in that style. The course will improve your ability to
solve problems using computer programs of your own construction. The course
will further your ability to use more complex data structures and algorithms
in the solution of such problems and help you get a feel for how large
programming projects can behave and how you can do things to make them easier
to work with. Prerequisite: CSCI 1320 or consent of instructor
Course Goals and Objectives:
Topics to be covered include, but are not necessarily limited to the following:
- Review of control structures, functions and primitive data types in Python
- Object oriented design and programming, class, inheritance, polymorphism
- Data Structures: arrays, linked lists, stacks, queues, trees
- Sorting
- Searching
- Recursion
- Event driven programming
- GUI construction
- Simple graphics and animation
- Use of an API
- Analysis of algorithms
- Use of python library classes
- Threads, processes and parallelism
- Applications
Laboratory problems:
- Several homework laboratory problems will be required for successful
completion of this course. Problems will be coded in python on the departmental
unix network. Homework solutions must represent your own individual effort.
Each laboratory will include a formal report detailing the results of your
experiments. The requirements for your laboratory report submission will be
detailed in class. Laboratory reports are due at the beginning of class on
the day assigned, otherwise they are late.
Grades:
- The grades in this class will be determined by the results of three major
examinations, given at approximately equal intervals in the semester, by the
results of several laboratory assignments, and by the results of periodic
quizzes. Each of the three examinations will be approximately equally
weighted, including the final, which will be given during the final
examination week, and will serve as the third examination. Each examination is
comprehensive, emphasizing the most recent material, but covering the entire
semester. Each of the laboratory assignments will be worth a variable number
of points, depending on difficulty. Averages will be calculated as a simple
percentage, points earned divided by points possible. Attendance and
class participation also play a role in the determination of your grade.
(see below)
- Letter grades will be assigned according to the following scale:
- 90-100 -- A
- 80-89 -- B
- 70-79 -- C
- 60-69 -- D
- below 60 -- F
- Plus and minus grades assigned in marginal cases. I advise you to keep
a track of your scores so you know where you stand in the class at any time.
Examination Dates:
Examination 1:
February 13, 2012
Examination 2:
March 23, 2012
Reading Days:
April 30, May 1, 2012
Final Examinations
- CSCI 2324: May 3, 2012, 8:30am
- CSCI 1321: May 4, 2012, 12:00pm
- CSCI 2321: May 7, 2012, 12:00pm
Important Dates:
Click Here for Important Dates
Spring Final Exam Schedule
Final Exam Schedule
Spring 2012 Calendar Showing Examination Dates
Spring 2012 Calendar
All students are covered by the Trinity University Honor Code that prohibits
dishonesty in academic work.
The Code asserts that the academic community is based on honesty and trust,
and defines specific violations as well as the procedure to determine if a
violation has occurred. The Code also covers the process of hearings for
alleged violations and the various sanctions applied for specific violations.
The Code also provides for an appeal process.
The Code is implemented by the Academic Honor Council. Under the Code, a faculty
member will (or a student may) report an alleged violation to the Academic Honor
Council. It is the task of the Council to collect the pertinent evidence, adjudicate,
and assign a sanction within certain guidelines if a violation has been verified.
Students who are under the Honor Code are required to pledge all written work that
is submitted for a grade: "On my honor, I have neither given nor received any
unauthorized assistance on this work" and their signature. The pledge may be
abbreviated "pledged" with a signature.
The specifics of the Honor Code, its underlying philosophy, and the norms for
sanctioning can all be found on the Academic Honor Council website, accessed
through the Trinity Homepage.
NOTES:
1. Regular class attendance is required. Role will be taken and attendance is
considered mandatory.
One point will be awarded for each class attendance and one point will be deducted
for each unexcused absence. These points will be included in the calculation of
your final averages as described above in the section on "grading."
Excessive absences will be reported to you and to appropriate university
officials and may cause you to be withdrawn from the class. Excused absences
require a note from the appropriate university offical or from appropriate
medical personnel.
2. Homework assignments that are identical beyond coincidence are in
violation of the Academic Integrity policy of the university and will
result in disciplinary action, including, but not limited to a failing
grade on that assignment for all parties involved. You are responsible
for the security of your work, both electronic and hard copy.
3. Discussion of the homework assignments between students is encouraged,
but when it comes time for the final submission, make sure it is your own
work. You are cheating yourself if you get the homework from some source
other than creating your own.
4. Homework will be due at the beginning of the class period on the day
assigned. LATE WORK WILL NOT BE ACCEPTED. Make sure you resolve problems
with printing, workstations, communication, etc. IN ADVANCE so your work
may be submitted in a timely manner. Homework will NOT BE ACCEPTED FOR
CREDIT if submitted late. Those of you who submit work late penalize
the conscientious students who turn in their work on time.
5. The only exceptions to these policies are for University sanctioned
activities or illness and require a note from your supervising professor
(coach) or doctor. If you have unusual circumstances (as we all sometimes
do) please discuss these with your instructor in advance.
Return to Dr. Eggen's Home Page