Programming for Data Analysis Marking Scheme Page 1 of 3

Name : TP : Mark:

Individual Assignment - Design, Documentation, and Implementation (80%):

Question No. Question Vs Taxonomy
Cognitive Level
Topic 1 2 3 4 5 6 PLO
SQ SQ SQ SQ SQ SQ
1 Report Format and System Documentation 37% 2
2 Implementation 63% 2
Total 100%

Individual Assignment - Presentation (20%):

Question No. Question Vs Taxonomy
Affective Level
Topic 1 2 3 4 5 PLO
SQ SQ SQ SQ SQ
1 Assignment Presentation 100% 5
Total 100%

Level 2 Asia Pacific University of Technology and Innovation 2020

Programming for Data Analysis Marking Scheme Page 1 of 3

Fail Marginal Fail Pass Credit Distinction

0-3 4 5-6 7 8 - 10

THE CODERUNNING
 No submitted code.  Analysis examples do  Analysis examples run  Analysis examples run  Analysis examples run
 Coding incomplete with not run due to some with no/minor errors. smoothly when smoothly when
obvious errors. errors. executed. executed.
 At least 1 additional  At least 2 additional
feature runs smoothly features run smoothly
when executed. when executed.

0 - 13 14 - 17 18 - 22 23 - 26 27 - 35
Coding
FEATURESADDITIONAL&EXAMPLESANALYSIS

 No submitted code.  No proper analysis  Seven analysis  Eleven analysis  At least fourteen
(50%)  Many wrong analysis examples covering data examples covering examples covering data analysis examples
examples were included. visualization, data visualization, visualization, covering data
[CLO2-PO2] exploration, and exploration, and exploration, and visualization,
manipulation topics were manipulation topics manipulation topics were exploration, and
included. were included. included. manipulation topics
 Incorporate basic  At least 1 additional were included.
concepts R concepts feature which can  At least 2 additional
and incomplete graph. improve the result which features which can
is apart from the course. improve the result
 Incorporate intermediate which is apart from the
concepts / knowledge in course.
R programming and  Incorporate advance
proper report generation. concepts / knowledge in
R programming and
excellent graph
creation.

0-1 2 3 4 5

Level 2 Asia Pacific University of Technology and Innovation 2020

Programming for Data Analysis Marking Scheme Page 1 of 3

PRACTICEGOOD PROGRAMMING
 No submitted code.  Poor coding style.  Basic coding style.  Adherence to good  Excellent adherence to
 Very poor coding style. Adherence to good Adherence to good programming practices good programming
Adherence to good programming practices programming practices like commenting, practices like
programming practices like commenting, like commenting, variable naming and commenting, variable
like commenting, variable naming and variable naming and indentation is between naming, and
variable naming and indentation is between indentation is between 65% - 80% only. indentation.
indentation is less than 40% - 50% only. 50% - 65% only.
40%.

/50

Fail Marginal Fail Pass Credit Distinction

0-4 5 6-7 8 9 - 12
CODESOF SOURCEPRINTOUT

 Documentation not done.  Major printout of source  Some evidence of  Most of the source  All source code
 No source code included. codes not included. the source code code printout printout included.
 No / poor / inaccurate  Insufficient explanation printout included. included.  Appropriate
explanation of source codes. of source codes.  Moderate  Some explanation explanation of
explanation of of source codes. source codes.
source codes.

Documentation
(30%)
[CLO2-PO2]
0-4 5 6-7 8 9 - 12

Level 2 Asia Pacific University of Technology and Innovation 2020

Programming for Data Analysis Marking Scheme Page 1 of 3

GRAPHSPROGRAM RESULTS’ SCREENSHOTS AND

 Documentation not done.  Major program results’  Some evidence of  Most of the  All program results’
 No program results’ screenshots and graphs program results’ program results’ screenshots and
screenshots and graphs not included. screenshots and screenshots and graphs included.
included.  Insufficient explanation graphs included. graphs included.  Appropriate
 No / poor / inaccurate of program results’  Moderate  Some explanation explanation of
explanation of program screenshots and graphs. explanation of of program results’ program results’
results’ screenshots and program results’ screenshots and screenshots and
graphs. screenshots and graphs. graphs.
graphs.  At least 1  At least 2 additional
 Additional features additional feature features were
were included was included with included with
without proper some explanation. appropriate
explanation. explanation.

0-1 2 3 4 5-6
    
STANDARDSATIONDOCUMENT

Documentation not done. Some missing / poor Overall average Good Excellent
 Mostly poor documentation documentation standards documentation documentation documentation
standards with missing such as table of contents, standards in table of standards in most standards. Overall
components such as table of referencing, page contents, areas such as table documentation has a
contents, referencing, page numbering, captioning, referencing, page of contents, professional
numbering, captioning, poor poor command of the numbering, referencing, page outlook.
command of the language, language. Referencing captioning, numbering,
etc. done does not adhere to command of the captioning,
Harvard’s Name language, etc. command of
Referencing style. language.

/30

Presentation Fail Marginal Fail Pass Credit Distinction

Level 2 Asia Pacific University of Technology and Innovation 2020
Programming for Data Analysis Marking Scheme Page 1 of 3

(20%) 0-7 8-9 10-12 13-14 15-20

[CLO3-PO5]  Not able to answer any  Not able to answer most  Able to answer some  Able to answer most  Able to answer all
question posed. questions indicating questions indicating questions well questions posed
 Not able to explain the poor understanding of some understanding of indicating some clear accurately indicating
code. the work done. the work done. understanding of the clear understanding of

 No understanding or  Not able to explain nor  Able to explain but not work done. the work done.

idea of R programming modify code upon able to modify code  Able to explain and  Able to explain and
concepts. request. upon request. modify some code upon modify code upon
 Has hardly any  Hardly able to explain R request. request.
understanding or idea of concepts.  Able to explain the  Able to explain all the
R programming implementation code implementation code
concepts. and graphs incorporated. and graphs incorporated.

Level 2 Asia Pacific University of Technology and Innovation 2020