ITGS IA Grader
This page is designed to help you understand the assessment criteria for the Information Technology in a Global Society (ITGS) Internal Assessment (IA). By breaking down the rubric, providing annotated examples, and offering a free embedded grader, you can efficiently self-evaluate your work and identify areas for improvement.
Quick Start Checklist
Before using the grader, ensure you have the following:
- Complete IA Report: Your final draft, including all sections.
- Word Count: Verify adherence to the prescribed limit.
- Supporting Materials: Include data tables, screenshots, and any other relevant appendices.
- Citations: Ensure all sources are properly referenced.
- Client Feedback: Documented responses from your client regarding the product.
- Reflection Notes: Your personal evaluation of the project and its development process.
Rubric Breakdown (Paraphrased & Plain English)
Understanding the assessment criteria is crucial for maximizing your IA score. Below is a breakdown of each criterion:
Criterion A: Planning (6 marks)
What it tests: Your ability to identify a real-world problem and plan an appropriate IT solution.
High Performance: Clearly define the problem, justify the need for a solution, and outline detailed success criteria.
Common Mistakes: Vague problem statements, lack of justification, or insufficient success criteria.
| Mark Band | What it means | Evidence you must show |
|---|---|---|
| 0 | Work does not meet the standard. | No clear problem identification or planning. |
| 1–2 | Basic problem identification with minimal planning. | Brief problem statement with limited success criteria. |
| 3–4 | Adequate problem identification and planning. | Clear problem statement with some justification and success criteria. |
| 5–6 | Comprehensive problem identification and detailed planning. | Thorough problem statement, strong justification, and detailed success criteria. |
Criterion B: Solution Overview (6 marks)
What it tests: Your ability to design a solution and plan its development.
High Performance: Provide detailed design diagrams, a comprehensive testing plan, and a structured development approach.
Common Mistakes: Lack of detailed designs, inadequate testing plans, or unstructured development processes.
| Mark Band | What it means | Evidence you must show |
|---|---|---|
| 0 | Work does not meet the standard. | No clear design or development plan. |
| 1–2 | Basic design with minimal development planning. | Simple design diagrams and a brief development plan. |
| 3–4 | Adequate design and development planning. | Clear design diagrams with a structured development plan. |
| 5–6 | Comprehensive design and detailed development planning. | Detailed design diagrams, thorough testing plan, and a well-structured development approach. |
Criterion C: Development (6 marks)
What it tests: Your ability to implement the planned solution effectively.
High Performance: Demonstrate advanced techniques, provide evidence of development stages, and justify your choices.
Common Mistakes: Lack of complexity, insufficient evidence of development, or failure to justify decisions.
| Mark Band | What it means | Evidence you must show |
|---|---|---|
| 0 | Work does not meet the standard. | No evidence of development. |
| 1–2 | Basic development with minimal complexity. | Simple product with limited techniques. |
| 3–4 | Adequate development with some complexity. | Product with moderate techniques and some justification. |
| 5–6 | Comprehensive development with high complexity. | Complex product with advanced techniques and thorough justification. |
Criterion D: Functionality (4 marks)
What it tests: The effectiveness and functionality of your final product.
High Performance: Product meets all success criteria, functions without errors, and is user-friendly.
Common Mistakes: Product does not fully meet success criteria, contains errors, or lacks usability.
| Mark Band | What it means | Evidence you must show |
|---|---|---|
| 0 | Work does not meet the standard. | Non-functional product. |
| 1–2 | Partially functional product with some success criteria met. | Product with limited functionality and some errors. |
| 3–4 | Fully functional product meeting all success criteria. | Product operates as intended without errors and is user-friendly. |
Criterion E: Evaluation (4 marks)
What it tests: Your ability to evaluate the product and reflect on its development.
High Performance: Comprehensive evaluation against success criteria, client feedback, and thoughtful reflection on future improvements.
Common Mistakes: Superficial evaluation, lack of client feedback, or no consideration for future development.
| Mark Band | What it means | Evidence you must show |
|---|---|---|
| 0 | Work does not meet the standard. | No evaluation or reflection. |
| 1–2 | Basic evaluation with minimal reflection. | Limited evaluation against success criteria and brief client feedback. |
| 3–4 | Comprehensive evaluation with detailed reflection. | Thorough evaluation against success criteria, detailed client feedback, and thoughtful future recommendations. |
Criterion F: Required Elements (4 marks)
What it tests: Inclusion of all necessary components as specified by the IB.
High Performance: All required elements are present, correctly formatted, and contribute to the overall quality of the IA.
Common Mistakes: Missing elements, incorrect formatting, or elements that do not add value.
| Mark Band | What it means | Evidence you must show |
|---|---|---|
| 0 | Work does not meet the standard. | Missing multiple required elements. |
| 1–2 | Some required elements present with errors. | Inclusion of some elements but with formatting issues or lack of completeness. |
| 3–4 | All required elements present and correctly formatted. | Complete inclusion of all elements with correct formatting and contribution to the IA's quality. |
How to Interpret Your Grade from the Tool
The embedded grader provides a score for each criterion, which maps to the mark bands outlined above. Here's how to interpret your results:
- Between Bands: If your score falls between two bands, focus on the descriptors of the higher band to identify areas for improvement.
- Uncertainty: If you're unsure about a score, review the evidence required for each mark band and assess whether your work meets those standards.
Improvement Actions:
- Criterion A: Ensure your problem statement is clear, justified, and supported by detailed success criteria.
- Criterion B: Develop comprehensive design diagrams and a structured development plan.
- Criterion C: Implement advanced techniques and provide thorough documentation of your development process.
- Criterion D: Test your product rigorously to ensure it meets all success criteria without errors.
- Criterion E: Conduct a detailed evaluation against success criteria, gather client feedback, and propose thoughtful future improvements.
- Criterion F: Verify that all required elements are included and correctly formatted.
Annotated Examples
High-Band Excerpt:
"The problem identified was the client's difficulty in managing inventory efficiently. The proposed solution is a database-driven application that tracks stock levels in real-time. Success criteria include real-time updates, user-friendly interface, and detailed reporting features."
Why it scores high: The problem is clearly defined, justified, and supported by specific success criteria.
Mid/Low-Band Excerpt:
"The client needs a new system to manage inventory."
What's missing: Lacks detail, justification, and specific success criteria.
Grade Boundaries & Converting Your Mark
Grade boundaries can vary by session. Below is an example of how marks might convert to grades:
| Total Marks | Grade |
|---|---|
| 27–30 | 7 |
| 23–26 | 6 |
| 19–22 | 5 |
| 15–18 | 4 |
| 10–14 | 3 |
| 5–9 | 2 |
| 0–4 | 1 |
Please verify the latest grade boundaries with your instructor or the IB coordinator.
The IA contributes to your overall ITGS grade, which is combined with external assessments to determine your final score.
Common Mistakes & Fast Fixes
- Vague Problem Statements → Clearly define and justify the problem.
- Insufficient Planning → Develop detailed design diagrams and a structured development plan.
- Lack of Complexity →
