
Completing your Computer Science Internal Assessment (IA) is a straightforward process if you are well-prepared and follow the structured computational thinking process. For the 2027 guide, the IA task is officially called the computational solution. This project requires you to identify a problem of your choice and develop a coded software product to solve it.
At the starting point, you must clearly define the problem you intend to solve. The recommended length for this section is 300 words.
Problem Scenario: Provide a clear description of the problem, whether it relates to a real-world situation, another field of knowledge, or a current issue in computing.
Solution Requirements: Describe the problem in terms of measurable requirements - what must the solution actually do?
Success Criteria: State appropriate, measurable outcomes that will be used to determine if the product is successfully developed.
Computational Context: Explain your choice of the specific area of computing (e.g., mobile app, database-driven web app) that you will use for the solution.
This criterion assesses your ability to break down your project into manageable tasks. The recommended length is 150 words.
Decomposition: Construct a reasonable decomposition of your problem scenario into smaller sub-problems or components, effectively using diagrams.
Chronology: Include a proposed timeline for the steps involved in planning, designing, developing, testing, and evaluating your solution.
Addressing Requirements: Ensure your plan directly addresses all success criteria identified in Criterion A.
In this section, you should provide a technical overview that would allow a third party to recreate your product. The recommended length is 150 words.
System Model: Construct a complete model using diagrams that show all system components, their connections, and the user interface design.
Algorithms: Construct algorithms for your system components using natural language, flowcharts, or pseudocode.
Testing Strategy: Describe a systematic approach to evaluating your solution, often presented as a table with proposed test data and expected outcomes aligned with your success criteria.
This is the core of your documentation, where you justify your technical choices and demonstrate your coding skills. The recommended length is 1000 words.
Technique Justification: Evaluate the choices you made to implement your algorithms, such as specific loops, data structures, or the integration of software tools.
Code Documentation: Include key excerpts of your code that are essential to the functioning of your algorithms. Ensure the code is readable, consistent, and contains relevant comments.
Testing Evaluation: Justify the effectiveness of your testing strategy, ensuring it covers the correctness, reliability, and efficiency of your product.
You must submit a separate video file (e.g., MP4) as evidence of your work.
Functionality: The video must demonstrate the full functionality of your completed software product.
Testing in Action: You must show specific examples of your testing strategy being deployed to prove the software works as intended.
In the final section, you look back at your initial goals. The recommended length is 400 words.
Success Criteria Assessment: Evaluate the extent to which the final product met each success criterion from Criterion A.
Improvements and Extensions: Justify specific product improvements or potential extensions, explaining how they would enhance the solution.
We hope this guide helps guide you in properly formatting and structuring your computer science IA! If you want to read some exemplary IAs before you start writing, we've got you covered! Simply head to the Clastify website, where you will be able to find numerous computer science IA ideas and examples, so you can look for the ones that are the most relevant to your topic. Good luck!
Completing your Computer Science Internal Assessment (IA) is a straightforward process if you are well-prepared and follow the structured computational thinking process. For the 2027 guide, the IA task is officially called the computational solution. This project requires you to identify a problem of your choice and develop a coded software product to solve it.
At the starting point, you must clearly define the problem you intend to solve. The recommended length for this section is 300 words.
Problem Scenario: Provide a clear description of the problem, whether it relates to a real-world situation, another field of knowledge, or a current issue in computing.
Solution Requirements: Describe the problem in terms of measurable requirements - what must the solution actually do?
Success Criteria: State appropriate, measurable outcomes that will be used to determine if the product is successfully developed.
Computational Context: Explain your choice of the specific area of computing (e.g., mobile app, database-driven web app) that you will use for the solution.
This criterion assesses your ability to break down your project into manageable tasks. The recommended length is 150 words.
Decomposition: Construct a reasonable decomposition of your problem scenario into smaller sub-problems or components, effectively using diagrams.
Chronology: Include a proposed timeline for the steps involved in planning, designing, developing, testing, and evaluating your solution.
Addressing Requirements: Ensure your plan directly addresses all success criteria identified in Criterion A.
In this section, you should provide a technical overview that would allow a third party to recreate your product. The recommended length is 150 words.
System Model: Construct a complete model using diagrams that show all system components, their connections, and the user interface design.
Algorithms: Construct algorithms for your system components using natural language, flowcharts, or pseudocode.
Testing Strategy: Describe a systematic approach to evaluating your solution, often presented as a table with proposed test data and expected outcomes aligned with your success criteria.
This is the core of your documentation, where you justify your technical choices and demonstrate your coding skills. The recommended length is 1000 words.
Technique Justification: Evaluate the choices you made to implement your algorithms, such as specific loops, data structures, or the integration of software tools.
Code Documentation: Include key excerpts of your code that are essential to the functioning of your algorithms. Ensure the code is readable, consistent, and contains relevant comments.
Testing Evaluation: Justify the effectiveness of your testing strategy, ensuring it covers the correctness, reliability, and efficiency of your product.
You must submit a separate video file (e.g., MP4) as evidence of your work.
Functionality: The video must demonstrate the full functionality of your completed software product.
Testing in Action: You must show specific examples of your testing strategy being deployed to prove the software works as intended.
In the final section, you look back at your initial goals. The recommended length is 400 words.
Success Criteria Assessment: Evaluate the extent to which the final product met each success criterion from Criterion A.
Improvements and Extensions: Justify specific product improvements or potential extensions, explaining how they would enhance the solution.
We hope this guide helps guide you in properly formatting and structuring your computer science IA! If you want to read some exemplary IAs before you start writing, we've got you covered! Simply head to the Clastify website, where you will be able to find numerous computer science IA ideas and examples, so you can look for the ones that are the most relevant to your topic. Good luck!