Computer Science 2101 - Data Structures
Syllabus - Fall Semester, 2009

MWF 2:15pm-3:20pm (Science 1030), Tuesday 12:00-1:50 pm (Science 2610)
pre-requisite: CSci 1201 OR CSci 1301 OR permission (OR (CSci 1001 AND CSci 1101) may possibly count - see me for more information)
5 credits

Final Exam: Monday, December 14, 2009, 4-6pm


Contact
Info
Instructor:
Kristin Lamberty (aka: "kk")

Contact Guidelines:
I will be in my office with the door open during office hours. Please feel free to stop and see me during those times. If I can not be there during the scheduled hours, I will attempt to let the class know in some fashion. I tend to prefer email over telephone contact, though I will accept either. Please make certain that you sign your e-mails and that you make it clear what the e-mail is about. This will help me to help you. Especially helpful is including the course number (2101) in the subject.

Communication is important. If something is unclear, please ask. If there is a problem, please bring it to my attention. It is impossible to be responsive to your needs if you do not make it clear that help is needed. Remember, feedback helps make the class and my teaching better! I will show you respect by being responsible for facilitating your learning to the best of my abilities. I will do my best to be approachable and to be timely in my work. I will do my best to honestly and accurately answer your questions. I will admit when I don't know an answer, but I will try to either find the answer later or point you to a good resource.

It is important that the class learning environment feels SAFE to you. You should not be subjected to harassment based on gender, race, ethnicity, orientation or creed. If there are problems regarding the learning environment, please let me know what can be done to improve the situation. If I am the source of the problem, and you are not comfortable with bringing it to my attention, contact another CSci faculty member or the Division Chair for help.

Office:
Science Bldg 2370
e-mail:
lamberty@morris.umn.edu
phone:
589 6351
homepage:
http://www.morris.umn.edu/~lamberty
Office Hours:
Th 10-noon, 4-5pm, or by appointment on other days

Course
Materials
Texts:
Data Abstraction and Problem Solving with Java: Walls and Mirrors, second edition, covers java 5.0, Carrano & Prichard
Using your course materials:
The Carrano & Prichard book will serve as your Data Structures/Algorithms book. I really like how this book presents data structures moving from an abstraction with pesudocode to a more concrete implementation. The exercises are informative and helpful.
Head First Java, 2nd Edition (covers Java 5.0), Kathy Sierra & Bert Bates Head First Java will serve as your Java guide book (if you choose to purchase it - it is optional). I particularly like its thoughtful, educational approach. I think you will find it useful for understanding how things work in Java.
Software:
Java 2, J2SE 6.0 (1.6)
(download for free from Sun)
You may download a free version of Sun's Java Operating Environment, Development Kit, etc. by going to the links found on my web pages for this course. We have the Java language available in our CSci laboratories, but if you wish to work in your own home/room, feel free to download this software.
Eclipse
(download for free from eclipse.org)
Eclipse is a programming environment. It is installed in the lab and can be downloaded free if you wish to use it. Eclipse is NOT required for you to work with Java, but many prefer to use either it, or programs called jEdit or jGrasp to begin. We will also use Dr. Java sometimes.
linux The laboratory is run under a linux operating system. You can still do programming tasks on Windows or MacOS boxes as well. However, you will be expected to do some work in the labs during laboratory hours. You will be given the commands and knowledge to do that which is necessary to complete your tasks, there is no expectation that you should either become an expert in, or even like, linux. However, you ARE expected to perform work in this lab environment.
Web resources:
Moodle
Please go to the course Moodle and bookmark it. As the semester progresses, you will find materials there that will supplement your reading and your learning (additional subject or lecture notes, links, review sheets). You will also find lab descriptions, project descriptions, assignment descriptions, a course schedule, this syllabus and other items that may be of use to you. You are required to check the Moodle at least one time between class meetings. Most of our communications outside of lecture and lab will happen via the Moodle.
Java documentation Often called "javadoc", you will need to be able to locate and understand information using this documentation. This is especially helpful for understanding code you did not write.

Grading
Labs (including some "in-lab" activities) 30%
Assignments (Problem Sets and other) 25%
Quizzes and Whaddayaknows 15%
Midterm Exam 15%
Final Exam 15%
You should always focus on learning the material. I realize that there is a great deal of pressure to receive high marks/grades. However, if you focus on the grade, you will fail to focus on the very thing that can earn you the grade you want. Achieve the goal of becoming confident in your knowledge of the material. If you do this, you will find that you will earn a grade you will be pleased with.

A somewhat standard 90%(some kind of A), 80% (some kind of B), 70% (some kind ofC), 62% (either a D+ or D, D- does not exist) scale will be used. Results are NOT curved.


Policies

All class policies are based on responsible and respectful behavior and actions. Flexibility within the framework of any class is always more possible as long as requests follow these principles.

You may appeal any grade or policy you feel is inappropriate. Provide an appeal in writing (on paper). Outline why you think the decision or policy is wrong. Set a meeting time to discuss the issue and so that you can advocate for your position. Decisions regarding your appeal will be made at that meeting. If you feel the process was unsatisfactory, you may use the grievance process provided by UMM.

General policies
  • You may use two grace days however you would like throughout the term - this means you may turn in one assignment two "school days" late, or two assignments one "school day" late with no penalty (where a "school day" is a day that classes, though not necessarily this one, meet on campus - e.g. no weekends or holidays will count against you). I will try to grade your assignment quickly, but you might not get your grade with everyone else.
  • Late assignments not using grace days will be accepted until two weeks after the due date for 75% of the points as the new maximum number of points possible. Note: If the asignment has been graded and returned (or feedback posted on the Moodle), you will have to make an appointment and sit in my office while I grade the assignment. You will have to show me what you did and why. This will show me that you understand the work and it will prevent me from letting ungraded work pile up. This policy will enable me to give you prompt feedback on your work (which will help you learn more and be more productive in this course). So, if you turn it in late, you run the risk that you will have to show me every step of what you did to solve the problem, and you will be docked 25%.
  • Do your own work. It will be clear when you are expected to do work without collaboration. It will be equally clear when collaboration is encouraged. However, even when you work with others, you are expected to provide an equal share of the effort. Please see UMM policies if you feel you must review the consequences of failure to comply with this.
  • Attendance is encouraged, but not mandatory. I reserve the right to refuse to repeat myself incessantly due to your absence. But, I will work with you if I am forewarned of an absence. In-class activities will occur in this class frequently.
  • The University of Minnesota is committed to providing all students equal access to learning opportunities. Disability Services is the campus office that works with students who have disabilities to provide and/or arrange reasonable accommodations. Students registered with Disability Services who have a letter requesting accommodations, are encouraged to contact the instructor early in the semester. Students who have, or think they may have, a disability (e.g. psychiatric, attentional, learning, vision, hearing, physical, or systemic), are invited to contact Disability Services for a confidential discussion at 320-589-6163 or freyc@morris.umn.edu. Additional information is available at the DS web site at www.morris.umn.edu/services/dsoaac/dso.

Course
Work
Labs
  • will occur in the Computer Science lab in the Science building
  • will always be on Tuesday from 12 until 1:50pm. An outline of instructions will appear on the Moodle the day of the lab (perhaps earlier). You are expected to do work on the lab during the class time AND you are encouraged to continue to work on the lab outside of lab time. Lab materials do two things - they help encourage you to do work that is part of the projects and they encourage you to get coding practice in.  There is no other way to learn to effectively code.
  • will be diverse in nature. Some will be collaborative, some will not. Most will involve Java programming. See directions for each. There will be lab activities that require your presence in the lab... some kind of like quizzes, some group activities.
  • will be due on Fridays at the start of class unless otherwise specified
  • early in the semester will focus on learning how to use Java. Later labs will focus on using Java to implement algorithms and data structures.
Assignments
  • are done outside of class and will be individual work, unless otherwise noted.
  • are given to encourage you to exercise data structures concepts and problem solving.
  • will be evenly spaced through the semester and will be made due at some point prior to the midterm exam that will cover the material found in that assignment.
  • are due at the BEGINNING of class on their due dates.
Quizzes and "Whadayaknows"
  • are individual work
  • are given often throughout the term as an opportunity for you to show me what you know
  • often contain questions that are similar to those found on the midterm or final exams
  • need to be taken at the scheduled times (quizzes cannot be made up unless prior arrangements have been made for an excused absence, whaddayaknows may be made up as quizes between the date missed and the next class period)
Exams
  • are individual work, closed book (unless otherwise stated).
  • must be taken at the given exam times unless you have contacted me at least 24 hours prior to the event with a reasonable excuse and have worked out an alternative with me.
  • The final exam will occur as scheduled. A review sheet will be available. Focus of this exams will be on concepts, structures and algorithms, though some Java coding may also appear on these as a medium for illustrating the ability to convert to/from representations and trace through code.

Official Grading policy:

For undergraduate courses, one credit is defined as equivalent to an average of three hours of learning effort per week (over a full semester) necessary for an average student to achieve an average grade in the course. For example, a student taking a three credit course that meets for three hours a week should expect to spend an additional six hours a week on coursework outside the classroom.


Academic Integrity

Academic integrity is essential to a positive teaching and learning environment. All students enrolled in University courses are expected to complete coursework responsibilities with fairness and honesty. Failure to do so by seeking unfair advantage over others or misrepresenting someone else's work as your own, can result in disciplinary action. The University Student Conduct Code defines scholastic dishonesty as follows:

"Scholastic Dishonesty: Scholastic dishonesty means plagiarizing; cheating on assignments or examinations; engaging in unauthorized collaboration on academic work; taking, acquiring, or using test materials without faculty permission; submitting false or incomplete records of academic achievement; acting alone or in cooperation with another to falsify records or to obtain dishonestly grades, honors, awards, or professional endorsement; altering forging , or misusing a University academic record; or fabricating or falsifying data, research procedures, or data analysis."

Within this course, a student responsible for scholastic dishonesty can be assigned a penalty up to and including an "F" or "N" for the entire course. If you have any questions regarding the expectations for a specific assignment or exam, ask.

This page: http://www.morris.umn.edu/~lamberty/cs2101/index.html last updated 8-23-2009

The views and opinions expressed in this page are strictly those of the page author. The contents of this page have not been reviewed or approved by the University of Minnesota.