Homework.1.cs561.fall.2010 - 1 CSCS-561 Homework 1 Due...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
CSCS-561 Homework 1 Due: Before class Wednesday, September 22, 2010 Guidelines: This assignment has a written and programming component. You can see how much each part of the assignment is worth by the percentage next to it. For the written part, please turn in typewritten answers. You are not English majors, however blatant spelling and grammatical errors may cost you points, so be sure and run the spell check at least once. Answers on the written part will require justification and a simple yes/no answer will almost certainly garner you little or no points. In general, it is safer to write longer answers than shorter ones, but stay focused as a long but off-topic answer will not work either. This way, we can discern your train of thoughts better and grant partial credit for a wrong answer, if you were on the right track. The written portion should in some way be computer published . This means that graphs are produced with programs such as Adobe Illustrator or Microsoft Power Point and answers are typed. Thus, ideally you should produce a document in Latex, Word or even Quark XPress if that’s your flavor. Really snappy looking graphs and homework hand-ins can sometimes get extra credit. What publishing software packages you use is totally up to you. This is a good opportunity to acquaint yourself with tools that will be extremely helpful in your future professional and academic career. For the programming part, you will be provided sample inputs and at least one sample output. Since each homework is checked via an automated Perl script , your output should match the example format exactly . Failure to do so will most certainly cost some points. Since the output format is simple and there is an example on the web, this should not be a problem. Additionally, if your code generates a large number of warnings during compilation, you will lose points, so try and eliminate compile-time warnings. Additionally, your code should be well documented. If something goes wrong during compile and grading, if the fix proves easy, the amount of points lost will be far less. As such, documentation makes fixing easier, so it is to your advantage to do so. You will be provided with a stub Perl script called “stubby.pl”, which works like the grading Perl script. You can run this script to make sure that your project will work properly. Thus, it is expected that your project will run through the grading Perl script without problems. Pedantically, we assert it will cost you points if your code does not run on the Perl script correctly. You will be able to tell if your output is correct if stubby shows each of the lines from your program output is exactly the same as from the comparison file which shows what output you should be getting. To run stubby, copy it to your code directory along with the input, output and comparison files.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 9

Homework.1.cs561.fall.2010 - 1 CSCS-561 Homework 1 Due...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online