The University of Sydney Page 1
ENGG1810/9810
Assignment Briefing
Sue Inn Chng
The University of Sydney Page 2
Assignment Details
– Contributes 20% of your final marks
– Due date: 11:59PM Friday 28 May April 2021 (local Sydney time)
– To make a submission, you need to press the “Mark” button.
– Multiple submissions allowed before the due date. Only the last submission will be graded.
– Late penalty: 25% per day
– 1 day late: Max 75%
– 2 days late: Max 50%
– 3 days late: Max 25%
– 4 days late: 0%.
The University of Sydney Page 3
What should I do now?
1. Read the assignment brief.
– Watch: https://www.youtube.com/watch?v=nK4oDD-4CeE
– Understand requirements and tasks.
– Lost?
• Read: How do I begin?
• Backtrack to relevant section to understand requirements.
2. Do the assignment.
– Act with academic integrity.
• Do NOT share your solution/approach/implementation with others.
• Do NOT ask Relatives/Hired Coders/Students outside unit/online
forums/online tutors to do the Assignment.
– Teaching team can only help clarify questions and explain general
concepts through relevant teaching materials and NOT on assignment
materials.
The University of Sydney Page 4
What should I submit?
– Read Section:
– Code Submission
– Marking Criteria
– All Python files of your work + README.md file.
The University of Sydney Page 5
README.md File
– Add your answer to both questions (see Section:
Marking Criteria) here.
– Maximum word count – 1000 words.
– Write concisely.
– What is a markdown file?
– https://www.markdowntutorial.com/
The University of Sydney Page 6
How will I be graded?
– Automatic tests: 15%
– Marked by a computer to make sure codes follows requirements.
– Any attempts to deceive or disrupt the marking system will result in an
immediate zero for the entire assignment.
– Negative marks can be assigned if you do not properly follow the
assignment description, or your code is unnecessarily or deliberately
obfuscated.
– Manual grading: 5%
– Code readability – 2.5%
– Explanation of work – 1.5%
– Testing – 1%
The University of Sydney Page 7
Code Readability
– Recommendation: https://www.python.org/dev/peps/pep-0008/
– Factors that affect code readability:
– Poor naming of variables e.g. does not match represented value, non-
descriptive names.
– Additional white spaces where there shouldn’t be:
• before open parenthesis that starts argument list of a function call e.g.
math.sqrt (2)
• before open bracket that starts an index or slice e.g. ls [1]
• inside brackets/parenthesis e.g. ls [ 1 ]
– Comments that differ from codes/line length exceeds 72 characters.
– Additional line breaks that separates codes that should be in the same block.
– Examiners will manually read your codes to check its implementation
for all files.
The University of Sydney Page 8
Explanation of Work
– High-level view of your work towards the purpose of the
software.
– Must explain relevance of each file with respect to running the
simulation.
– You may include an image to aid your explanation (if it helps):
• https://www.markdowntutorial.com/lesson/4/
– Choose a simulation (from the examples given or your own) to aid your
explanation.
– More words does not mean more marks. Penalties may apply
to submissions that exceed the word limit.
The University of Sydney Page 9
Testing
– Explanation and justification of your actions when you prepare
your solution.
– Plan your response:
– What did you do and why?
– When did you carry out the test and why?
– Which testing ‘tools’ did you use and why? (refer to Lecture 9 - Testing)
– Your testing files and logs must be included in your submission
with clear instructions on its usage.































































































学霸联盟