OENG1206 – Digital Fundamentals Practical
Assessment Guidelines

General Submission Guidelines:

• How to Submit: Practical tasks must be submitted electronically to Canvas (via the
Assignments link) prior to 11:59pm on the Friday after completing the task in class.
• Practical reports MUST be submitted in either Word (.doc or .docx) or portable
document format (.pdf). Due to compatibility issues reports in all other formats
including but not limited to Open Office format (.odt) and Mac OS format (.pages)
WILL NOT BE ACCEPTED!
• MATLAB file submission: All MATLAB solutions must be submitted along with your
report. These must be uploaded in .m file format only. Code that has been copied and
pasted or screenshot into a document will not be accepted.
• Practicals must be submitted on time. A late penalty of 10 marks deduction will be
applied per day late (inclusive of weekends and public holidays).
• Practicals are group tasks. Groups must consist of no more than 3 students and all
group members must contribute equally to the work submitted.
• Please notify your prac tutor and the course coordinator in a timely manner if there
are issues with group members not contributing so alternative assessment
arrangements can be organised.
• You MUST attend the class you are enrolled in officially via MyTimetable, failing to do
so may result in a zero grade for your pracs.
• Copying from other students or from any source without referencing is called
plagiarism and will result in all students involved being referred to the STEM College
Student Conduct group.







Report Format:

Your practical reports should be in the following form:

Page 1: Cover Page (example):

RMIT University
School of Engineering
OENG1206 – Digital Fundamentals
Practical Task 1
Introduction to MATLAB
Lecturer: Dr. Katrina Neville
Practical tutor: ………
Student Names: …….. Student Numbers: ………
Group: e.g. PRA01/01 - Monday 9:30-11:30 Submission Due Date: …….


Page 2: Statement of Contribution (example):
Student Name Student Number Contributions
John Smith 1234567 Problem Statement, Input/output descriptions,
MATLAB code (Tasks 1 & 3)
Jane Elliott 2468012 MATLAB code (Tasks 2 & 4), Flow-chart, testing
table
Carol James 3212345 MATLAB code (Tasks 5 & 6),
discussion/evaluation of output


Pages 3 - 6:

1. Problem-solving steps used (Based on the problem-solving methodology from
lectures): (50 marks)
a. State the problem: Describe the problem you are setting out to solve, give
details on the nature of the problem and the client’s specifications.
b. Specify the input data: What known information do you have from the
problem description? What other input may be required? How is that
information being obtained? In what format (text, integer, file)?
c. Specify the output data: What do you need to output to solve the problem?
How should it be output? In what format (graph, text, file)?
d. Design algorithm(s): include block diagrams, flow charts, etc to show the way
your algorithm(s) operate. Also, evaluate your algorithms’ viability by showing
its operation with a small set of data for this part.

Pages 7 - 10:

2. Software solution and testing: (50 marks)
a. Testing: Present evidence in your report of your testing regime to show your
software solution generates accurate and consistent outputs for a range of
reasonable input data values. This may include a comparison between your
program’s actual output and what you expected in part 1d.
b. Evaluation: Include a selection of graphs (or other output) from your MATLAB
solution and thoroughly explain how these demonstrate your solution solves
the problem you needed to solve. Describe the strengths and weaknesses of
your solution and how you could improve it in future.
c. Include your MATLAB script(s) (.m file(s)) in your submission to Canvas so your
tutor can check your solution works as described in your documentation.


Other considerations when writing your reports:

References: If you have used external references to help you with theoretical
background you MUST also include these at the end of your report.
a. References must be in IEEE format (see the RMIT library website for details
on this referencing style:
https://www.rmit.edu.au/library/study/referencing/referencing-guides-for-
printing ).
b. References can include sources such as: textbooks, websites, patents,
standards and journal/conference papers.

Presentation and language: Make sure you present your report in a readable and
logical format.
a. The practical report should be written in English.
b. The report should be typed not handwritten. A sensible font and font size
should be used (e.g. Calibri or Arial at 12 points, 1.5 line spacing)
c. All pages should be numbered.
d. Graphs and tables should also be numbered and given appropriate titles.
e. Report sections should also be given appropriate headings.
f. Make sure your names and student numbers are visible on ALL pages.












Assessment Rubric for Digital Fundamentals Practicals

0-49 Fail
NN
50-59 Pass
PA
60-69 Credit
CR
70-79 Distinction
DI
80-100 High
Distinction
HD
Problem Solving
Methodology/
Algorithm Design
(50%)
Students have
presented little to no
evidence of the
problem-solving
steps taken to
produce a solution or
the problem-solving
steps contained
serious fundamental
flaws.
Most of the problem-
solving methodology
has been addressed
in a generally
superficial way.
Students’
understanding of the
problem may not be
clear.
Problem-solving
methodology has
been presented but
may be lacking some
details.
Problem statement
may not be clearly
stated.
Problem-solving
methodology is
adequate and backed
up by evidence.
Problem statement
shows a good
understanding of the
nature of the
problem.
A thorough plan has
been presented with
excellent use of
evidence to back up
chosen software/
algorithm design.
Excellent
understanding of the
nature of the
problem.
Solution, Testing and
Discussion (50%)
No solution output
presented in report,
or the solution has
serious, fundamental
flaws.
No evidence of
testing presented in
report.
MATLAB solution
submitted and
documentation in
report do not match
or do not fulfil the
specific requirements
outlined in the
specifications for the
task.
Solution output has
been presented in
report but there is
little to no evidence
of testing.
MATLAB solution
submitted and
documentation in
report may have
some inconsistencies
or contain some
errors but somewhat
fulfils the
requirements of the
task.
An adequate
presentation of
solution output in
report with some
evidence of testing
having been
performed with a
very limited set of
inputs.
MATLAB solution
submitted and
documentation in
report mostly match
and mostly fulfils the
requirements.
A good presentation
of solution output in
report with evidence
of testing with a
variety of inputs.
Minimum
requirements have
been implemented
and presented in
report to fulfil
specifications (no
extra functionality
present).
MATLAB solution
submitted and
documentation in
report match and
fulfils requirements.
Excellent
presentation of
solution output in
report with evidence
of a wide range of
testing with relevant
input data.
Extra functionality
may have been
implemented where
appropriate.
MATLAB solution
submitted and
documentation in
report fulfils all
requirements to an
excellent standard.