CIS 3022 – Programming for CIS Majors I
|
Instructor: |
Pete Dobbins |
Office: |
CSE E428 |
|
E-mail: |
Office |
|
|
|
Phone: |
392-6866 |
Hours: |
The purpose of this course is for students with little or no background in computer science to be introduced to the technical aspects of the field of computer science. Due to the nature and complexity of this field of study, the course will be time consuming and requires serious dedication on the part of each student. Among other topics, we will learn how to solve problems, transform the solution into a program written in the Java programming language, and visa versa.
Although no programming background is expected, be aware that you will be expected to learn how to program and doing so requires very technical work. Attention to detail and analytical thinking will be expected. The programming projects will require students to spend an extensive amount of time working outside of class. In addition, rote memorization is necessary to recall the syntax and definitions of Java and computer science. Please arrange your schedule accordingly.
CIS 3023 – Programming for CIS Majors II should be taken the semester following your completion of this course.
No text is required for this course. All material covered will be given in lecture. However a few recommendations for good supplements are given here. The cheapest and fastest way to purchase them is online.
Here is an approximate schedule of the topics that will be covered each week. More details about each topic and exact dates can be seen on the calendar pages of the course web site.
Week # |
Dates |
Topics |
Barker |
|
|
|
|
|
|
1 Aug |
24 – 30 |
Introduction |
Ch 2 (p15-32) |
|
2 |
31 – Sep 6 |
Java Installation, Binary |
App C |
|
3 Sept |
7 – 13 |
Low Level System, Pseudo Code, Variables |
Ch 2 (p33-38) |
|
4 |
14 – 20 |
Literals, Primitive Types, Input |
Ch 2 (p32-38) |
|
5 |
21 – 27 |
Operators, If/Else, Switch |
Ch 2 (p38-48) |
|
6 |
28 – Oct 4 |
Repetition, Loops |
Ch 2 (p49-52) |
|
7 Oct |
5 – 11 |
Nested Loops |
See online ref |
|
8 |
12 – 18 |
Methods |
Ch 4 (p95-108) |
|
9 |
19 – 25 |
Recursion, Arrays |
Ch 6 (p216-227) |
|
10 |
26 – Nov 1 |
Spring Break |
|
|
11 Nov |
2 – 8 |
Problem Analysis, Assertion |
Ch 10 (p355-365) |
|
12 |
9 – 15 |
Objects, UML, Class Design |
Ch 3 |
|
13 |
16 – 22 |
Class Design, Object Relationships |
Ch 5 (p167-174) Ch 10 (p368-403) |
|
14 |
23 – 29 |
Inheritance |
Ch 5 (p174-205) |
|
15 |
30 – Dec 6 |
Object Casting, Polymorphism |
Ch 4 (p115-116) Ch 5 (p188-191) Ch 7 (p273-281) |
|
16 Dec |
7 – 13 |
Review |
|
|
17 |
14 – 20 |
Final Exam |
|
General course policies can be found at: http://www.cise.ufl.edu/~pjd/admin/policies/course.html. You are expected know and follow all of these policies.
You may consider lecture notes posted online to be buried treasure … they will be hard to find! At best, if there is something posted, it will only be a note shell. More often, nothing will be posted at all, so you must plan on attending lecture.
There will be seven projects worth 5% each minus one drop for a total of 30%, three exams worth 20% each minus one drop for a total of 40%, and a cumulative final exam worth 25%. Any of these values may be modified by +/- 5%. All projects are due via the course submission system by midnight on the date assigned within the project specification. The due date of corresponding lab activities will be assigned separately. If you will be absent from discussion, ensure your lab activities have been delivered to your discussion leader before the lab meeting time. The examination schedule is:
|
Exam |
Day |
Date |
Time |
Location |
|
|
|
|
|
|
|
1 |
Tuesday |
09/30/08 |
8:20 – 10:10 PM |
See Calendar |
|
2 |
Tuesday |
11/04/08 |
8:20 – 10:10 PM |
See Calendar |
|
3 |
Tuesday |
12/09/08 |
8:20 – 10:10 PM |
See Calendar |
|
Final |
Wednesday |
12/16/08 |
7:30 – 9:30 AM |
TUR L011 |
All projects are due via the course submission system and the project schedule is (note these are anticipated dates and are subject to change depending upon the speed at which we cover the course material):
|
Project |
Day Due |
Date Due |
Time Due |
|
|
|
|
|
|
0 |
Friday |
09/12/08 |
11:59 PM |
|
1 |
Friday |
09/19/08 |
11:59 PM |
|
2 |
Friday |
09/26/08 |
11:59 PM |
|
3 |
Friday |
10/17/08 |
11:59 PM |
|
4 |
Friday |
10/31/08 |
11:59 PM |
|
5 |
Friday |
11/21/08 |
11:59 PM |
|
6 |
Monday |
12/15/08 |
11:59 PM |
Diligence Points – 5% of your grade will be based on your diligence in attempting to learn the course material. This will be judged by many different things including, lecture attendance (although not mandatory, attending lecture will be necessary if you expect to succeed in this course), discussion attendance (mandatory and taken), class participation, asking appropriate questions, your picking up of previous work when it is returned, attempting all projects, quizzes, and exams.
All grading/re-grading issues must be resolved within 1 week of the graded work being returned. You must return exams and quizzes to your discussion leader, along with a printed (not handwritten) attachment stating the reasons for the re-grade. Do not write anything on the exam itself or detach (un-staple) the pages from each other. If you do so, your exam will not be re-graded. For project re-grading, see the TA who grades your assignment in his or her office hours immediately. Note, when requesting a re-grade, the whole exam/project/quiz is subject to the re-grade, not just the portion you specify. We will be happy to discuss the solution and answer any questions, however no change will be made after the allotted week has passed.
There will be no make-ups, except for serious medical reasons with a medical practitioner’s note.
Any curve will be determined at the end of the semester, after every student has taken the exam and no judgment can be made beforehand. Since new exams, projects, and quizzes are given every semester, the scale of a previous semester has no bearing or indication as to the final scale for this semester. The grading ranges will be created based upon the complete analysis of every student’s final average. The range used to calculate your final letter grade will be no harsher than the typical grading scale (A 100 – 90, B+ 90 – 88, B 88 – 80, C+ 80 – 78, C 78 – 70, etc). A 75 or higher is required to receive an S (Satisfactory), when taking the course SU. The formula used to calculate your final total of points is:
Final Exam Total = ( Final Exam / 100 ) * 25
Project Total = ( ( Sum of Project Scores – Lowest Project Score ) / 150 ) * 30
Exam Total = ( ( Sum of Exam Scores – Lowest Semester Exam Score) / 200 ) * 40
Final Total = Final Exam Total + Project Total + Exam Total + Diligence Points
There will be no discussion sessions the first week of classes. Discussions will meet for the first time starting Thursday, September 4, 2008. There will be no office hours the first week of classes. If you need to see me, do so after lecture or schedule an individual appointment.
All projects are due at 11:59 PM on the assigned date. No late submissions will be accepted. You will submit a soft copy (a .java file) of your project, using a web-based submission system. Never submit a .class file. Submitting the wrong file and not following the instructions will result in an automatic loss of points on the project. Some projects will also require you to submit a second file, the specifications for this file submission will be explained at the time the project is assigned. Here are the steps to follow:
1. Clearly place your name, section number, group number, and the name of your partner in a comment at the top of your program. Here is the format you should follow:
|
Name |
Meriadoc 'Merry' Brandybuck |
|
Section |
1234 |
|
Group |
1 |
|
Partner |
Peregrin 'Pippin' Took |
2. Create any diagrams, write ups, etc, required by the project.
3. Write the program.
4. Test the program. Compile and run the program on your own, verifying it works correctly.
5. Submit the .java file (and only the .java file unless specified to submit a separate file as well) via the web-based submission system.
Here are the individuals that you should see concerning the following topics:
|
Course Policies |
Pete & Any TA
|
|
Course Material Questions |
Pete & Any TA
|
|
Project Questions |
Any TA
|
|
Exam Grading |
Your Discussion Leader
|
|
Project Grading |
The TA/Grader assigned to grade your projects
|
|
Picking Up Graded Work |
Your Discussion Leader
|
Listed here is the contact information of each Grader and Teaching Assistant (referred to in this document as TAs).
Name |
Office |
Phone |
|
Office Hours |
|
|
|
|
|
|
|
Tony |
CSE E309 |
392-1183 |
pchuchai@cise.ufl.edu |
See Daily Schedule |
|
Yuchu |
CSE E309 |
392-1183 |
ytong@cise.ufl.edu |
See Daily Schedule |
All discussions will meet in CISE classroom labs located through the main CISE lab in CSE E114. You must attend the discussion section in which you are registered (attendance is mandatory). You will be allowed to miss two discussions without penalty. Here are the days, periods, locations, discussion leaders, and project graders for each section. Note that TA discussion & grading assignments are projected and could change as the semester develops.
Section |
Day |
Period |
Location |
Discussion Leader |
|
|
|
|
|
|
|
5993 |
Thursday |
8th |
CSE E113 |
TBA |
|
5994 |
Thursday |
4th |
CSE E113 |
TBA |
|
5996 |
Thursday |
9th |
CSE E113 |
TBA |
|
6909 |
Thursday |
7th |
CSE E113 |
TBA |
|
6925 |
Thursday |
6th |
CSE E113 |
TBA |
|
9504 |
Thursday |
5th |
CSE E113 |
TBA |
|
9509 |
Thursday |
3rd |
CSE E113 |
TBA |
Come to my office hours and the TA’s office hours. We will be glad to help you as much as possible. Above I refer to the “timeliness of questions”, office hours are always a good time to ask any question of the appropriate person. Please remember to follow the guidelines above.
Whenever you send email to me or a TA, the email must have CIS 3022 (and only CIS 3022) as its subject. Also, within every email, whether you deem it helpful or not, clearly place your name, section number, group number, and the name of your partner at the top of the email. If you receive a reply to an email that does not contain this information, go buy a lottery ticket immediately. Your luck can not get any better. Any email without this information will be deleted. As above, here is the format you should follow:
|
Name |
Bullwinkle J. Moose |
|
Section |
4321 |
|
Group |
25 |
|
Partner |
Rocket J. 'Rocky' Squirrel |
Before emailing questions, always read the syllabus, announcements, and schedule. It is quite possible that your question has already been answered in one of these places.
I and the TAs will answer your questions and resolve your issues the quickest and most clearly in office hours. We receive many emails and reply to them in their order of importance. If you would like to ensure your question is moved to the top of the list, see us in office hours.
Always start early. The projects and your studying will be easier the sooner you begin. Starting early will allow you more time to ask the specific questions you need answered in order to complete the projects and understand the material on the exams and quizzes.
Never place your Social Security # or UF ID # on any course material.
If you choose to use a laptop during lecture, do not use an optical mouse. If you are using a laptop during lecture, use it only for the purpose of taking notes and following along with our topic of discussion. Do not play games, chat, or create any similar distractions for yourself and your classmates during lecture. Turn off your cell phone, laptop speakers, and all other electronic devices before lecture begins.
Never ask questions that can be answered by reading the syllabus, doing so may cause you to lose diligence points. Examples are questions such as “Where is the TA’s office?” or “What are your office hours?”. Copies of the syllabus are available on the course web site for your convenience.
Never ask when grades will be posted. We always post grade information as soon as possible. Each time you ask when grades will be posted, you will lose at least 1 diligence point. If you would like a grade to be clarified, see the appropriate TA in his or her office hours immediately.
We will adhere to the academic honesty policies of the University of Florida, which can be seen at www.dso.ufl.edu/Academic_Honesty.html. When a breach of these policies occurs, the University requires that an adjudication form be submitted to Judicial Affairs regarding the circumstance. The incident will then be investigated by Judicial Affairs and when an incident is found to have broken the University of Florida’s Student Honor Code, a penalty is assessed. Penalties range from grade reductions to expulsion from the University. In addition, a notation of the incident is placed on the student’s permanent record.
All coursework: exams, projects, homework and so on are to be done individually. A list covering some examples of actions which break the honor code is given here. When working in an assigned group activity, these policies hold across groups.
Recall, our course provides office hours for your assistance in understanding course material. Take advantage of these hours to receive help with your comprehension of the topics being addressed.
Students requesting classroom accommodation must first register with the Dean of Students Office. The Dean of Students will provide documentation to the student who must then provide this documentation to the Instructor when requesting accommodation. Your documentation and specific needs must be given to me as soon as possible, so that appropriate arrangements are made.
In order to take this course, sit in on the course, or complete an incomplete of this course every student must be officially registered in either the normal fashion or through the auditing process. Any student not officially registered is in violation of UF policy and subject to the penalties set forth by the University.
This document is subject to change at the discretion of the instructor, based on unforeseen circumstances occurring during the semester.