CS 115 Introduction to Computer Programming
Course Syllabus (Night Sections)
Fall 2015
Night Section Lecturer: Mohammad Tariqul Islam E-mail: mtislam.tarik@uky.eduOffice Hours and Location: TBD
Class Webpage http://www.cs.uky.edu/~tarik/teaching/fall2015/cs115/index.html Lecturer: Dr. Neil Moore
E-mail: neil@cs.uky.edu
Office: 207 Hardymon Building Office Hours and Location: TBD
Class Webpage: http://www.cs.uky.edu/~keen/115/115.html
Phone: (859) 218-0056
Course Coordinator
& Lab Instructor: Dr. Debby Keen E-mail: keen@cs.uky.edu
Office: 215 Davis Marksbury Building Office Hours and Location: TBD
Class Webpage: http://www.cs.uky.edu/~keen/115/115.html
Phone: (859) 257-6742
Note: This syllabus is based on CS115 Day Section syllabus (prepared by Dr. Keen and Dr. Neil Moor) with some modifications.
All policies associated with this course are subject to revision. Reasonable notification will be provided to students before any major changes are made.
_____________________________________________________________________
Class Meeting Times
_____________________________________________________________________
Lectures: Two times a week on Tuesday, Thursday from 6:00pm - 7:15pm in Room 115 of College of Nursing Building.
Labs: Once a week on Monday in Ralph G. Anderson Building (RGAN) at the
following times:
Section 401: 5:00pm - 5:50pm in Room 103 of RGAN Section 402: 6:00pm - 6:50pm in Room 103 of RGAN Section 403: 7:00pm - 7:50pm in Room 103 of RGAN Section 404: 8:00pm - 8:50pm in Room 103 of RGAN
Welcome to CS 115!
The Lecturers and Teaching Assistants of CS 115 want to welcome you to CS 115. We hope you find this course to be interesting, useful and stimulating. Please feel that you can ask questions and participate with your fellow students in a friendly learning environment.
We are trying out some new ideas for teaching the class this semester. We will be asking for your feedback on these ideas regularly. Please be as careful, thorough and honest as you can with your answers. They will be carefully considered!
_____________________________________________________________________
Information on Textbook and Required Materials
_____________________________________________________________________
Required Textbook: The textbook used is an online textbook and costs $48. Please go
to Zyante and click on the Student link and create an account. Then get the zyBook with the code UKYCS115Fall2015 and click Subscribe. The book will be used for Homework worth 5% of the grade all semester.
Software: The main programming environment will be Python 3.x. This software is
free and available from www.python.org. The software will be available on computers in many labs on campus and is available to all students in the class for free download. Make sure that you get version 3.x of Python, not version 2! See here for more details about Python. Apple Macintosh computer owners, be especially careful! your computer may already come with version 2.x. You still need to install Python 3.x.
A recommended IDE for Python is WingIDE 101. It is free. It does not crash as often as the IDE provided with the Python interpreter (IDLE). Here is the link to the page where you can download it. There are versions for Windows, Linux and OS X there. Be careful to get the 101 version of WingIDE - they also have professional and shareware versions which are not free.
Recommended Supplies: a pack of 3x5 index cards, used for cooperative learning
assignments. Alternatively, you can use a full or half sheet page (extra page or from notebook – either is fine).
_____________________________________________________________________
Course Description from the Department Web Page
_____________________________________________________________________
From the Department Web Page:
“CS 115 INTRODUCTION TO COMPUTER PROGRAMMING (3)
This course teaches introductory skills in computer programming using an object-oriented computer programming language. There is an emphasis on both the principles and practice of computer programming. Covers principles of problem solving by computer and requires completion of a number of programming assignments.”
Lecture meets twice per week; lab sections meet once per week. This course covers introductory skills in computer programming using Python. The course assumes NO programming experience.
You should already have basic computing skills, like being able to copy files from one place to another, renaming files, making folders. You should expect to spend at least 10 hours per week outside class on this course, on average.
_____________________________________________________________________
Desired Course Outcomes
_____________________________________________________________________ The goals or desired outcomes of this class are that the student will be able to:
1. To acquire an understanding of computer architecture and data representations (variables, representation of numbers and character strings)
2. To learn basic algorithmic problem-solving techniques (decision structures, loops, functions)
3. To be able to use and understand objects used in programming
4. To be able to design, document, implement and test solutions to programming problems
_____________________________________________________________________
Student Evaluation
_____________________________________________________________________ Attendance at Lectures 5%
Lab Attendance and Assignments 8% Homework assignments from Zybook 5% Programming Assignments 32% Two Written Exams during the semester 20%
Lab Test 1 5%
Lab Test 2 5%
Final Exam (Comprehensive) 20%
The two written tests during the semester will be held on the dates given below. They are common hour exams. They will be held in Whitehall Classroom Building Rooms 122 from 7:30 to 9:30 pm.
Test 01 Wednesday, October 7 Test 02 Wednesday, November 11
The lab tests will be given during regularly scheduled lab sessions on Monday in RGAN 103
Lab Test 01 Sections 401-404 Monday, October 12 Lab Test 02 Sections 401-404 Monday, November 30
The final exam will be held according to the published Final Exam Schedule in Memorial Hall Room 103. It is scheduled for Monday of Finals Week, December 14, 6:00 pm - 8:00 pm.
Grading Scale:
_____________________________________________________________________
Policy on Laptop and other Technology Usage
_____________________________________________________________________
Laptops in Lecture
In the lecture laptops and smart phones are serious distractions. People believe that they can multitask during a lecture and still get every word. There are many studies which show this is NOT true. No one multitasks as well as they think they do. There are many case studies which show that students who are distracted with technology do not do as well on tests and on final grades overall. Consider these facts when deciding whether to use a laptop or phone in class.If you have a documented medical reason
for having to use a laptop in class to take notes, then please present this
documentation to Dr. Keen or Dr. Moore. Otherwise, laptops are only allowed on the back row of the lecture hall. That way you distract only yourself, not people
sitting behind you. Phones of any type are not allowed in class.
Laptops in Lab
On the other hand, you are allowed to use your own laptop in any lab session including lab tests. There are computers in the labs in sufficient number for every student, but it is up to you. If you use your computer, you need to have Python 3.x installed on it as well as any IDE you choose.
All policies associated with this course are subject to revision. Reasonable notification will be provided to students before any major changes are made.
_____________________________________________________________________
Makeup Policy for Tests CS 115
_____________________________________________________________________ A student who missed a test (lab or lecture) will be allowed to make it up if the following conditions are met:
• Dr. Keen or your instructor (Mohammad Islam) is contacted by the student within one week after the day the test was scheduled to be taken.
• The reason for the absence can be satisfactorily documented (death in the family, illness serious enough to necessitate a visit to a doctor, an official university trip, etc.)
• The student can schedule enough time with Dr. Keen or Dr. Mohammad Islam to take the test within one week.
If the absence is NOT excused, a makeup exam MAY be allowed with a substantial penalty, determined by Dr. Keen and Mohammad Islam.
_____________________________________________________________________
Your "Magic Excuse" - The Rules
_____________________________________________________________________ Every student starts off with ONE "Magic Excuse" It gives you a 24-hour extension on a program source code deadline. It is ONE-use only.
You use it by emailing your TA or Dr. Keen or Mohammad Islam and stating that you want to use it. You must state your intention to use it BY the "5 days after the deadline" point. That is the point that we stop accepting program source code assignments at all. After that point it is too late to use your "Magic Excuse" on that program.
If you do not use your "Magic Excuse" at all during the semester, it will be worth 10 bonus points on the Final Exam.
If you use the "Magic Excuse", your program source code is NOT eligible for any bonus part of the assignment. So do not use your "Magic Excuse" to try to get the bonus point part finished.
The excuse is NOT transferable. You cannot give it to someone else for their use. This excuse is the equivalent of 10 percent of points on the implementation (source) part of a program assignment. If your program source is more than 1 day late, penalties will accrue as usual after the extension.
This excuse is good only on the implementation phase, the source code part of the program, not the design nor the test cases.
This excuse is NOT a 'free pass' not to do the assignment! It is just a 24-hour extension on the deadline. You are still expected to complete and submit the assignment.
This excuse cannot be used on anything but program assignments. It does not work on labs or quizzes or attendance.
If you have a _UK valid_ excuse for being late like a documented illness, death in family, academic trip, religious holiday, then do NOT use this excuse! Let Dr. Keen or Mohammad Islam know about your valid excuse and give her your documentation and deadlines can be adjusted. You don't need a Magic Excuse for this!
_____________________________________________________________________
Attendance Policies
_____________________________________________________________________ Lecture and lab attendance are required. Attendance will be checked in lecture on random days. Attendance will be checked at all lab periods. Students are expected to come to class on time and stay for the whole period.
The University Faculty Senate states: (Rule V-5.2.4.2) If attendance is required by the class policies elaborated in the syllabus or serves as a criterion for a grade in a course, and if a student has excused absences in excess of one-fifth of the class contact hours for that course, a student shall have the right to petition for a "W", and the Instructor of Record may require the student to petition for a "W" or take an "I" in the course. [US: 2/9/87; RC: 11/20/87] * Here is the source of that rule. Look for 5.2.4.1 Attendance
and Completion of Assignments (about page 130 in the pdf).
If you miss a lecture where attendance is taken, a test or any lab period, you are responsible for contacting Dr. Keen or Mohammad Islam within one week of the absence. If the absence is excused and you have documentation for the absence, credit will be given for attendance or a makeup for the missed test will be arranged without penalty. If you do not have one of the excuses below, you will lose the credit for that attendance. If you do not contact Dr. Keen or Mohammad Islam within the time limit (one week), your absence will be counted as unexcused. For an unexcused absence, a makeup may be allowed, with a penalty determined by Dr. Keen and Mohammad Islam. This penalty can be 50% or more.
Punctuality: Students are expected to come to all classes on time and stay for the whole
period. This is especially important for Lab Tests. Lab Tests end at 10 minutes until the hour. Any work turned in after that deadline will lose 10 percent out of what is possible for each minute late, based on the file's timestamp when it is submitted. Extra time will NOT be given.
Excused absences are the following:
• Illness of the student or serious illness of a member of the student's immediate family.
• The death of a member of the student's immediate family.
• Trips for members of student organizations sponsored by an academic unit, trips for University classes, and trips for participation in intercollegiate athletic events. When feasible, the student must notify the instructor prior to the occurrence of such absences.
• Major Religious Holidays. Students are responsible for notifying the instructor in writing of anticipated absences due to their observance of such holidays no
later than the last day for adding a class.
Written documentation, a paper copy that we can keep, will be required for all excused absences.
Missed announcements, instructions, assignments, etc. due to absence will not constitute acceptable reasons for failing to meet subsequent deadlines. It is the student's responsibility to learn the content of the missed classes and to initiate arrangements with the instructor for making up the work.
NOTE: See definition of excused absences in the current edition of Student Rights and Responsibilities or on the web at http://www.uky.edu/StudentAffairs/Code/. No absence can be designated "excused" until documentation has been provided and verified. Absences due to minor conditions (lack of transportation, slight discomfort, conflict with an appointment, etc.) are considered unexcused, as are absences for registration or advising.
_____________________________________________________________________
Assignments
_____________________________________________________________________ The only way to learn programming is to do programming, so this course will include several programming and lab assignments and homework for you to do on the computers available in the computer labs or at home. All students may download Python for free.
Please do all assignments exactly as they are assigned. Do not change the problem to something you like better. Part of the assignment is to see if you can meet the specifications as given. We also ask this to ensure the programs can be graded in a timely manner, and that the students understand the statements they are using. If you want to use something that has not been discussed in class, ask your TA or Dr. Keen or Mohammad Islam first and don't be surprised if we say no. If you do use more advanced statements without permission, you will be penalized up to 75% on the program grade. See the program assignment page for more discussion of this.
Turn in complete assignments and programs. If you don't have an assignment finished, wait until you are ready to turn in everything you are going to do. If a partial project is turned in, it will be graded as it stands. If more of the project is turned in later on, the entire project is considered as late as the date of the last part turned in, and the entire project is subject to be regraded and to late penalties.
You do NOT have to submit a partial assignment in order to submit a full one later. We grade ONLY the last version submitted. We will NOT "piece together" your work from different submissions.
Save your graded work and programs until you get your final grade. Mistakes do happen during recording, and your copy is your proof of your grade. Do keep electronic copies of your source files, at least until you get the graded results. You will be provided with a record of your scores at various times during the semester. Please check these and let your TA or Dr. Keen or Mohammad Islam know about any discrepancies as soon as possible. Don't wait until Finals!
_____________________________________________________________________
Laboratory Assignments
_____________________________________________________________________ This class has scheduled times for you meet in a computer lab with a teaching assistant. Each lab will have a specific assignment which is posted on the class web page several days before the lab meets. The lab will have Individual problems and Team problems. You must do the Individual problems before the lab session. It will be due at midnight the night before the lab.
The Team problems
Near the start of the semester, you will be assigned to a team. These people will be in your section and will be working on the same problems as you are. The team lab
work will be done with your team members cooperatively, during the lab period. ONE
copy of the work will be turned in for each team. All team members will get the same grade for the lab work. This work will normally be submitted electronically.
NOTE: Team Lab material can certainly appear on tests or be used in programs. This will be individual work. This means that ALL members of a team should be sure to UNDERSTAND the Team Lab, instead of one person relying on another person to do the work.
It is important to communicate frequently with your lab partners. It is the joint responsibility of all partners to make sure the work is turned in on time. Everyone in the team is penalized if this is not done.
Attendance will be taken at all lab periods. Each person will get credit for attendance individually; i.e., your lab partner's attendance won't hurt your grade directly. You are not penalized for attendance if your partner(s) are not in lab. Of course if they are not there, they will not be able to work with you on the assignment, which WILL impact
your lab grade. It is very important that everyone be there! Regular practice is an important part of gaining any skill.
Communication between team members is VERY important! If you have trouble getting in touch with your team mates talk to them about it. Then talk to your TA about it. Team members can and will be reassigned. People who try to get by without doing the work will be assigned NO partner and have to do all the work themselves!
Each team lab assignment's work is officially due at the deadline given by the lab instructor, usually near the end of the lab period. and your team can turn it in then via the submit link.
You are expected to do the individual work of the lab and turn it by the night before the lab session. If you don't do this, you come to class the next day unprepared to help your team do the work. You also do not learn as much when you have not done the preparation ahead of time.
You are expected to come to lab sessions on time. If you are not there, you are not helping your team. If you show up more than 20 minutes late to a lab, you will not be allowed to sign the attendance sheet and you will not get the team points for that day. We will listen to reasons for lateness. If the lateness is not chronic, some adjustments can be made. But if the lateness happens repeatedly no points will be given. It would still make sense to attend, you may learn something useful in the short time you are in lab.
Students are expected to focus on the lab work and the team. You should be asking questions or explaining something to your team mates or listening to a short talk about a topic. If your TA notices that you are distracting yourself and others in lab by spending time on non-class activities, they will ask you to stop and work with your team. If you do not go back to working with your team, you will lose all points on that day's work. If this is repeated, you may lose your team and have to do the work by yourself!
_____________________________________________________________________
Lab Tests
_____________________________________________________________________ There will be two Lab Tests given during the semester - see the schedule for the dates. These will allow you to demonstrate that you can generate a working program from a problem statement in 50 minutes. You can use any kind of text reference you wish. It is open note, open book. You are NOT allowed to communicate with anyone during the test, either orally or electronically. These will be individual, NOT team tests. Each
lab test is worth 5% of your overall grade. If you miss a lab test, the policy for obtaining a makeup is here.
Difference between Lab Assignments and Program Assignments
You are expected to work with your partners on a Team Lab assignment. You are REQUIRED to work individually (by yourself) on program assignments and individual lab assignments.
_____________________________________________________________________
Programming Assignments
_____________________________________________________________________ Programming assignments are different from lab assignments in that they are larger and more elaborate. Typically you will have two to three weeks to do one and turn it in. The Documentation Standard will not be adhered to strictly in lab assignments; it will be in programming assignments. Lab assignments are meant to give you practice writing small pieces of code. Programming assignments allow you to develop larger programs that require more thought and time.
Implementation of programming assignments are meant to be
done by individuals not teams.
Program Test Plans: A test plan is a set of test cases that you have come up with to test your program against. Each case has a description of what it is testing, inputs that cause that case to happen, and the expected output/outcome of that input.
You devise these to make sure that all parts of your program are executed and tested in different situations. Make sure that you use your test plan later when your implementation is done! That is what it is for.
Program Designs: A design or an algorithm is a rough draft or outline of a program. It
is important to do a design before you actually write the program. You will be expected to write a design (in pseudocode) for all programming assignments before the design lab. A lab period will be set aside for discussing designs for program assignments, before the program assignment is due (see the schedule), and your team will submit a design at that time. The pseudocode at that time does not have to be completely detailed, but it has to be mostly complete. Your design grade will be part of the programming assignment grade. There are several examples of designs on the class web page.
Documentation
Documentation is important to any program. With good documentation, you can go back six months later, pick up the program and understand what you did and why you did it! Comments should NOT just repeat code; they should explain WHY the code is the way it is. A programming standard which you are expected to follow will be described and developed during the course. It is posted on the class web page. Programs can lose points for poor documentation or style, even if the
program works! This standard specifically states that you must include your name,
section and email address, the date turned in and the purpose of the program in the header of the program. This is very important if we need to contact you quickly about your program. The header is the first place we will look for your preferred mail address. If nothing is there, the only other address we have is the University one (uky.edu). If you don't get a message in time because it went to the wrong address, that is your problem. You will be penalized for late submission.
_____________________________________________________________________
Due Dates
_____________________________________________________________________ It is not acceptable to email your submission, either lab or program.
Lab Assignments
Every lab assignment will be posted on the page several days before the lab period when it will be due.
Late Policy for Labs The individual part of the lab will be due the night before the lab
meets. It must be submitted by midnight. If it is submitted later than midnight, but before the first lab period of the day (regardless of which section the student is enrolled in), (usually 8 or 9 am), it will be accepted with a late penalty. After that, it is not accepted at all. There is a deadline for the team work, which will usually be during the lab period. Team work will not be accepted after the end of the period. There will be links on the lab assignment page for submitting individual and team lab assignments.
Programming Assignments
The electronic submission of program assignments will be done via a link on the class web page; it can be done as soon as you have your program ready. >p>Program assignments are in 3 parts: test cases, design and implementation. Each of these will have due dates. Test cases and designs will NOT be accepted late.
Late Policy for Programs
Implementations (source code) may be turned in late, but they lose 10 percent of the points possible per calendar day late, up to 5 calendar days late. That is, work that is one day late loses 10 percent, work that is two days late loses 20 percent, and so on. This means that weekends count as days! Programs are submitted electronically so you can submit on Saturday or Sunday.
Some assignments may have bonus parts. If a program is turned in late, it is NOT eligible for any bonus points. This means if you are tempted to turn in an assignment late so you can finish the bonus, don't. The bonus will not be counted. Even if you use the "Magic Excuse" to extend your due date, the bonus will NOT be counted in that case.
Programs will not be accepted more than 5 calendar days late. This means that work
turned in more than 5 calendar days after the deadline will get a grade of zero. This allows your TA to grade most of the submitted programs at the same time, increasing consistency and improving return times for assignments.
If you have an excused absence, some deadline extension will be allowed, determined by Dr. Keen and Mohammad Islam. Contact them immediately.
Late assignments will not be accepted once the graded work has been returned to the class!
Be advised that programming projects require time to prepare and a way to do POORLY on them is to wait to start work the evening before they are due. A program need not be fully functional to receive some credit, but we would much rather see a working program turned in late than one on time which does not work. A program
that does not run because of errors which cause it to crash should not be turned in without being fixed. This means you MUST test your program thoroughly! Python
does not tell you about syntax errors in many cases until you actually run that part of the code. This is another reason to start work on your assignments early - so you will have time to run tests and ask questions before the due date! It is easy to accidently delete a character or comment out a line at the last minute. After you submit your program, check to make sure what you just turned in DOES run! YOU are responsible for making sure your program as turned in will run cleanly! Any checking we do is a courtesy, not a right!
File Formats in Electronic Submissions: You need to know the difference between a
text file and a doc file and a PDF file and an executable file. Very often, the type that is acceptable in electronic submissions is a text file (which include .py files) or a docx or
pdf file (test cases). We will explain how to generate them. Occasionally other files may be required (e.g., a jpg file or a csv file if your program generates one or uses one for input). The assignment will specify what format each file should be in. It is YOUR
responsibility to make sure the files are in the correct format. If we have time and
find files of incorrect formats in a submission, we will try to notify you by email as soon as possible, BUT the submission will be counted as getting later, up until you submit the files in the correct format. This can cost you lots of points on your grade! If the submission is not corrected before the last date we accept the assignment, the program will not be graded and your score will be zero. Make sure you have the files you need and NOTHING else in your submission. When in doubt, show it to your TA or Dr. Keen or Mohammad Islam ahead of time! This also means check your email regularly!
If a solution for an assignment is posted onto the class web site, late work will not be accepted after that time.
_____________________________________________________________________
What to do if you miss
_____________________________________________________________________
• a lecture - find out what the material covered was, read the book, borrow someone's notes, find out what any announcements or assignments were. If attendance was taken and you have a documented excuse as described in the attendance policy, contact Dr. Keen or Mohammad Islam within one week of your absence with your paper documentation.
• a lab - the points for attendance and for the team work cannot be made up unless you have a documented, excused absence. If you have an excuse, make sure you contact Dr. Keen or Mohammad Islam within one week. You MUST still turn in your individual labwork by the deadline for the lab
• a test - if you know ahead of time you must miss a test, contact Dr. Keen or Mohammad Islam and make arrangements for an alternate time. If circumstances force you to miss an exam unexpectedly, you MUST contact Dr. Keen or Mohammad Islam within a week after the test, in order to have a chance to be allowed to make the exam up.
• a deadline on an assignment - see the late policy. Programs are accepted up to 5 days late, with penalty.
_____________________________________________________________________
Who to Contact if...
_____________________________________________________________________ The class has several persons connected with it. For the fastest resolution of most problems, here is a list of problems and who to contact first about them.
If Contact
you have an excused absence from lecture or lab
Dr. Keen or Mohammad Islam with your paper documentation
you find a mistake on your grade records your TA
you know you are going to miss a test Dr. Keen or Mohammad Islam you missed a test unexpectedly Dr. Keen or Mohammad Islam you have a question about how something
was graded your TA
_____________________________________________________________________
You should check
_____________________________________________________________________ This course requires that you act responsibly to get the most out of the class. It is a large class; you have to take care of details that would not be needed in a small class.
• Check the class web page! Lab assignments, program assignments, lecture notes, examples, study sheets are all on there. It is where you submit your work via links. It will change almost daily.
• Check your grades! Look at your graded work and make sure you understand the grade, that you understand why points were deducted. Ask questions if you don't.
• Check your grade online! Fairly early in the semester, you'll be provided with a way to look online at your grade as your TA has it recorded in their spreadsheet. This "informer page" will be updated regularly. Make sure you look at it - proofread it for mistakes and let your TA know if you find one!
Above all, communicate with your TA or Dr. Keen or Mohammad Islam when you have a question or problem! Most things can be corrected very simply. Don't let a situation get worse all semester!
_____________________________________________________________________
Accommodation
_____________________________________________________________________ If you have a documented disability that requires academic accommodations, please contact Dr. Keen or Mohammad Islam as soon as possible. In order to receive accommodations in this course, you must provide a Letter of Accommodation from the Disability Resource Center. If you have not already done so, please register with the Disability Resource Center for coordination of campus services available to students with disabilities (725 Rose Street, Multidisciplinary Science Building, Suite 407, 257-2754, David Beach, dtbeac1@uky.edu).
Accommodations can be made for all parts of the course.
These letters are NOT retroactive! This means that we only make special arrangements for class activities after we receive the letter.
_____________________________________________________________________
Lab Accounts and Electronic Communication
_____________________________________________________________________ We will be using the personal computers in RGAN 103, and your University LinkBlue accounts. Treat your account as you would your personal and confidential records. You must have your University account set up in order to receive your feedback on most assignments.
Do not abuse the computer systems by doing things that are inconsiderate, annoying, or disruptive to other users, or destructive to other accounts. Do not share your account with anyone else. Your right to use the UK computer systems can be taken away if you abuse the privilege.
We will use email to communicate with you quickly. Please check your email regularly! If you don't want to use your University account, forward it to somewhere you DO read. YOU are responsible for all email sent to your University account. Check your email often!
Visit the course homepage often (http://www.cs.uky.edu/~keen/115/115.html). If you have trouble accessing this page or find a dead link, please let Dr. Keen
(keen@cs.uky.edu) know as soon as possible. The syllabus and schedule will be posted there during the entire term. Lab and programming assignments will be posted there. This site is subject to change as necessary.
_____________________________________________________________________
Plagiarism / Cheating
_____________________________________________________________________ Students are expected to do their own work on tests, individual lab work and program assignments. Cheating is considered a serious offense by the University and the Department. Any form of "seeking an unfair academic advantage" is considered cheating.
If an assignment is designated as "cooperative learning" or "team work", then you are allowed, encouraged, in fact required, to work with your team. These are the ONLY students you are allowed to work with. Of course you can also ask questions of Dr. Keen or Mohammad Islam or any TA.
Any other assignment is individual work. That includes program implementations, individual lab parts, lab tests, lecture tests, and quizzes. You can also talk to Dr. Keen or Mohammad Islam or any TA about individual work.
Learning to program is an individual task; you are expected to implement the programming assignments on your own. One person taking any part of another person's work (with or without their permission) and claiming it as his or her own is plagiarism and will not be tolerated. Any occurrences will be dealt with according to the University policy stated here. This policy allows for a minimum penalty of zero on an assignment AND a warning letter in the student's file. Repeat offenders (in ANY class) face increasing penalties with each offense.
The only way to LEARN programming is to DO programming. You may think you have gotten the grade very easily by using someone else's work if the copying is not detected, but you have lost that much experience and will be that much further behind on the next assignment and on the next written test.
If you would agree that "he/she and I worked together" on implementing a program, then we would consider it cheating.
If you and your roommate share a computer, be VERY careful. Your work MUST be your OWN. Discuss your design or algorithm or logic in GENERAL terms, but write your own design, your own test cases and your own code, your own implementation.
Advice: if it makes you uneasy, then it's probably NOT ok. When in doubt, ASK Dr. Keen or Mohammad Islam or your TA before submitting work.
Do not show your source code (implementation) to ANY other student.
It may seem an easy way to "show them how it's done" or "help them understand the problem". It is a recipe for getting into trouble. It is a temptation to copy the other person's work without figuring out how to solve the problem.
It is just as dishonest to allow someone to represent your work as their own as to do the reverse. This also means YOU are responsible for making sure that your code does not accidentally fall into someone else's hands. Don't leave memory sticks or printouts in a lab; don't leave source code files on a hard drive somewhere. Be aware that files that you put on the local hard drive (C or D or E) in a computer lab on campus STAY there until they are deleted. They do NOT automatically go away when you log out! If someone else finds your code and turns it in, YOU are responsible too!
Do not post your code on the Internet. This is an open invitation for someone else in
the class to copy it and turn it in as theirs!
If you get help from a person who is not in the class, be extremely careful. Do not take code from anyone! Make sure the help you get is using the material covered in THIS class. You can be penalized in this situation also. If you work with a tutor, make sure you understand what the tutor is telling you. If they just "transplant" code into your program, (meaning either they wrote it for you or they dictated while you typed) you are being cheated of the understanding you need to do the next program and to take the Lecture tests. This is also considered cheating.
If you cheat on an assignment, you are cheating yourself. You are not getting the experience of working the problem out on your own, and you are not really learning the knowledge you are supposed to get from the assignment. This means that you are that much further behind on the next assignment, on the quizzes and tests. You are hurting your chances of getting the grade you want from the class.
If you are enrolled in this class, you are NOT allowed to be a tutor (either paid or unpaid) in this class. This has caused problems in the past and will not be allowed. If you get stuck at a point in the assignment, that is when you ask for help from the approved sources, TAs, Dr. Keen, Mohammad Islam. Googling the problem is NOT the best way to find a solution! All assignments are designed to use the material covered in class. If you cannot figure out how to solve the problem with that, then it shows that there is something you do not understand about that material. It is a red flag to start asking questions! If you find something on the Net which 'solves the problem'
but you do NOT understand it, you have cheated yourself of the understanding you need. When the next quiz or test or programming assignment comes along, you will not have the knowledge you need.
All programs will be checked by plagiarism detection software. This software works across ALL sections of the class.
_____________________________________________________________________
Withdrawing from Class
_____________________________________________________________________ If you decide to leave the class, please do it officially. There is a date on the Academic Calendar past which you are not allowed to drop for academic reasons, Friday, November 6, 2015. We'd much rather give a W grade than an E. Don't just stop coming to class - you WILL get an E! Take care of your transcript!
All policies associated with this course are subject to revision. Reasonable notification will be provided to students prior to any major changes.
_____________________________________________________________________
Class Locations
_____________________________________________________________________
• Shortcut to Interactive Map with our buildings highlighted
• Whitehall Classroom Building Lectures TR for sections 1-15, 11:00 am - 12:15 pm, CB 118, Common Hour Exams (CB 106, 118, 122)
• Memorial Hall for Final Exam at 6:00-8:00 pm December 14, Monday
• College of Nursing Room 115 for Night Sections (401-404) Lectures
• Ralph G. Anderson Building (RGAN)
o Classroom Lab (Room 103) for Monday and Friday labs (Day Sections
1-15) and Night sections 401-404 (Monday 5pm to 8pm)
o TA office hours (Room 102)
• Davis Marksbury Building Dr. Keen's office (215)
• Hardymon Building Dr. Moore's office (207)
• Engineering Annex (Multilab on 2nd floor) - TA office hours
_____________________________________________________________________
Schedule CS 115 Fall 2015 Night Sections
This schedule is subject to change as the term progresses. Lectures meet on Tuesdays and Thursdays at 6:00 pm.
Lab meetings are on Mondays . Please visit the class website for lab meeting times.
Week
Monday Tuesday Wednesday Thursday Friday Sunday
Lab Lecture Lecture
Program Due Dates Week 01: August 26 - 28 Syllabus, Chapter 1 (Introduction) Week 02: August 31 - September 04 Lab 01 Participation Activity (PA) 1.1-1.7 due at midnight Chapters 1 and 2 (Introduction, Variables and Expressions) Homework 01 due at midnight Chapters 1 and 2 (Introduction, Variables and Expressions) Homework 01 due at midnight Week 03: September 07 - 11 Holiday Chapter 2 (Variables and Expressions) Homework 02 due at midnight Chapter 3 (Types) This week: Monday is Labor Day Holiday Program 01 announced Week 04: September 14 - 18
Lab 02 Chapter 3 (Types)
Test Cases due for Program
01 Chapter 3
(Types)
Design due for Program 01
Week
05: September
21 - 25
Lab 03 Python Graphics
Python Graphics
Program 01 due
Program 02 announced
Week
06: September
28 - October 02
Lab 04 Chapter 4 (Branching)
Test Cases due for
Program 02 Chapter 4
(Branching)
Design due for Program 02 Week
07: October
05 - 09
Lab 05 Review for Lecture Test 01 Lecture Test 01 Wed 7:30 pm Structured Programming This week: Lecture Test 01 Debugging Week 08: October 12 - 16
Lab Test 01 Chapter 5 (Loops)
Chapter 5 (Loops)
Program 02 due
This week:
Lab Test 01 Program 03 announced
Week 09: October
19 - 23
Lab 06 Chapter 5 (Loops)
Test Cases due for Program 03 Chapter 6 (Functions) This week: Monday is Midterm
Design due for Program 03 Week 10: October 26 - 30 Lab 07 Chapter 6 (Functions) Chapter 7 (Strings) Week 11: November 02 - 06 Lab 08 Chapter 7 (Strings) Chapter 8 (Lists and Dictionaries) Program 03 due This week: Friday last day to get W Week 12: November 09 - 13
Lab 09 Review for Lecture Test 2 Lecture Test 02, Wed. 7:30 pm Chapter 8 (Lists and Dictionaries)
This week: Lecture Test 02 Program 04 announced Week 13: November 16 - 20
Lab 10 Chapter 9 (Exceptions)
Test Cases due for
Program 04 Chapter 10
(Files)
Design due for Program 04 Week
14: November
23 - 27
Lab 11 Chapter 10 (Files) Holiday This week: Thanksgiving Holiday W-F Week 15: November 30 -
December 04 Lab Test 02 Chapter 12 (Recursion) Chapter 12 (Recursion) Program 04 due
This week: Lab Test 02 Week 16: December 07 - 11 Lab 12 Chapter 13 (Classes) Review This week: "Dead Week"
We are not finished yet! Next week is Finals Week!
Week Monday
Finals Week: December 14 - 18
This week: "Finals Week" Final Exam on Monday December 14, 6:00 pm - 8:00 pm
_____________________________________________________________________
Additional Information
Pictures of TAs
