-
Notifications
You must be signed in to change notification settings - Fork 4
/
cs210.html
653 lines (597 loc) · 18.5 KB
/
cs210.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html> <head>
<title>CAS CS210 Computer Systems Fall 2013</title>
</head>
<body link="#FF0000" vlink="#FF0000" alink="#000000">
<div style="position: relative;
background: url(images/cs210banner.png); width: 702px; height: 217px;">
<div style="position: absolute; top: -25px; left: 110px; width:
500px; font-size: xx-large; text-shadow: 0.10em 0.15em 0.2em black; font-weight: bold; color: #fff; text-align: left">
<p>CAS CS210 Computer Systems<br>Fall 2013</p>
</div>
<div style="position: absolute; bottom: 5px; left: 20px; width: 113px; height: 51px;">
<a href="http://www.bu.edu"><img src="images/bu.gif" width="113px"; height="51px"></a>
</div>
<div style="position: absolute; bottom: -20px; left: 135px; width:
800px; font-size: x-large; text-shadow: 0.10em 0.10em 0.2em black; font-weight: bold; color: #f00; text-align: left">
<p>
<a href="http://www.cs.bu.edu">Department of Computer</a><br>
<a href="http://www.bu.edu/cas">College of Arts and Science</a>
</p>
</div>
</div>
<blockquote>
<hr>
<b>
This page <a
href="http://www.cs.bu.edu/~jappavoo/webpages/cs210.html">http://www.cs.bu.edu/~jappavoo/webpages/cs210.html</a>
will NOT be generally updated. We will typically use the course's
piazza site (<a href="http://piazza.com/class#fall2013/cs210">http://piazza.com/class#fall2013/cs210</a> for all online information other than grades.
For grade information we will use the course's Blackboard site (<a
href="http://learn.bu.edu">http://learn.bu.edu</a>)
</b>
<ul>
<li><a href="#announce">Announcements</a></li>
<li><a href="#instructor">Instructor & Office Hours</a></li>
<li><a href="#tf">Teaching Fellow & Office Hours</a></li>
<li><a href="#time">Time And Place</a></li>
<li><a href="#syllabus">Syllabus</a></li>
<li><a href="#schedule">Class Schedule</a></li>
<ul>
<li><a href="#byweek">By Week</a></li>
<li><a href="#exams">Tests/Exams</a></li>
<li><a href="#asched">Assignment Schedule</a></li>
</ul>
<li><a href="#esub">Assignments</a></li>
<li><a href="#oref">Online References</a></li>
<li><a href="#honesty">Academic Honesty</a></li>
</ul>
<hr>
</blockquote>
<hr>
<h1><a name="announce">Announcements</a></h1>
Read and sign copy of <a href="#syllabus">syllabus</a> for submission at your first
discussion.
See the course's
piazza site (<a
href="http://piazza.com/class#fall2013/cs210">http://piazza.com/class#fall2013/cs210</a>)
for all online information other than grades.
All future announcements will be done via the piazza site so please be
sure to have register correctly.
<hr>
<hr>
<h1><a name="instructor">Instructor</a></h1>
<a href="http://www.cs.bu.edu/~jappavoo">Prof. Jonathan Appavoo</a>
<br><a href="http://www.bu.edu/maps/?id=757">Math & Computer Science
Building</a> Office: <b>284</b>
<br> 111 Cummington Street, Boston, MA
<br>Email: jappavoo (at) cs.bu.edu
<br>Office Hours: Tuesday, Thursday 4:00-6:00PM
<hr>
<h1><a name="tf"></a>Teaching Fellow</h1>
<a href="http://cs-people.bu.edu/kzhao">Katherine Zhao</a>
<br>Email: kzhao (at) cs.bu.edu
<br>Office Hours: Monday 2:00-4:00PM, Friday 3:00-5:00PM
<h1><a name="ua"></a>Undergraduate Assistant</h1>
George Silvis, III
<br>Email: gsilvis (at) bu.edu
<br>Office Hours: Wednesday 4:00-5:30, Friday 3:00 - 5:00
<hr>
<h1><a name="time">Time And Place</a></h1>
<dl>
<dt><b>Time:</b></dt><dd>Tuesday, Thursday 2:00pm to 3:30pm</dd>
<dt><b>Place:</b></dt><dd><a
href="http://www.bu.edu/maps/?id=372">School of Theology Building</a> Room: <b>B19</b></dd>
</dl>
<hr>
<h1><a name="syllabus">Syllabus</a></h1>
<b>
You are required to submit a signed and
dated version of this syllabus to the TF in your first discussion
session indicating that you have read, understood and agree to its
contents.
</b>
You can obtain a copy of the syllabus from
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/syllabus.pdf">here</a>.
<h1><a name="schedule">Class Schedule</a></h1>
<h2>Special Dates </h2>
You should be sure to be familar with the
<a href="http://www.bu.edu/reg/dates/idates-fall12.html">Official
Semester Dates</a>
<p>Some of the critical Semester Dates are below:
<ul>
<li>
<b>Monday September 16, 2013: The Last Day to ADD Classes</b>
</li>
<li>
<b>Tuesday, October 7, 2013: The Last Day to DROP Classes (WITHOUT a
'W' grade)</b>
</li>
<li>
<b>Friday, November 8, 2013: The Last Day to DROP Classes (WITH a
'W' grade)</b>
</li>
</ul>
</p>
<h2><a name="byweek">Weekly Schedule</a></h2>
<p>
<table border="1" bordercolor="#000000"
style="background-color:#FFFFFF" width="100%" cellpadding="3" cellspacing="3">
<tr>
<td><h2>Week</h2></td>
<td><h2>Dates</h2></td>
<td><h2>Description</h2></td>
<td><h2>References</h2></td>
</tr>
<tr>
<td>1</td>
<td>Sept 3, 5</td>
<td>
TUES: CSPP-Ch1 -- Introduction<br>
THUR: CSPP-Ch2 -- 2.1
</td>
<td>
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/protected/discussion1.pdf">Reading for Monday's Discussion USER: 210
PW: 210210</a><br>
Research what SSH is and Putty.
</td>
</tr>
<tr>
<td>2</td>
<td>Sept 10, 12</td>
<td>
DISC: QUIZ 1 & Intro to UNIX <br>
TUES: CSPP-Ch2 -- 2.1<br>
THUR: CSPP-Ch2 -- 2.2<br>
<font color="green"><b>THUR: PA1 OUT</b></font><br>
</td>
<td>
</td>
</tr>
<tr>
<td>3</td>
<td>Sept 17, 19</td>
<td>
DISC: QUIZ 2 <br>
TUES: CSPP-Ch2 -- 2.2, <br>
THUR: CSPP-Ch2 -- 2.2<br>
</td>
<td>
</td>
</tr>
<tr>
<td>4</td>
<td>Sept 24, 26</td>
<td>
DISC: QUIZ 3<br>
TUES: CSPP-Ch2 -- 2.3<br>
THUR: CSPP-Ch2 -- 2.3, Intro to Floating Point<br>
<font color="blue"><b>TUES: PA1 IN</b></font><br>
</td>
<td>
Read Selected Portions for Discussion of <a
href="http://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html">What
Every Computer Scientist Should Know About
Floating-Point Arithmetic</a>
</td>
</tr>
<tr>
<td>5</td>
<td>Oct 1, 3</td>
<td>
DISC: REVIEW FOR MIDTERM 1<br>
TUES: MIDTERM<br>
THUR: CSPP-Ch3 -- 3.1-3.4<br>
</td>
<td>
</td>
</tr>
<tr>
<td>6</td>
<td>Oct 8, 10</td>
<td>
DISC: QUIZ 4<br>
TUES: CSPP-Ch3 -- 3.5-3.6<br>
THUR: CSPP-Ch3 -- 3.7<br>
</td>
<td>
</td>
</tr>
<tr>
<td>7</td>
<td>Oct 17</td>
<td>
<b>NO CLASS ON TUESDAY</B><BR>
TUES DISC: QUIZ 5<BR>
THUR: CSPP-CH3 -- 3.8-3.10<BR>
<font color="green"><b>TUES: PA2 OUT</b></font><br>
</TD>
<TD>
</TD>
</TR>
<TR>
<TD>8</TD>
<TD>OCT 22, 24</TD>
<TD>
DISC: QUIZ 6<BR>
TUES: CSPP-CH6<BR>
THUR: CSPP-CH6<BR>
<FONT COLOR="BLUE"><B>TUES: PA2 PART 1 IN</B></FONT><BR>
</TD>
<TD></TD>
</TR>
<TR>
<TD>9</TD>
<TD>OCT 29, 31</TD>
<TD>
DISC: QUIZ 7<BR>
TUES: CSPP-CH5<BR>
THUR: CSPP-CH5<BR>
<FONT COLOR="BLUE"><B>TUES: PA2 PART 2 IN</B></FONT><BR>
</TD>
<TD>
</TD>
</TR>
<TR>
<TD>10</TD>
<TD>NOV 5, 7</TD>
<TD>
DISC: MIDTERM 2 REVIEW<BR>
TUES: MIDTERM 2<BR>
THUR: CSPP-CH8<BR>
<FONT COLOR="GREEN"><B>TUE: PA3 OUT</B></FONT><BR>
</TD>
<TD>
</TD>
</TR>
<TR>
<TD>11</TD>
<TD>NOV 12, 14</TD>
<TD>
DISC: QUIZ 8<BR>
TUES: CSPP-CH8 <BR>
THUR: CSPP-CH8 <BR>
<FONT COLOR="BLUE"><B>TUE: PA3 PART 1 IN</B></FONT><BR>
</TD>
<TD>
</TD>
</TR>
<TR>
<TD>12</TD>
<TD>NOV 19, 21</TD>
<TD>
DISC: QUIZ 9<BR>
TUES: CSPP-CH9 <BR>
THUR: CSPP-CH9 <BR>
<FONT COLOR="BLUE"><B>THUR: PA3 PART 2 IN</B></FONT><BR>
<FONT COLOR="GREEN"><B>THUR: PA4 OUT</B></FONT><BR>
</TD>
<TD>
</TD>
</TR>
<TR>
<TD>13</TD>
<TD>NOV 26</TD>
<TD>
DISC: QUIZ 10<BR>
TUES: CSPP-CH9 <BR>
<B>NO CLASS THURSDAY</B>
<FONT COLOR="BLUE"><B>FRI: PA4 PART 1 IN</B></FONT><BR>
</TD>
<TD>
</TD>
</TR>
<TR>
<TD>14</TD>
<TD>DEC 3, 5</TD>
<TD>
DISC: QUIZ 11<BR>
TUES: CSPP-CH7<BR>
THUR: OTHER<BR>
</TD>
<TD></TD>
</TR>
<TR>
<TD>15</TD>
<TD>DEC 10</TD>
<TD>
DISC: REVIEW<br>
<b>TUESDAY IS LAST CLASS: REVIEW</b>
<FONT COLOR="BLUE"><B>TUE: PA4 PART 2 IN</B></FONT><BR>
</td>
<td>
</td>
</tr>
</table>
<h2><a name="exams">Tests/Exams</a></h2>
<table border="1" bordercolor="#000000"
style="background-color:#FFFFFF" width="100%" cellpadding="3" cellspacing="3">
<tr>
<td><h2>Name</h2></td>
<td><h2>Date</h2></td>
<td><h2>Solutions</h2></td>
</tr>
<tr>
<td>Midterm 1</td>
<td>Oct 1</td>
<td>TBP</td>
</tr>
<tr>
<td>Midterm 2</td>
<td>Nov 5</td>
<td>TBP</td>
</tr>
<tr>
<td>Final</td>
<td>Date</td>
<td> --- </td>
</tr>
</table>
<h2><a name="asched">Assignments</a></h2>
<p>
<table border="1" bordercolor="#000000"
style="background-color:#FFFFFF" width="100%" cellpadding="3" cellspacing="3">
<tr>
<td><h2>Name</h2></td>
<td><h2>Dates</h2></td>
<td><h2>Resources</h2></td>
<td><h2>Solutions</h2></td>
</tr>
<tr>
<tr>
<td><a name="pa1">PA 1: Data Lab</a></td>
<td>
OUT: Sept 12<br>
IN: Sept 24, 1:30pm
</td>
<td>
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/assignments/datalab.pdf">
handout
</a>
<td>
</td>
</tr>
<tr>
<td><a name="pa2">PA 2: Buffer Overflow Lab</a></td>
<td>
OUT: Oct 15<br>
PART 1 IN: Oct 22, 1:30pm<br>
PART 2 IN: Oct 29, 1:30pm
</td>
<td>
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/assignments/buflab.pdf">
handout
</a>
</a>
<td>---</td>
</tr>
<tr>
<td><a name="bonus">Bonus: Bomb Lab</a></td>
<td>
OUT: Oct 15
</td>
<td>
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/assignments/bomblab.pdf">
handout
</a>
</a>
<td>---</td>
</tr>
<tr>
<td><a name="pa3">PA 3: 6502 Lab</a></td>
<td>
OUT: Nov 5<br>
PART 1 IN: Nov 12, 1:30pm<br>
PART 2 IN: Nov 21, 1:30pm
</td>
<td>
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/assignments/6502lab.pdf">
handout
</a>,
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/assignments/6502.tar">
resources
</a>
<td>---</td>
</tr>
<tr>
<td><a name="pa4">PA 4: 6502 Devices, Interrupts, and
Context Switching Lab</a></td>
<td>
OUT: Nov 26<br>
PART 2 IN: Dec 10, 1:30pm
</td>
<td>
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/assignments/cswitch.pdf">
handout</a>,
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/assignments/cswitch.tar">
resource</a>
</td>
<td>---</td>
</tr>
</table>
<hr>
<h1><a name="esub">Assignments</a></h1>
<p>
You will be required to submit an electronic copy of your code, in
addition to both electronic and hard copies of supporting
documentation and any requested written report(s).
When
explicitly specified, you may have the
option to work in teams of two on large programming assignments.
<p>
<h3>General Requirements on What to Submit</h3>
<p>
Unless automated and otherwise specified, the program you submit
should work correctly and be documented. You should submit an
electronic copy of the following:
<p>
<b>1. Program:</b> a program listing containing in-line documentation (i.e.,
comments).
<p>
<b>2. Design document:</b> a separate file (a page or so) describing the overall
program design, a verbal description of "how it works", and design
tradeoffs considered and made. Also describe possible improvements and
extensions to your program (and sketch how they might be made).
<p>
<b>3. Testing document:</b> a separate file describing how to run your
program. Specify the steps that must be followed to successfully run
your program. Also, describe the tests you ran on your program to
convince yourself that it is indeed correct. Also describe any cases
for which your program is known not to work correctly.
<p>
It is fine to submit all the above documentation in one README file,
given you have clear subtitles. To save trees, you are required to
submit a hard copy only of the above supporting documentation and any
requested written report(s), but not of your program listing/code.
<h2>Additional Guidelines for Electronic Submission</h2>
[adapted from Prof. Matta's note that was adapted from D. Metcalf's
note]
<h3>How to submit an electronic copy: (Only plain ASCII files!)</h3>
To submit your programming assignments, use the <tt>gsubmit</tt>
program from your csa account.
<p>
<tt>gsubmit</tt> is an electronic file submission engine which will submit
files or directories of files to the grader so they can be marked.
<p>
Every file submitted by a given student for a given assignment should
have a unique file name. If a file is submitted with a duplicate name
it will either overwrite the file or generate an error message.
<p>
To make it easy for the grader to find the files relating to a
specific programming assignment, all files for each assignment should
be stored in a subdirectory called pa1, pa2, pa3, etc. and the entire
directory should be submitted.
<h3>To submit an assignment:</h3>
Create a subdirectory <tt>"pa#"</tt>, where <tt>#</tt> is the
programming assignment number. This is done using the mkdir command:
e.g.,
<pre>
mkdir pa5
</pre>
<p>
Copy all files necessary for that assignment into the new
subdirectory, using the cp command: e.g.,
<pre>
cp prog1.s pa5
</pre>
<p>
Be sure to copy only the files you need to submit into this subdirectory.
<p>
Use <tt>gsubmit</tt> to submit the entire subdirectory:
<pre>
gsubmit cs210 -cp pa5
</pre>
<p>
If submission is successful a status message will be printed.
<h3>To submit a file to an already-submitted subdirectory:</h3>
If you only submitted part of the assignment and would like to add
another file:
To submit a file README.txt to subdirectory pa5, type (at the prompt):
<pre>
gsubmit cs210 -cp README.txt pa5
</pre>
<h3>To resubmit a file:</h3>
To resubmit a file prog1.s in subdirectory pa5, first unsubmit the
file:
<pre>
gsubmit cs210 -rm pa5/prog1.s
</pre>
Then resubmit it:
<pre>
gsubmit cs210 -cp prog1.s pa5
</pre>
<h3>List all files which you have submitted:</h3>
To list all files which you have submitted, type:
<pre>
gsubmit cs210 -ls
</pre>
<h3>Looking at a file which has already been submitted:</h3>
To look at a file which has already been submitted, type:
<pre>
gsubmit cs210 -cat pa5/prog1.s
</pre>
You can store this in a file foo by typing:
<pre>
gsubmit cs210 -cat pa5/prog1.s > foo
</pre>
<h3>Where do submitted files go?</h3>
Each student who submits an assignment has a subdirectory created to
hold his/her files, in a directory for the specified course. This is
called the student's "submission spool directory".
<h3>How can the grader tell when a file has been submitted?</h3>
Every gsubmit command is automatically logged in a log file, along
with a time stamp.
<h3>For further information:</h3>
Note - The information in this document is taken from the gsubmit man page.
For further information type man gsubmit.
<hr>
<hr>
<h1><a name="oref">Online References</a></h1>
<h2>C/Unix</h2>
<ul>
<li><a href="http://csapp.cs.cmu.edu/public/unixfaq.html">Unix FAQ</a> (courtesy <a href="http://www.cs.cmu.edu/~bryant">Randal
E. Bryant</a> and <a href="http://www.cs.cmu.edu/~droh">David R. O'Hallaron</a> of CMU)</li>
<li><a href="http://heather.cs.ucdavis.edu/~matloff/unix.html">Norm
Matloff's Unix/C Tutorial Center</a></li>
</ul>
<h2>GNU/Unix Tools</h2>
The <a href="http://www.gnu.org/">GNU project</a> provides <a
href="http://www.gnu.org/manual/">online manuals</a> for all of the
GNU tools, including:
<ul>
<li><a href="http://projects.gnome.org/gedit/">gedit</a>(a simple graphical unix text editor)</li>
<li><a
href="http://en.wikipedia.org/wiki/Nano_(text_editor)">nano</a>
(a simple terminal based text editor). </li>
<li><a href="http://www.gnu.org/software/emacs">Emacs</a> (text
editor) (reference card for version 23 <a
href="http://www.damtp.cam.ac.uk/user/eglen/ess11/resources/emacs-refcard.pdf">ref
card</a>) </li>
<li><a href="http://gcc.gnu.org/onlinedocs/">GCC</a> (compiler driver) </li>
<li><a href="http://www.gnu.org/software/gdb">GDB</a> (debugger) </li>
<li><a href="http://www.gnu.org/software/make">Make</a> (program building utility) </li>
<li><a href="http://heather.cs.ucdavis.edu/~matloff/UnixAndC/CLanguage/Debug.html">Norm Matloff's GDB tutorial</a>
<li>Quick GDB reference ( <a
href="http://www.cs.bu.edu/~jappavoo/Resources/210/gdbnotes-ia32.pdf">ia32</a>,
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/gdbnotes-x86-64.pdf">x86-64</a>,
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/gdbnotes.txt">txt</a>
) </li>
</ul>
<h2>Other</h2>
<ul>
<li><a href="http://www.ima.umn.edu/~arnold/disasters/disasters.html">Some disasters due to bad numerical computations</a></li>
<li>Useful documentation on the Intel IA-32 architecture, Volumes
<a href="http://www.cs.bu.edu/~jappavoo/Resources/210/IA32_basic_architecture(24547007)-v1.pdf">1</a> , <a href="http://www.cs.bu.edu/~jappavoo/Resources/210/IA32_instruction_set_reference(24547107)-v2.pdf">2</a> and <a href="http://www.cs.bu.edu/~jappavoo/Resources/210/IA32_system_programming_guide(24547207)-v3.pdf">3</a>.</li>
</ul>
<hr>
<hr>
<h1><a name="honesty">Academic Honesty</a></h1>
<p>
Assignments must be completed individually. Discussion of issues in
computer systems is encouraged, but representing the work of another
person as your own is expressly forbidden. This includes "borrowing",
"stealing", copying programs/solutions or parts of them from
others. We may use an automated plagiarism checker. Cheating will not
be tolerated under any circumstances. Handing in your own work a day
or two late will affect your grade far less than turning in a copy of
someone else's work on time!
<p>
See the <a href="http://www.bu.edu/academics/resources/academic-conduct-code/">CAS
Academic Conduct Code</a>, in particular regarding plagiarism and
cheating on exams. Copies of the CAS Academic Conduct Code are also
available in room CAS 105. A student suspected to violate this code
will be reported to the Academic Conduct Committee, and if found
culpable, the student will receive a grade of "F" for the course.
<p> <b>
Any resources, including material from other students (current or
past), that are used,
beyond the text or that provided by the TF or professor must be
clearly acknowledged and attributed. Using such material may at the
discretion of the TF or professor result in a lower grade.
However, if such material is used and not acknowledged and attributed,
it will automatically be considered as possible academic misconduct.
</b>
<hr>
<!-- hhmts start -->Last modified: Tue Sep 3 12:44:45 EDT 2013 <!-- hhmts end -->
</body>
</html>