Computer Science 2100
If you wish, you may download a printable version of the original syllabus. However, all of that information is also on this web page and the web page will be updated as the course proceeds, whereas the printed syllabus will not.
"The design, implementation and use of data structures. Principles of abstraction, encapsulation and modularity to guide in the creation of robust, adaptable, reusable and efficient structures. Specific data types to include stacks, queues, lists, priority queues, dictionaries, trees and graphs."
The official prerequisite is a C- or better in either CSCI 145+146 or CSCI 150, and a passing grade or concurrent enrollment in MATH 135 or equivalent.
This is an undergraduate course that is a follow-up to an introductory programming course. The goal of that first course can be viewed as gaining the ability to write computer programs for accomplishing tasks. The key in that course was that programs must work correctly for the task at hand. In this course, we will focus on the fact that there are actually many different ways to correctly solve a particular problem and that these different methods may vary greatly in efficiency and adaptability.
What we will find is that writing a "good" program is not as simple as starting with a correct program and then improving it. Instead, the quality of a program is most determined by key thoughts and decisions that take place long before the first line of code might be written. Relevant issues include the choice of data structures that are used to organize all of the information within a program, and the structure and level of generality which allow components of a program to be better maintained, reused, and adapted.
In hand with this emphasis on writing good programs and designing useful data structures, the course will reinforce aspects of object-oriented programming using the C++ programming language. Since the majority of students will enter this course having used Python in CSCI 150, we do not assume any familiarity with C++ at the onset of this course. In the early parts of the course, we will draw comparisons between these two languages to help in the transition.
|Instructor:||Dr. Michael Goldwasser|
|Email:||goldwamh at our university domain|
|Office:||Ritter Hall 108|
The material will be presented in four weekly meetings, one of which will typically be used as a hands-on lab. Attendance is expected and class participation is most welcome. These meetings will offer learning opportunities that cannot be recreated purely from readings. Information on the lecture topic can often be found on the course schedule web page.
With the exception of the first day's printed handouts, most of the information for this course will be distributed only by means of the course web page. This web site will contain all assignments, a schedule of lectures, detailed lecture notes and links to many other sources of information.
The web page contains some information (e.g. solutions, submitted assignments, individual grades) that is more sensitive and therefore which will be available to students in the class only after they have identified themselves properly. To gain access to these parts of the web page, a student must first complete the following online questionnaire, creating a unique identity and password.
All assignments for this course must be submitted electronically! The submission procedure will be done through the course web page, and allows students to submit from any computer connected to the Internet. Each student in this class will be selecting a unique username/password combination solely for use in identifying the student when using the course web page.
Details of the submission procedure are discussed on a separate web page.
Face-to-face contact in class and in office hours is most desirable. Yet email is a convenient form of communication as well. I try to respond to email promptly, including at least once each evening when possible.
If your question involves your progress on a current programming assignment, my response will be more informative if you can point out the specific problem you have encountered, and if I am able to see all of your source code. Therefore I strongly suggest that you either attach all relevant files to the email or submit preliminary versions of such files through our online system.
We expect there to be a total of 8-10 written homework assignments during the course. At the end of the semester, we will ignore your lowest of the homework grades, with the remaining homeworks contributing equally to this portion of the grade.
These will generally be due at the beginning of class on the assigned due date. The problems will consist of short questions reinforcing the material in the lectures, readings and programs. Each homework will contain one or more practice problems that are not to be turned in and which can be discussed freely between classmates. The problems that are to be submitted for a grade, however, must be done entirely individually. A more complete explanation of our policy towards Academic Integrity is given below.
Most Thursdays will be devoted to a hands-on "lab" problem. Each will have a formal "pre-lab" exercise that must be submitted individually at the beginning of class that Thursday. The rest of the lab will be completed in pairs, ideally during the Thursday class period. However, we will allow for the lab (but not the prelab) to be submitted anytime by 11:59pm on the subsequent Friday.
The labs will be graded on a simple 3-point scale. One point is awarded for successfully submit the prelab exercise. A second point is awarded for any sincere attempt at the lab activity, and a third point is awarded for successful completion of the lab activity. At the end of the semester, we will ignore your lowest of the lab grades, with the remaining scores contributing equally to this portion of the grade.
We expect there to be a total of 8-10 programming assignments during the course. At the end of the semester, we will ignore your lowest of the program grades, with the remaining programs contributing equally to this portion of the grade.
On certain assignments, you will be required to work individually; on others you will be allowed to work in pairs. Early in the course you will have approximately one week for each assignment; later in the course you will often have two weeks. The assignments will be submitted electronically and generally due at 11:59pm on the assigned due date.
Both homework and programming assignments will generally include a small extra credit challenge. Please notice, however, that the actual extra credit given for these challenges is relatively insignificant. Students who are seriously concerned about improving their overall grade would be best advise to focus all efforts on doing as well as possible on the required work and in preparing for exams.
Our true reason for including these opportunities is to provide some fun and encouragement for students who wish to dig a bit deeper than was required in an assignment. For those students, the chosen extra credit challenges provide a good next step.
Letter grades will be based on each student's overall percentage of awarded points according to the following formula.
Students are expected to have read and abide by the University statement on Academic Integrity available on page 58 of the Saint Louis University's Undergraduate Catalog. A more detailed policy statement is given by the College of Arts & Science, also applying to this course.
In addition to those general statements, we wish to discuss our policy in the context of this course. When it comes to learning and understanding the general course material, you may certainly use other reference materials and you may have discussions with other students in this class or other people from outside of this class. This openness pertains to material from the text, practice problems, general syntax and use of the C++ language or other computing tools.
However, when it comes to work that is submitted for this course, you are not to use or to search for any direct or indirect assistance from unauthorized sources, including but not limited to:
Acceptable sources of information include consultations with the instructor, teaching assistants, or members of organized tutoring centers on campus, as well as any materials explicitly authorized in an assignment. Even in these cases, if you receive significant help you should make sure to document both the source of the help as well as the extent.
On certain programming assignments, we will explicitly allow students to work in pairs. In this case, conversations between partners is both permissible and required. Furthermore, both students are expected to contribute significantly to the development of the submitted work. It is unethical to allow a partner to "sign on" to a submission if that partner did not significantly contribute to the work.
Any violations of these policies will be dealt with seriously. Penalties will apply as well to a student who is aiding another student. Any such violations will result in a minimum penalty of a zero on the given assignment that cannot be dropped, and severe or repeated violations will result in an immediate failing grade in the course. Furthermore all incidents will be reported in writing to the Department and/or the Dean, as per the College procedure.
All exams must be taken promptly at the required time. Requests for rescheduling an exam will only be considered if the request is made prior to the start of the exam, or else in an "emergency" situation with appropriate documentation.
For both written and programming assignments, we wish to allow students to continue to work comfortably beyond the official deadline when a little more time will result in more progress, while at the same time discourage students from falling significantly behind pace and jeopardizing their success on future assignments. Our solution is the following exponentially decaying late formula (some have suggested that we should offer extra credit to anyone who fully understands this formula).
We will consider an assignment submission "complete"
when any part of the assignment is last submitted or
modified. Any assignment that is not complete promptly by
its due date and time will be assessed a penalty based on the
The above policies will be waived only in an "emergency" situation with appropriate documentation.
In recognition that people learn in a variety of ways and that learning is influenced by multiple factors (e.g., prior experience, study skills, learning disability), resources to support student success are available on campus. Students who think they might benefit from these resources can find out more about:
Students who believe that, due to a disability, they could benefit from academic accommodations are encouraged to contact Disability Services at
Course instructors support student accommodation requests when an approved letter from Disability Services has been received and when students discuss these accommodations with the instructor after receipt of the approved letter.
Our department employees many junior/senior computer science majors to help out in our department labs. Those students are also available to provide assistance with course materials at such times.
Our department web page maintains a current list of the available times and locations .
As stated in the section on Academic Integrity, these tutors are an acceptable resource for help, yet you should still document both the source of the help as well as the extent, if significant.
Our department runs a computer server named turing that serves as the primary computing environment for this course. If you do not already have an account on this machine from a prerequisite course, please let us know and we will create a new one.
See further documentation regarding use of turing's facilities.
Please note: you are not explicitly required to use turing as your computing platform, but it is the only platform that we will officially support. If you wish to use another platform for completing your assignments, please feel free to do so.