|
|
|
|
|
COMS W4156 Advanced Software EngineeringFall 2009: Prof. Gail KaiserTue/Thu 11:00am-12:15pm
|
 |
Instructor:
Professor Gail Kaiser Office: 607 CEPSR Office hours: immediately after class, or by appointment Phone: 212-939-7081 Email: kaiser+4156@cs.columbia.edu (make sure to include the '+4156') |
|
| TA:
Mr. Nipun Arora Office: 608 CEPSR Office hours: Tue and Fri 3-4pm Office phone: 212-939-7184 Email address: nipun@cs.columbia.edu |
|
| TA:
Mr. Jonathan Bell Office: 6LE1 CEPSR Office hours: Mon 3-4pm and Thu 4-5pm Office phone: 212-939-7100 Email address: jsb2125@columbia.edu |
|
|
REQUIRED
Author: Ian Sommerville |
|
|
RECOMMENDED
Author: Ron Patton |
Students may use any machines and accounts available, provided that they can (1) install and run their team's component model framework; (2) develop and test their project code together with the other member of their programming pair, integrate together with the other pair in their team, and demonstrate their project to the teaching staff; (3) submit written assignments in plain text, html, MS Word or Adobe PDF format (with any figures embedded or viewable via Firefox with only standard plugins); and (4) access the class website and CourseWorks over the Web. It is highly recommended but not required that students obtain CS accounts (CLIC/MRL).
Regular attendance is required. Short "pop quizzes" will be given at approximately the middle of the class period several times during the semester; the scheduling of these quizzes will not be announced in advance, since everyone is expected to attend every class. Waivers or makeups for these quizzes will be available only in the event of severe illness, dire emergencies and religious observances. Please present appropriate documentation to the instructor regarding the nature and duration of the illness or emergency as soon as possible thereafter; the instructor should be reminded of upcoming religious observances in advance.
Midterm and Final "Individual Assessments" are given as take-home examinations with approximately one week between posting and submission deadline, the MIA near the middle of the semester and the FIA near the end. There will be no other exams (except see "pop quizzes" above). The registrar may schedule a 3-hour exam period during finals week, ignore it.
The MIA and FIA should be treated with the same seriousness as in-class exams, and are weighted analogously to conventional exams in the final grade breakdown (see breakdown). The assessments must be completed by each student working individually. See the academic honesty policy.
All students are required to form themselves into "pairs" of two (2) members each; if there is an odd number of students enrolled in the class, then exactly one (1) "triplet" of three (3) members is permitted. There may not be any "onesies"! The teaching staff will assist the pairs in forming teams, ideally each consisting of two (2) pairs, but students are encouraged to form their own 2-pair teams in advance. If some students drop the course, any remaining pair or team members may be arbitrarily reassigned to other pairs/teams at the discretion of the teaching staff (but are strongly encouraged to re-form pairs/teams on their own and inform the teaching staff as soon as possible of any new arrangements).
All assignments other than the individual assessments correspond to milestones in the team project. Team members should work together throughout their project; pair or individual responsibilities for specific project milestones or portions of project milestones should be organized within the team. See the academic honesty policy.
Team members who do not contribute appropriately should be brought to the attention of the teaching staff as soon as possible. Such team members may receive a significantly lower grade for the relevant project assignment(s) than the rest of that team, possibly "zero", may be reassigned to another team, and/or may be asked to withdraw from the course.
10% "pop quizzes" and class participation, 20% Midterm Individual Assessment, 20% Final Individual Assessment, 50% Team Project.
Extensions may be arranged only in the event of severe illness, dire emergencies and religious observances, and the duration of the extension will be at the discretion of the instructor in accordance with university policies. Please present appropriate documentation to the instructor regarding the nature and duration of the illness or emergency as soon as possible thereafter; the instructor should be reminded of upcoming religious observances in advance.
Assignments submitted late will not be read or graded, and will receive no credit. CourseWorks timestamps will be used to determine time of submission. All assignment deadlines are US Eastern Time (local NYC time) unless otherwise announced by the teaching staff.
For the purposes of this course, students are permitted and encouraged to "reuse" existing open source or public domain code as well as any publicly available utilities, tools, frameworks, APIs, IDEs, etc. However, all such "reuse" must be clearly documented in the submitted assignments (e.g., by providing the download url together with a prose explanation of what, specifically, was adopted/adapted). Students are not permitted to "reuse" any code or systems that are not available to the general public, with the sole exception of code they wrote themselves personally (where there are no proprietary claims, e.g., by the student's current or former employer). All members of a team will be held responsible for any occurrences of plagiarism, even when that portion of the code was produced by a single team member.
Documentation other than in-code comments, i.e., for the various written prose assignments, may not be "reused" under any circumstances. All reference materials, whether electronic or physical, must be listed in the submission. Students must write in their own words, without any copying or paraphrasing from reference materials, with the sole exception of very short quotations (e.g., one or two sentences or an image) that are clearly indicated as quotations (e.g., placed in quote marks) and explicitly cited (e.g., [David Pogue, Behind the Scenes of "iPhone: The Musical", Pogue's Posts, The New York Times, July 12, 2007, http://pogue.blogs.nytimes.com/2007/07/12/behind-the-scenes-of-iphone-the-musical/]). All members of a team will be held responsible for any occurrences of plagiarism, even when that portion of the document was produced by a single team member.
Also see the department's academic honesty policy.
Last updated September 23, 2009.
|
Copyright © 2009 Gail E. Kaiser. All rights reserved. Report broken links or other problems with this website to the instructor. |
