Skills Demonstration #1 – 20%:

This assignment is graded out of 100 marks and weighted to be worth 20% of the module.  The main learning outcome refers to the learner being able to demonstrate an understanding of the different data types used in object oriented programs.

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 a simple algorithm based on the problem statement

• make simple coding inferences from the problem statement in order to identify all appropriate data types required

• code and test an object oriented program that provides a solution to the problem statement that:

  • contains a single class

  • features appropriate data types to simulate and/or model the problem

  • uses logical program blocks

  • correctly performs type conversions

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 20%.  The marking is generally broken down as follows:

Clearly Documented Source Code (20%)

• algorithm (class diagram) provided

• code documentation (docstrings)

Program Functionality (20%)

• working program: runs without error

• data validation and formatting

Accurate Programming (Syntax and Semantics) (40%)

• appropriately named identifiers (class, method, fields/variables )

• correctly implemented data types

• appropriate data type conversion performed

• correct implementation of mthods of the class

Software Testing/Debugging (20%)

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

• screen captures, visual/digital evidence provided