@www.csse.monash.edu.au |
| Assessment | Contacts | Laboratories | Lectures | Resources | Timetables | Tutorials | Unit Outline |
| Last modified: 20100803:122924/add submission instructions | FIT2022 AJH-2010-25 |
Assignment 1 Submission and Marking Strategy
(Also included in the Assignment Specification.)
Use the SVN server supplied to submit your assignment, with repository fit2022-your authcate ID. Make sure you include all relevant files (.py files, .pdf files, literate program files, etc.), and place them in a directory called Assignment1.
Your assignment will be retrieved from that repository for marking. If the file is not correctly named, it will not be retrieved, and hence you will not get any marks for the assignment!
NO WORD DOCUMENTS are to be submitted - if you want to use Word, please convert to a pdf file before submission (there are free convertors available, see for example http://www.doc2pdf.net/). If you submit Word documents, they will be ignored.
You can attempt this assignment at a variety of levels. The more challenging the level, the more marks you will receive. The following levels are recognized:
| Documentation | Max Marks |
|---|---|
| in-line comments | 13 |
| python documentation | 15 |
| literate program | 17 |
Transitions between these levels are possible (either upwards, as you complete a level, or downwards, if you find a level too hard).
You must document your code. Either with comments (base level), or with a documentation tool, or as a literate program. (Google for downloadable tools.) Note that using a literate program attracts possible bonus marks.
Write a short User Manual, which should explain all user features of your program. Don't make the mistake of describing how your program works! A good way of testing your manual is to get a friend to read through it, and see if they understand all the things you are trying to explain.
Marks breakdown:
| Attribute | Mark | percentage of Max Marks |
in-line | python | literate |
|---|---|---|---|---|---|
| mark scaling factor | 0.65 | 0.75 | 0.85 | ||
| code architecture (key algorithms, perspicacity of program, use of procedures/functions/libraries) | 5 | 25 | 3.25 | 3.75 | 4.25 |
| coding style (clarity, variable names, etc.) | 5 | 25 | 3.25 | 3.75 | 4.25 |
| documentation effort | 5 | 25 | 3.25 | 3.75 | 4.25 |
| user manual | 3 | 15 | 1.95 | 2.25 | 1.5 |
| working code | 2 | 10 | 1.3 | 1.5 | 1.7 |
What this means is that markers will mark according to the "Mark" column, and then scale the total mark by the scaling factor shown at the top of the table, to give the appropriate maximum mark.
| 20100803:122924 | 1.0.2 | ajh | add submission instructions |
| 20100803:121442 | 1.0.1 | ajh | add marks breakdown |
| 20100803:101252 | 1.0.0 | ajh | revised for 2010 |
| This page maintained by John Hurst. Copyright Monash University Copyright Policy |
|
![]() |
|
Generated at
20120430:1956
from an XML file modified on
20100803:1249 | |||