Skills Demonstration #3 – 30%:

This assignment is graded out of 100 marks and weighted to be worth 30% of the module.  The main learning outcomes are:

• Construct larger programs from smaller programs

• Properly document program code

• Debug and test programs

• Deploy programs to the end user via the front-end

and these support a module objective which is to "demonstrate an ability to access purpose-built class libraries /API packages and basic Collection classes (as and if appropriate) and incorporate them into user defined classes".  The specific library/package that this assesment makes use of is usually pygame or arcade- python packages used to create 2D games.

This assessment allows the user to design a custom class and implement a range of dunder (magic) methods using various data types to create a new model.  The learner will design, code and test an object oriented program. It is envisaged the assessor will design a skills demonstration to test the learner’s competence and ability in learning outcome 1. The learner will be presented with a suitable problem statement with clear guidelines/instructions as to what is to be done and what is being assessed. 

Specifically, the skills demonstration should test the learner’s ability to:

• devise and document an algorithm based on the problem statement 

• make correct coding inferences from the problem statement to identify appropriate  fields/variables, objects, control/repetition statements, data sequences, etc, as required

• utilise an integrated development environment (IDE) to code and test an object oriented program that provides a solution to the problem statement that:

  • contains a class object that is based on another class (inheritence)

  • makes use of separate class libraries or packages (pygame in this instance, with other optional modules)

  • features appropriate data types to simulate and/or model the problem  (a game)

  • using modularised and logical program blocks (classes in files- re-usable and modular)

  • contains a number of appropriately named methods/functions

  • correctly implements control structures (loops)

  • uses repetition statements appropriately  (conditional execution)

  • contains meaningful documentation

The learner will produce:

• a working program (soft and hard copy)

• appropriate program documentation to include an algorithm, relevant screen captures, digital/visual evidence of the development cycle (including evidence of debugging/testing, etc) and indicative critical reasoning

The assessment is marked out of 100 and weighted to 30%.  The marking is generally broken down as follows:

Clearly Documented Source Code (10%)

• algorithm (class diagram) provided

• code documentation (docstrings)

Program Functionality (10%)

• working program: runs without error

• appropriate front-end: GUI aesthetics: title, screen ratio, layout, presentation

• repr methods implemented for development testing and verification

Accurate Programming (Syntax and Semantics) (66.5%)

• source code generated within IDE

• correctly accessed packages/library classes (as appropriate)

• appropriately named base class(es)

• appropriately named identifiers (fields/variables)

• appropriately named methods/functions

• appropriate use of methods, e.g., correct method calls, return values

• working selection statements, e.g., if-else, switch  

• working control structures, e.g., while, do-while, for loops

• correctly implemented data structure(s)

• no syntax or semantic errors

Software Testing/Debugging (13.5%)

• evidence of software testing, e.g., documentation of problems/bugs

• take a TDD approach

• screen captures, visual/digital evidence provided

• create a video demonstration