Академический Документы
Профессиональный Документы
Культура Документы
Course Information Course number: Course title: Section number: Credit hours: Term: CS 1136 Computer Science Laboratory .603 1 Fall 2011
Contact Information Instructor: Office: e-mail: Phone: Office hours: Assistants: Feliks Kluzniak ECSS 4.403 feliks.kluzniak@utdallas.edu (972) 883-6906 TBD Brian DeVries email: Office hours: Office:
Course Pre-requisites None. Co-requisites CS 1336 .501 Please note that enrollment in this particular section is mandatory. CS 1136 is a laboratory course that is an integral part of the learning package presented in this section of CS1336.
Page 1
Course Description See the syllabus for 1336.501 . CS 1136.101 is a laboratory course whose purpose is to allow the students to apply the knowledge acquired in CS 1336.501 in practice, and thus to deepen and internalize their understanding and to develop elementary practical skills in programming.
Student Learning Objectives/Outcomes As a result of attending the course the students should acquire elementary practical programming skills and an internalized understanding of the fundamental principles of imperative programming that are taught in CS 1336.501 .
Required Textbooks and Materials Materials will be distributed during the course. There is no textbook.
Assignments & Academic Calendar Grades will be based on the grades for assignments set during the lab course.
Grading Policy The grade scale for this course is A+, A, B, C, D, F. F is the failing grade. The final grade will be the average of the grades for all the assignments. However, for each student two assignments with the lowest grades will not be included in the average.
Page 2
Course & Instructor Policies Any student who has difficulty understanding a particular point is expected to interrupt the TA with a question (albeit in an orderly manner). Students are expected to review the relevant course material from the lectures, so that they come to the lab well-prepared to practice it and to ask question about what they dont understand. (The course material for CS 1336.501 is posted on the instructors university web page.) Students are encouraged to discuss their difficulties (related to the lab) with the TA during his office hours.
Submission Policy Submissions for the course are expected to contain the following at the top of each file submitted: Student Name UTD ID # (the number, not your Net-ID) UTD Email Address (Your university email, not personal Gmail / Yahoo / etc. address) Names of students that worked together Given that most of the submissions will consist of code, and that the above information will likely be invalid programming language syntax, the above information should be placed in comments in source code files in order to allow the source code to compile successfully. Submissions are due one week from the date the assignment is given, at the beginning of the lab. Until further notice, lab submissions are to be printed out and turned in in-person, unless prior arrangements are made in advance with the TA.
Page 3
Plagiarism Policy DISCLAIMER: The following is the plagiarism and collaboration policy for CS1136.101 ONLY. This policy does not apply in any fashion in other classes or sections within the UTD Computer Science Department, in other departments at UTD, or at any other university. The student is expected to abide by the plagiarism policy as specified for each course the student is enrolled in. The student is expected to request additional information or clarification from the course instructor if the courses plagiarism policy is unclear. This includes CS1336.501 taught by Dr. Feliks Kluzniak! In this course, the objective is for the students to achieve a comprehensive understanding of the material presented in the course and in the lab. Pursuant to that objective, the TA realizes that working in groups on the lab assignments may prove beneficial to students and wishes to encourage such a collaborative environment. However, with collaboration comes two dangers: 1. The student is misled into believing they have an understanding of the material, only to find this notion dispelled during a test or quiz. 2. The student wholesale copies the work of another student under the guise of collaboration. In order to avoid both of these situations, the TA will examine submissions for similarity to each other. Unfortunately, similarity must by nature be a subjective assessment, so in order to obtain a more objective analysis, all submissions should conform to the following rules: 1. At the top of each assignment file, the student should fill in the Names of students that worked together entry with the names of others the student collaborated with, if any. 2. The student may only collaborate with other students currently enrolled in CS1336.501 and CS1136.101 for the Spring 2011 semester. 3. Students should endeavor not to develop actual source code as a group; rather, collaboration should consist of only discussion of the overall solution, as much as possible. 4. Students should never comment their source code as a group. Such comments are the primary means of assessing the students comprehension of the material, and as such, should be written in the students own words. When grading submissions, if the TA observes that two assignments are similar, the following metric will be applied: 1. If the students for each assignment are listed in each others collaboration list, then proceed. Otherwise, the assignment lacking the listing will be given a grade of 0. 2. If the comments for both students code is extremely similar or identical, then both assignments will be given a grade of 0. 3. Otherwise, although the two code bases may be similar, the TA will conclude that each student has arrived at their own understanding of the code as indicated in their comments, and will grade the assignments as normal. If a student receives a grade of 0 on the basis of this policy, the student is encouraged to discuss it with the TA during office hours.
Page 4
Academic Integrity
The faculty expects from its students a high level of responsibility and academic honesty. Because the value of an academic degree depends upon the absolute integrity of the work done by the student for that degree, it is imperative that a student demonstrate a high standard of individual honor in his or her scholastic work. Scholastic dishonesty includes, but is not limited to, statements, acts or omissions related to applications for enrollment or the award of a degree, and/or the submission as ones own work or material that is not ones own. As a general rule, scholastic dishonesty involves one of the following acts: cheating, plagiarism, collusion and/or falsifying academic records. Students suspected of academic dishonesty are subject to disciplinary proceedings. Plagiarism, especially from the web, from portions of papers for other classes, and from any other source is unacceptable and will be dealt with under the universitys policy on plagiarism (see general catalog for details). This course will use the resources of turnitin.com, which searches the web for possible plagiarism and is over 90% effective.
Page 5
Email Use
The University of Texas at Dallas recognizes the value and efficiency of communication between faculty/staff and students through electronic mail. At the same time, email raises some issues concerning security and the identity of each individual in an email exchange. The university encourages all official student email correspondence be sent only to a students U.T. Dallas email address and that faculty and staff consider email from students official only if it originates from a UTD student account. This allows the university to maintain a high degree of confidence in the identity of all individual corresponding and the security of the transmitted information. UTD furnishes each student with a free email account that is to be used in all communication with university personnel. The Department of Information Resources at U.T. Dallas provides a method for students to have their U.T. Dallas mail forwarded to other accounts.
Page 6
Disability Services
The goal of Disability Services is to provide students with disabilities educational opportunities equal to those of their non-disabled peers. Disability Services is located in room 1.610 in the Student Union. Office hours are Monday and Thursday, 8:30 a.m. to 6:30 p.m.; Tuesday and Wednesday, 8:30 a.m. to 7:30 p.m.; and Friday, 8:30 a.m. to 5:30 p.m. The contact information for the Office of Disability Services is: The University of Texas at Dallas, SU 22 PO Box 830688 Richardson, Texas 75083-0688 (972) 883-2098 (voice or TTY) Essentially, the law requires that colleges and universities make those reasonable adjustments necessary to eliminate discrimination on the basis of disability. For example, it may be necessary to remove classroom prohibitions against tape recorders or animals (in the case of dog guides) for students who are blind. Occasionally an assignment requirement may be substituted (for example, a research paper versus an oral presentation for a student who is hearing impaired). Classes enrolled students with mobility impairments may have to be rescheduled in accessible facilities. The college or university may need to provide special services such as registration, note-taking, or mobility assistance. It is the students responsibility to notify his or her professors of the need for such an accommodation. Disability Services provides students with letters to present to faculty members to verify that the student has a disability and needs accommodations. Individuals requiring special accommodation should contact the professor after class or during office hours.
These descriptions and timelines are subject to change at the discretion of the Professor.
Page 7