CIS 3023 – Fundamentals of Programming for CIS Majors II
|
Instructor: |
Pete Dobbins |
Office: |
CSE E452 |
|
E-mail: |
Office |
|
|
|
Phone: |
352.450.5452 |
Hours: |
The purpose of this course is to build upon the foundation developed in CIS 3022 (pre-requisite). Students will learn more about the technical aspects of the field of computer science, including further object-oriented concepts, problem solving, user interfacing, and system testing.
Due to the nature and complexity of computer science, this course will be time consuming and requires serious dedication on the part of each student. Attention to detail, analytical thinking, logical problem solving, and Java programming is very technical work and will be expected of you from day one in the semester. In addition, as in any course, rote memorization is necessary to recall the terms, definitions, and syntax taught. Please be aware of these points and arrange your schedule accordingly.
Here is our textbook. You will find resources from the textbook given here and additional supplements can be found on our course website. Our textbook will assist us with the design concepts needed to structure objects within a programmatic solution. It will also provide review of the syntax and structure of Java elements.
· Introduction to Programming and Object Oriented Design Using Java, Third Edition, Nino & Hosch, 2008, John Wily & Sons, ISBN 978-0-470-12871-8.
Here is an approximate schedule for the semester. Further details can be found on the Calendar pages of the course website.
Week # |
Dates |
Topic |
Reading |
|
|
|
|
|
|
1 Aug |
22 – 28 |
Design Specs, Software Engineering |
Ch 0, 1 |
|
2 |
29 – Sept 4 |
Polymorphism |
Ch 2, 3 |
|
3 Sept |
5 – 11 |
Assertion |
Ch 4, 5 |
|
4 |
12 – 18 |
Problem Solving |
Ch 6, 7 |
|
5 |
19 – 25 |
Interfaces |
Ch 8, 9 |
|
6 |
26 – Oct 2 |
Graphical User Interfaces |
Ch 10, Ch 17 |
|
7 Oct |
3 – 9 |
Graphical User Interfaces |
Ch 11, Ch 17 |
|
8 |
10 – 16 |
Testing |
Ch 6 |
|
9 |
17 – 23 |
Exceptions |
Ch 15 |
|
10 |
24 – 30 |
File IO |
Ch 16 |
|
11 |
31 – Nov 6 |
Recursion, Searching |
Ch 14, 19 |
|
12 Nov |
7 – 13 |
Recursion, Sorting |
Ch 14 |
|
13 |
14 – 20 |
Array List, Stack, Linked List |
Ch 12, 19, 21 |
|
14 |
21 – 27 |
Array List, Stack, Linked List |
Ch 12, 19, 21 |
|
15 |
28 – Dec 4 |
Iterators |
Ch 22 |
|
16 Dec |
5 – 11 |
Review |
|
|
17 |
12 – 18 |
Final Exams Week |
|
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.
There will be four exams worth 20% each. Your lowest exam score will automatically be dropped (providing an inherent make up option for you). Your three highest exam scores will account for 60% of your grade. The examination schedule is:
|
Exam |
Day |
Date |
Time |
Location |
|
I |
Tuesday |
10/05/10 |
8:20 – 10:10 PM |
See Calendar |
|
II |
Tuesday |
11/02/10 |
8:20 – 10:10 PM |
See Calendar |
|
III |
Thursday |
12/02/10 |
8:20 – 10:10 PM |
See Calendar |
|
IV |
Tuesday |
12/07/10 |
8:20 – 10:10 PM |
See Calendar |
There will be six projects worth 6.67% each for a total of 40% of your grade.
All projects are due via the university submission system Sakai 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 |
|
I |
Monday |
09/20/10 |
11:59 PM |
|
II |
Monday |
10/04/10 |
11:59 PM |
|
III |
Monday |
10/18/10 |
11:59 PM |
|
IV |
Monday |
11/01/10 |
11:59 PM |
|
V |
Monday |
11/15/10 |
11:59 PM |
|
VI |
Wednesday |
12/01/10 |
11:59 PM |
Any of these values may be modified by +/- 5%.
All grading/re-grading issues must be resolved within 1 week of the graded work being returned. You must return exams 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 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.
Any curve will be determined at the end of the semester, after every student has all the course work and no judgment can be made beforehand. Since new exams and projects are given every semester, the scale of a previous semester has no bearing or indication 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 grading scale (A 100 -to- 92, A– 92 -to- 89, B+ 89 -to- 86, B 86 -to- 82, B– 82 -to- 79, C+ 79 -to- 76, C 76 -to- 72, C– 72 -to- 69, etc). The formula used to calculate your final total of points is given here. In this example, each exam is worth 100 points and each project is worth 25 points. Semester by semester the point total of assignments may vary, however the logic of the formula remains the same, i.e. the sum of the points you earn will be divided by the sum of the maximum points available.
Exam Total = ( ( Sum of Exams – Exam Drop ) / 300 ) * 60
Project Total = ( ( Sum of Project Scores ) / 150 ) * 40
Final Total = Exam Total + Project Total
A note from the University Curriculum Committee: “A C– will not be a qualifying grade for critical tracking courses. In order to graduate, students must have an overall GPA and an upper-division GPA of 2.0 or better (C or better). Note: a C– average is equivalent to a GPA of 1.67, and therefore, it does not satisfy this graduation requirement. For more information on grades and grading policies, please visit: http://www.registrar.ufl.edu/catalog/policies/regulationgrades.html”
There will be no office hours and no discussion sessions the first week of classes. If you need to see me, do so after lecture or schedule an individual appointment. Discussions sessions will begin meeting for the first time Tuesday, August 31, 2010.
All soft copies of 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 the university submission system Sakai. 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 or a hard copy of your solutions. The specifications for this type of submission will be explained at the time the project is assigned. When creating solutions, follow these steps:
1. Place your name and section number (commenting as necessary) at the top of all files.
2. Create any diagrams, write ups, etc, required by the project.
3. Develop your programmatic solutions.
4. Test the program. Compile and run the program, verifying it works correctly.
5. Submit the .java file (and only the .java file unless specified to submit additional files as well) via Sakai.
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 |
Any TA
|
|
Project Grading |
Any TA
|
|
Picking Up Graded Work |
Any TA
|
Here are the Teaching Assistants (referred to in this document as TAs):
Name |
Office |
Phone |
|
Office Hours |
|
|
|
|
|
|
|
Christan |
CSE E309 |
392-1183 |
cgrant at cise dot ufl dot edu |
See TA Schedule |
|
Shayan |
CSE E309 |
392-1183 |
sjaved at cise dot ufl dot edu |
See TA Schedule |
All discussions will meet in CSE E113. You must attend the discussion section in which you are registered (attendance is mandatory). Here are the days, periods, locations, discussion leaders, and project graders for each section. Note that this is tentative and could change, based on any last minute departmental needs pertaining to TA assignments.
Section |
Day |
Period |
Location |
|
|
|
|
|
|
8226 |
Tuesday |
4th |
CSE E113 |
|
8228 |
Tuesday |
5th |
CSE E113 |
|
8229 |
Tuesday |
6th |
CSE E113 |
|
8230 |
Tuesday |
7th |
CSE E113 |
|
7255 |
Tuesday |
8th |
CSE E113 |
Come to my office hours and the TA’s office hours. We will be glad to help you as much as possible. Office hours are always a good time to ask any question of the appropriate person. Please remember to follow the guidelines above to more effectively answer your question.
Whenever you send email to me or a TA, the email must have CIS 3023 (and only CIS 3023) as its subject. Also, within every email, whether you deem it helpful or not, clearly place your name and section number at the top of the email. Emails without this information are often harder to answer. Here is the format you should follow:
|
Name |
Bart Simpson |
|
Section |
4321 |
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.
We always post grade information as soon as possible. If you would like a grade to be clarified, see the appropriate TA in his or her office hours immediately.
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.
I am available through email at all times. Outside of office hours, it is the best and quickest way to contact me. You may call my office phone, however be aware that I check and reply to emails sooner than phone messages.
Never place your Social Security # on any course material, unless you are directly instructed to.
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.
As a rule all coursework: exams, projects, homework, and so on are to be completed 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.
A note from the University Curriculum Committee: “Honesty Policy – All students admitted to the University of Florida have signed a statement of academic honesty committing themselves to be honest in all academic work and understanding that failure to comply with this commitment will result in disciplinary action. This statement is a reminder to uphold your obligation as a UF student and to be honest in all work submitted and exams taken in this course and all others.”
Students requesting classroom accommodation must first register with the Dean of Students Office. That office will provide the student with documentation that he/she must provide to the course 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.
Resources are available on-campus for students having personal problems or lacking clear career and academic goals. The resources include:
· University Counseling Center, 301 Peabody Hall, 392-1575, Personal and Career Counseling.
· SHCC mental Health, Student Health Care Center, 392-1171, Personal and Counseling.
· Center for Sexual Assault/Abuse Recovery and Education (CARE), Student Health Care Center, 392-1161, sexual assault counseling.
· Career Resource Center, Reitz Union, 392-1601, career development assistance and counseling.
All faculty, staff, and students of the University are required and expected to obey the laws and legal agreements governing software use. Failure to do so can lead to monetary damages and/or criminal penalties for the individual violator. Because such violations are also against University policies and rules, disciplinary action will be taken as appropriate. We, the members of the University of Florida community, pledge to uphold ourselves and our peers to the highest standards of honesty and integrity.
This document is subject to change at the discretion of the instructor, based on unforeseen circumstances occurring during the semester.