Question 1

What is NCEA AS 91637 about?

Accepted Answer

You need to build a working computer program that solves a real problem or task. The program must use proper programming structure (with modules, data storage, and user-friendly buttons/windows), handle what the user does with it, and prove that it actually works. You'll be marked on how well you design it, how clearly you write and explain your code, and how thoroughly you test it.

Question 2

What do students need to do for AS 91637?

Accepted Answer

1. Design and build a program with modules (separate chunks of code), variables, and a list or array to store data 2. Create a graphical user interface (buttons, text boxes, windows) that responds when the user clicks or types 3. Use classes and objects to organize your code properly 4. Test your program with different types of input to prove it works correctly 5. Write clear comments and variable names so someone else can understand what your code does

Question 3

What's the difference between Achieved, Merit, and Excellence for AS 91637?

Accepted Answer

Achieved: You develop a complete working program with the required structure, GUI, and testing, with code that is reasonably clear and commented. Merit: You design and build your program carefully with well-documented variable and module names, test it thoroughly on both normal and edge-case inputs, and show your development process step-by-step. Excellence: Your program design is logically organized and efficient, your code is robust and flexible, you test comprehensively (including invalid inputs), and you use variables and constants smartly to make the program work well in different situations.

Question 4

What mistakes do students typically make in AS 91637?

Accepted Answer

1. Not testing the program thoroughly—especially failing to test edge cases (like empty inputs, very large numbers, or boundary values) or invalid inputs that break the program 2. Poor code organization and documentation—vague variable names, missing comments, or unclear module structure that makes it hard to follow what the code does 3. Incomplete or weak GUI design—buttons and windows that don't respond properly to user actions, or missing event handling for user interactions

Complex programming · AS 91637

Documents (9)

The standard itself

Bundles

Related standards

More in this subject

Other Technology - Digital Technologies and Hangarau Matihiko standards · Level 3 · Year 13

Foundations — Technology - Digital Technologies and Hangarau Matihiko Level 2 · Year 12