
Finalise Your CBA
Review and finalise your Classroom-Based Assessment (CBA) portfolio before the final submission deadline.
TL;DR:The final stage of the 3rd Year Coding course is the completion of the Classroom-Based Assessment (CBA). This topic focuses on finalizing the portfolio, ensuring all learning outcomes are evidenced, and reflecting on the journey from problem to solution. This aligns with NCCA Learning Outcomes 3.5 and 3.6, which emphasize communication and reflection.
About This Topic
The final stage of the 3rd Year Coding course is the completion of the Classroom-Based Assessment (CBA). This topic focuses on finalizing the portfolio, ensuring all learning outcomes are evidenced, and reflecting on the journey from problem to solution. This aligns with NCCA Learning Outcomes 3.5 and 3.6, which emphasize communication and reflection.
Students must be able to explain not just what they built, but why it matters and how it connects to the history of computing. This is a time for synthesis and pride. This topic benefits from peer-review sessions and 'mock presentations' where students practice articulating the social value of their code, helping them feel confident before their final submission.
Key Questions
- How does our software address the original social problem?
- What historical technological advancements made this project possible?
- How can we effectively communicate the social value of our code?
Watch Out for These Misconceptions
Common MisconceptionThe CBA is only about the final code working perfectly.
What to Teach Instead
Clarify that the NCCA assessment values the *process* and *reflection* as much as the product. Use a sample portfolio to show how documenting mistakes and changes can actually lead to a better grade.
Common MisconceptionI don't need to explain the history or ethics in my final report.
What to Teach Instead
Remind students that the Coding Short Course is about 'Computing and Society.' Use a checklist to ensure they have linked their project back to the pioneers and ethical issues they studied in earlier units.
Active Learning Ideas
See all activities→Peer Teaching
The CBA Pitch
Students have three minutes to 'pitch' their project to a small group, explaining the problem, their solution, and the social impact. Peers provide feedback on how clearly the student communicated their ideas.
Gallery Walk
Portfolio Showcase
Students display their final code and reflections on their screens. The class moves around, leaving 'positive praise' and 'thoughtful questions' on cards for each project to celebrate their hard work.
Think-Pair-Share
The Reflection Loop
Students look back at their very first code from 1st Year. They discuss with a partner how their skills and their understanding of technology's role in society have changed over the three years.
Frequently Asked Questions
What should be included in my final CBA portfolio?
How do I explain the 'social value' of my code?
How can active learning help students finalize their CBA?
What happens after I submit my CBA?
More in Developing Software for Societal Impact
Prototyping an App for the Community
Begin the development of a software project designed to address a specific social need. Focus on user interface design, historical context of the problem, and accessibility for diverse populations.
8 methodologies
Iterative Development and User Feedback
Write and test code for the community app, incorporating feedback from potential users. Reflect on how user-centered design improves the social utility of technology.
8 methodologies