PLEASE NOTE: the upgrades to this server, secure.csse.uwa.edu.au, have not yet been completed.
Hopefully the changes will be completed on THURSDAY 8th December.
Web-based programs, such as csmarks, cssubmit, and the help fora, will be unavailable at some time on Thursday 8th.
  It's UWAweek 49

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

Displaying selected article
Showing 1 of 919 articles.
Currently 5 other people reading this forum.


 UWA week 37 (2nd semester, week 7) ↓
SVG not supported

Login to reply

👍?
helpful
5:37am Thu 15th Sep, Christopher M.

ANONYMOUS wrote:
> I was wondering if there was a marking rubric released for this project? I am aware of the 25 marks for correctness and 25 for programming style, however is there a further breakdown of the 25 marks within each of these sections?
The description of the marking emphasis and marks breakdown meets the requirements of the Assessment Policy and has been approved; it just may look different to how rubrics are presented in other units. There are many, many, examples of acceptable programming style in lecture notes, and sample solutions for weekly labsheets and workshops. Adopting those, or similar consistent practices, should award you full marks for your style. The emphasis for programming correctness should be clear from our (recorded) Friday workshops. Clearly important are checking of command-line arguments, checking the success of file-based operations, checking the validity of file contents, reporting errors and terminating correctly, and the correctness of the 3 'words' on the final line of your output. The sample solution enables you to verify your results for any crontab- and estimate- files you design, and it's debugging/reporting output gives a big hint about (one possible) approach.
> In particular, I was wondering about the mark allocation for each of the three desired output values, as well as what would happen if the program ran for certain crontabs and estimates values but not for others?
Your project will be tested against many (maybe 8-10) pairs of crontab- and estimate- files, that each try to test something different. Hopefully your project will pass all of them, but it's feasible for your project to pass some, but not others. I hope that this helps (but, politely, I have hoped that this was all very clear from the way the unit has been running this year.)

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  1:17AM Sep 14 2022
Privacy policy