Computer Science A-level Project Writeup guide for OCR A-level
Icodewithben
Helpful Links:
Look at the Mark Scheme on the A-level hub: Project Marker (alevelcompscimarking.herokuapp.com) you should use this to roughly understand the sections you need
Mark scheme specification: OCR A Level Computer Science H446 Specification
Example top grade project : 514655-programming-project-set-a-high.pdf
Scope of a project: OCR A Level Computer Science Project Setting Guidance
Systems methodology , you need to understand Agile, Waterfall etc and the SDLC stage Unit 23 — Systems Methodology — YouTube
A-level project template:
Below is a possible layout you could follow for your project, this is taken from Example top grade project : 514655-programming-project-set-a-high.pdf but I have added the mark scheme for top band marks which is from OCR A level mark scheme you can see it on Project Marker (alevelcompscimarking.herokuapp.com) too:
Section 1 — Analysis
Problem Definition
- The problem statement short paragraph
- Stakeholders, who will use it?
- Decompose problem (break it down show why having computer is necessary)
- Interviews/ Requirement gathering… however you want to do this questionnaires reddit talk to people… Key thing is to analyse the info you get
- Transcribe or show info gathered then analyse what it means for you project
- Research into other problems… what other trading app are out there and how do they work, what features do you want to take from them or improve?
- Hardware requirements, what hardware or software is required to run this app?
- What does stakeholders want in terms of the design of app and functionality
- LIST SUCCESS CRITIERA… these are your business cases e.g. users can search a stock and analyse its price, users can buy a stock in the simulation, they can login etc.
Section 2 — Design
- User Interface design: Draw wireframes for each screen and describe each button or feature saying how they link to success criteria
- Justify and explain each screen , why is it there, how does it help to find a solution to your problem?
- How have you made your application usability, have you thought about user experience. Justify and explain why the screens are like that
- Get stakeholder input on the designs , analyse this feedback and change the designs
- Algorithms — Describe any complex algorithms that you want to design to put into your project, link to success criteria. Show pseudocode to give an idea of how the algorithms will work.
- Justify and explain the algorithms how they will be developed and how you will break the algorithm down so you can develop.
- Show a USE CASE and UML Class diagram of how the code in the app will function Summary of Use Case and Class Diagrams (youtube.com)
- Show how the flow of the actions lead into other screens DFD diagram or just from your design of screen show the functions and code that will be run 4 — Data Flow Diagrams — Unit 23 Systems Methodologies (youtube.com)
- Show Data dictionaries highlight all the variables you will use CASE Tools Data Dictionaries Decision Tables Screen Design (youtube.com)
- Show decision tables where necessary to describe the algorithms or key choices Tools Data Dictionaries Decision Tables Screen Design (youtube.com)
- For any databases show database schema ERD diagrams Entity Relationship Diagrams (youtube.com) how to make one How to make an Entity Relationship Diagram (youtube.com)
- Design your testing table , show how you will comprehensively test your application, describe how else you will test it?
Section 3 — Development and testing
- An iterative detailed description explaining and justifying why you have written he code you wrote in there… break the project down into stages or sprints saying what you delivered and how you tested it at the end of each stage.
- Show how you tested each part that you developed, you need to keep a record of all the parts you developed, what went wrong and how you fixed the bugs.
- You should show why you made the code easily adaptable and maintainable
- You should explain in detail how you developed all the algorithms you said you were going to write in your design
- At the end of each stage of development describe: What has been done, how it has been tested, how it meets your success criteria, whether you changed the design or not, where you are in the project what else needs to be done
Basic Structure: Documenting the milestones
For each milestone, include the following:
1. Objective of the milestone: In one or two sentences, describe what this milestone achieves.
2. Code listing: Provide a listing of the code for this milestone. Code must be commented with appropriate variable and data structure names.
3. Explanation of the code: Explain what the code section does and justify algorithms or approaches. It might not be immediately obvious to an examiner how the code works or why problems have been solved in the way they have. Remember, the examiner may not be familiar with the language you are using. If input validation is required, explain that too.
4. Module testing: Explain the tests you performed for this section of code and the outcome of those tests. You will likely be playing the game and tweaking the variables a lot to get the outcome you want. You should provide evidence of this process.
5. User feedback: Your user should tell you what they like and dislike about this aspect of the development so far, with ideas for future development. Your user must be an integral part of the iterative development process.
6. Reflections: As a result of playtesting and user feedback, discuss what needs to be changed.
Section 3 — Testing for Development
And testing to inform evaluation.
- Final Testing — You need to carry out the tests you designed in the design section saying whether or not they passed and the application meets the success criteria. Describe the tests in detail highlighting where the tests went wrong and what you need to do to fix them.
- Stakeholder or user testing — Hand the application to the users and let them play with it. You need to monitor them then interview them again like you did for design to fully understand the things that went well or not so much.
Section 3 — Evaluation of solution
- List all the success criteria and say whether or not you met it
- Show evidence of each success criteria being met by showing screen shots and detailed descriptions
- Explain and justify why you did or did not meet the success criteria
- Explain and justify how usable your application is to users, what could be improved
Limitations
- Show that you can be criticial of your work, show what you think worked well and what did not.
- Describe how you can improve it by giving solutions. Justify and explain it.
Maintenance
- How will you plan to maintain and update the application? Why? Justify and explain
Written by Icodewithben
Watch the YouTube: https://www.youtube.com/channel/UCJyd5XVdI2rrXENOIAaU-xw . The Computer Science A-level hub https://alevelcompscimarking.herokuapp.com/
Text to speech
More results...
- View all quizzes
- GCSE Concepts & Quizzes
- A Level Concepts & Quizzes
- Little Man Computer (LMC)
- Computer Networks
- Database Concepts
- Cryptography
- All Python Challenges
- Python Challenges – Beginner
- Python Challenges – Intermediate
- Python Challenges – Advanced
- HTML, CSS & JavaScript
- BBC micro:bit
- OCR J277/01 – 1.1 System Architecture
- OCR J277/01 – 1.2 Memory and Storage
- OCR J277/01 – 1.3 Computer networks
- OCR J277/01 – 1.4 Network security
- OCR J277/01 – 1.5 – Systems software
- OCR J277/01 – 1.6 – Ethical, legal, cultural and environmental impacts of digital technology
- OCR J277/02 – 2.1 – Algorithms
- OCR J277/02 – 2.2 – Programming fundamentals
- OCR J277/02 – 2.3 – Producing robust programs
- OCR J277/02 – 2.4 – Boolean logic
- OCR J277/02 – 2.5 – Programming languages and Integrated Development Environments
- OCR H446/01 – 1.1 The characteristics of contemporary processors, input, output and storage devices
- OCR H446/01 – 1.2 Software and software development
- OCR H446/01 – 1.3 Exchanging data
- OCR H446/01 – 1.4 Data types, data structures and algorithms
- OCR H446/01 – 1.5 Legal, moral, cultural and ethical issues
- OCR H446/02 – 2.1 Elements of computational thinking
- OCR H446/01 – 2.2 Problem solving and programming
- OCR H446/02 – 2.3 Algorithms
- 101 Extra Python Challenges
- 101 Python Challenges
- 101 Computing Challenges
- Become a member!
- Your Account
- Solved Challenges
- Membership FAQ
OCR – H446 – Computer Science A-Level
- Computer Science A-Level – H446
OCR Computer Science A Level (H446)
- H446/01 – Computer Systems
- 1.1 – The characteristics of contemporary processors, input, output and storage devices
- 1.2 – Software and software development
- 1.3 – Exchanging data
- 1.4 – Data types, data structures and algorithms
- 1.5 – Legal, moral, cultural and ethical issues
- H446/02 – Algorithms and programming
- 2.1 – Elements of computational thinking
- 2.2 – Problem solving and programming
- 2.3 – Algorithms to solve problems and standard algorithms
OCR H446/01 – 1.1 The characteristics of contemporary processors, input, output and storage devices
OCR H446/01 – 1.2 Software and software development
OCR H446/01 – 1.3 Exchanging data
OCR H446/01 – 1.4 Data types, data structures and algorithms
OCR H446/01 – 1.5 Legal, moral, cultural and ethical issues
OCR H446/02 – 2.1 Elements of computational thinking
OCR H446/01 – 2.2 Problem solving and programming
OCR H446/02 – 2.3 Algorithms
Extra Revision Resources…
Did you like this challenge?
Click on a star to rate it!
Average rating 4.4 / 5. Vote count: 19
No votes so far! Be the first to rate this post.
As you found this challenge interesting...
Follow us on social media!
Other challenges you may enjoy...
Recent Posts
- Pronic Numbers Challenge
- Olympics Host Cities (CSV Challenge)
- Paris 2024 – JSON Challenge
- Online Python IDE
- Space Explorer: The Way Back Home
- The Lost Treasures of Pirate Island
- Cryptic Puzzles – Computer Networks
- Computer Science – Cryptic Crossword #02
- Ice Cream Price Calculator
- Revision Progress Tracker Algorithm
- View more recent posts...
- View all our challenges...
- Take a Quiz...
Our Latest Book
- Computing Concepts
- Python Challenges
- Privacy Policy
- International
- Education Jobs
- Schools directory
- Resources Education Jobs Schools directory News Search
OCR A level Computer Science Overall Grade Calculator
Subject: Computing
Age range: 16+
Resource type: Other
Last updated
- Share through email
- Share through twitter
- Share through linkedin
- Share through facebook
- Share through pinterest
I have created this quick grade calculator to help predict grades a little more accurately.
This uses the 2019 grade boundaries and raw marks from Paper 1, Paper 2 and NEA. I have used my most recent mock exams for the Paper 1 and Paper 2 marks.
I have then added a table that calculates 5% added to the exam paper raw marks, and another table with 10% (students always do slightly better in their final exams compared to their mocks and you may see a pattern from past year groups between 5 and 10% increase). Both tables have a cell that calculates how many marks would be needed to get up to the next grade (ie if, with the 5% added, the student is on a C grade - how many more marks would they need to get for the B grade).
Of course, due to covid the grade boundaries are very likely to come down slightly but I have found the “how many more marks” has been really helpful to see if I think the student has a chance for that next grade up… usually you can see if it is really unlikely (I don’t think the grade boundaries are going to come down substantially).
I hope this helps with predictions, but also to help discuss what they need to be working toward on their individual papers.
Tes paid licence How can I reuse this?
Your rating is required to reflect your happiness.
It's good to leave some feedback.
Something went wrong, please try again later.
This resource hasn't been reviewed yet
To ensure quality for our reviews, only customers who have purchased this resource can review it
Report this resource to let us know if it violates our terms and conditions. Our customer service team will review your report and will be in touch.
Not quite what you were looking for? Search by keyword to find the right resource:
Teach Computer Science
OCR A Level Computing Teaching Resources & Revision Material
OCR A Level Computer Science mapping file. Download our comprehensive teaching resources and use the mapping table to align to the OCR examination board.
|
| |||
| languages | |||
|
| |||
|
| |||
|
|
| ||
|
| |||
|
| |||
|
|
| ||
A Level Science grade boundaries
This page outlines the A Level Science Grade Boundaries for AQA and OCR A exam boards.
Each year the exam boards endeavour to make sure that exam papers are designed to be no easier or harder to achieve a particular grade than previous years. This does mean that each year the percentage required for each grade changes slightly depending on how hard the exam paper is. And so, Oxford Revise has collected all the grade boundaries for the last 5 years of exams, giving you an idea of what percentage you will need to achieve to get a specific grade.
Grade boundaries for your subject are not published before the exams take place. Boundaries are set after exams have been completed and papers have been marked.
Check below for the AQA or OCR A exam board and see what was required in previous years for Science, Biology, Chemistry and Physics.
AQA A Level Biology
| A* | 180/260 (69%) | 173/260 (67%) | 168/260 (65%) | 170/260 (65%) | 178/260 (68%) | 166/260 (64%) |
| A | 153/260 (59%) | 142/260 (55%) | 136/260 (52%) | 138/260 (53%) | 149/260 (57%) | 138/260 (53%) |
| B | 125/260 (48%) | 115/260 (44%) | 113/260 (43%) | 114/260 (44%) | 125/260 (48%) | 116/260 (45%) |
| C | 98/260 (38%) | 89/260 (34%) | 91/260 (35%) | 90/260 (35%) | 101/260 (39%) | 94/260 (36%) |
| D | 71/260 (27%) | 63/260 (24%) | 69/260 (27%) | 67/260 (26%) | 77/260 (30%) | 72/260 (28%) |
| E | 44/260 (17%) | 37/260 (14%) | 47/260 (18%) | 44/260 (17%) | 53/260 (20%) | 50/260 (19%) |
AQA A Level Chemistry
| A* | 250/300 (83%) | 237/300 (79%) | 236/300 (79%) | 235/300 (78%) | 246/300 (82%) | 241/300 (80%) |
| A | 210/300 (70%) | 196/300 (65%) | 192/300 (64%) | 192/300 (64%) | 206/300 (69%) | 198/300 (66%) |
| B | 173/300 (58%) | 158/300 (53%) | 158/300 (53%) | 157/300 (52%) | 170/300 (57%) | 163/300 (54%) |
| C | 136/300 (45%) | 121/300 (40%) | 124/300 (41%) | 123/300 (41%) | 135/300 (45%) | 128/300 (43%) |
| D | 99/300 (33%) | 84/300 (28%) | 90/300 (30%) | 89/300 (30%) | 100/300 (33%) | 94/300 (31%) |
| E | 62/300 (21%) | 47/300 (16%) | 56/300 (19%) | 55/300 (18%) | 65/300 (22%) | 60/300 (20%) |
AQA A Level Physics – Coming soon
Ocr a level biology.
| A* | 183/270 (68%) | 184/270 (68%) | 169/270 (63%) | 173/270 (64%) | 185/270 (69%) | 187/270 (69%) |
| A | 155/270 (57%) | 156/270 (58%) | 137/270 (51%) | 144/270 (53%) | 158/270 (59%) | 159/270 (59%) |
| B | 130/270 (48%) | 130/270 (48%) | 115/270 (43%) | 121/270 (45%) | 136/270 (50%) | 135/270 (50%) |
| C | 106/270 (39%) | 104/270 (39%) | 94/270 (35%) | 98/270 (36%) | 114/270 (42%) | 111/270 (41%) |
| D | 82/270 (30%) | 78/270 (29%) | 73/270 (27%) | 76/270 (28%) | 92/270 (34%) | 87/270 (32%) |
| E | 58/270 (21%) | 52/270 (19%) | 52/270 (19%) | 54/270 (20%) | 70/270 (26%) | 63/270 (23%) |
OCR A Level Chemistry
| A* | 234/270 (87%) | 213/270 (79%) | 211/270 (78%) | 219/270 (81%) | 230/270 (85%) | 237/270 (88%) |
| A | 198/270 (73%) | 168/270 (62%) | 172/270 (64%) | 179/270 (66%) | 196/270 (73%) | 205/270 (76%) |
| B | 158/270 (59%) | 132/270 (49%) | 139/270 (51%) | 144/270 (53%) | 161/270 (60%) | 169/270 (63%) |
| C | 118/270 (44%) | 97/270 (36%) | 107/270 (40%) | 110/270 (41%) | 126/270 (47%) | 133/270 (49%) |
| D | 79/270 (29%) | 62/270 (23%) | 75/270 (28%) | 76/270 (28%) | 91/270 (34%) | 97/270 (36%) |
| E | 40/270 (15%) | 27/270 (10%) | 43/270 (16%) | 42/270 (16%) | 56/270 (21%) | 62/270 (23%) |
OCR A Level Physics
| A* | 211/270 (78%) | 211/270 (78%) | 214/270 (79%) | 221/270 (82%) | 230/270 (85%) | 219/270 (81%) |
| A | 182/270 (67%) | 181/270 (67%) | 182/270 (67%) | 192/270 (71%) | 204/270 (76%) | 188/270 (70%) |
| B | 151/270 (56%) | 147/270 (54%) | 151/270 (56%) | 159/270 (59%) | 174/270 (64%) | 158/270 (59%) |
| C | 120/270 (44%) | 113/270 (42%) | 120/270 (44%) | 126/270 (47%) | 144/270 (53%) | 128/270 (47%) |
| D | 90/270 (33%) | 80/270 (30%) | 89/270 (33%) | 94/270 (35%) | 114/270 (42%) | 98/270 (36%) |
| E | 60/270 (22%) | 47/270 (17%) | 59/270 (22%) | 62/270 (23%) | 84/270 (31%) | 68/270 (25%) |
OCR GCSE Computer Science Grade Boundaries
Scroll to see replies
Quick Reply
Related discussions.
- About Computer Science
- Computer Science Grade Boundaries
- GCSE Results: Post your results
- Who has done edexcel history gcse and ocr CS?
- Worried about my maths grade GCSE
- GCSE Results Day Countdown - 24th August 2023 TODAY - #BeResultsProud!
- Should I get my results remarked?
- I chose Computer Science GCSE OCR - help
- A level subjects
- Alevel options
- Law or Politics-A level
- Which gcse option is better to pick and more easier and less stressful???
- GCSE Grade Boundaries 2025- 2026
- What gcse options should I pick if wanna be a future pharmacist???
- gsce 2025. how are you guys feeling.
- Gcse ocr computer science
- GCSE Exam Discussions 2024
- AQA GCSE Computer Science Paper 1 (8525/1A, 1B, 1C) - 19th May 2023 [Exam Chat]
- GCSE Exam Discussions 2023
Last reply 5 days ago
Last reply 1 week ago
Last reply 1 month ago
Last reply 2 months ago
Articles for you
Students react after GCSE Computer Science Paper 2 on 21 May 2024
Students react after GCSE Computer Science Paper 1 on 15 May 2024
Students react after GCSE Computer Science Paper 1 on 19th May 2023
Finding a university place in Ucas Clearing 2024: 10 top tips to help you get ready
IMAGES
COMMENTS
37 0. 37 0. H600 01 Art, Craft and Design: Personal investigation. H600 02 Art, Craft and Design: Externally set task. H6 01 Fine Art: Personal investigation. H601 02 Fine Art: Externally set task. H602 01 Graphic Communication: Personal investigation. H6 02 Graphic Communication: Externally set task.
13 0. 13 0. 30 0. Level Music. H543 01 Performing A. H543 02 Performing B. H543 03 Composing A. H543 04 Composing B. H543 05 Listening and appraising All options *To create the overall boundaries, components 03 & 04 are weighted to respectively give marks out of 105 & 75.
GCSE grade boundaries - June 2024 PDF, 1MB. Cambridge Nationals grade boundaries - June 2024 PDF, 267KB. Entry Level grade boundaries - June 2024 PDF, 129KB. AS and A Level grade boundaries - June 2024 PDF, 433KB. Core Maths, Extended Project and FSMQ grade boundaries - June 2024 PDF, 170KB.
Whilst I am doing OCR Computer Science the only real advice I can offer you is simply meet the objectives. Marking CS projects is an objective thing, and you just have to satisfy the criteria given by OCR in their specification as best you can. I'm currently on track to receive ~90%+ and this is what I'm doing. In terms of your design phase, try to make as many useful prototypes on paper ...
A-level project template: Below is a possible layout you could follow for your project, this is taken from Example top grade project: 514655-programming-project-set-a-high.pdf but I have added the ...
My best guess would be 165-170 for a C but I'm of the opinion that the boundaries change based on a national average, so they really could go either way with it. Good point, as many students had found the papers "much" easier than previous years. Grade boundaries could even be higher than 2019 even.
H446 Course Overview. The OCR Computer Science A Level (H446 Specification) consists of 3 units of work as follows: H446/01 - Computer Systems. 1.1 - The characteristics of contemporary processors, input, output and storage devices 1.2 - Software and software development
Z2 - Statistics 2. Z3 - Statistics 3 Raw UMS Raw UMS Raw UMS. 72 100. 72 100. 72 100 No entry in June 2019. 80 70 60 50 40 0 No entry in June 2019. 80 70 60 50 40 0 No entry in June 2019. 80 70 60 50 40 0. AS & Advanced GCE Travel and Tourism.
OCR A level Computer Science Overall Grade Calculator. I have created this quick grade calculator to help predict grades a little more accurately. This uses the 2019 grade boundaries and raw marks from Paper 1, Paper 2 and NEA. I have used my most recent mock exams for the Paper 1 and Paper 2 marks. I have then added a table that calculates 5% ...
Searching algorithms. 54. Sorting algorithms. 55. Algorithms for main data structures. 56. Dijkstra's shortest path algorithm and A* algorithm. OCR A Level Computing teaching resources, revision material & lesson plans. Suitable for teachers of Computer science, parents or students.
Our registered address is AQA, Devas Street, Manchester M15 6EX. Component grade boundaries - June 2023 exams. This document shows the confirmed subject grade boundaries and the notional component grade boundaries for illustrative purposes only Where component marks are scaled two sets of grade boundaries are shown.
03 Iterative Design Project (OCR Repository) 04 Iterative Design Project (Postal Moderation) *To create the overall boundaries, components 03 and 04 are weighted to give marks out of 150
Grade Boundaries for A Level and GCSEs. This page gathers together the grade boundaries for the subjects listed below, at GCSE and A Level, for exam boards including AQA, Edexcel and OCR. Each year the exam boards endeavour to make sure that exam papers are designed to be no easier or harder to achieve a particular grade than previous years.
r/GCSE is the place for tips, advice, resources and memes for your GCSE exams.
Looking at last year's boundaries, 237/375 was an A. 237 - 54 = 182. So you need 182/300 on Paper 1 and Paper 2 which works out as 60.67% for an A. An A* was 296. I know you didn't ask but in case you're interested, 296 - 54 = 242.. 242/300 works out as 80.67% so it's definitely achievable as well! Reply 8. 4 months ago.
A grade boundary is the minimum mark you need to get a grade. For example, if the grade boundary for a Grade C is 160 marks, you need to get at least 160 to achieve a Grade C. A mark of 159 would therefore be a Grade D. Grade boundaries for linear qualifications are set at qualification level. This means it's how you did overall which decides ...
Original post by swnap. I dont think you did anything wrong. Most people found the papers easy so the grade boundaries must be astronomical. That is fair enough, just wanna see what parts i did mess up on though cos i found most of the 2 papers relatively easy. Reply 7. 6 months ago. A.
62/270. (23%) 84/270. (31%) 68/270. (25%) Oxford Revise has gathered all the grade boundaries for the A Level Science AQA and OCR A exam boards, to show what was needed to achieve specific grades in previous years.
GCSE (9-1) qualification and notional component raw mark grade boundaries June 2023 series. GCSEs are 'linear qualifications'. This means all the assessment takes place at the end of the course. ... 'Grades' at component level don't automatically add up to the same grade at qualification level. ... GCSE Computer Science J277 01 ...
Computer science ocr grades & grade boundaries. aliyahh16. 2. I got C for one coursework And a U for another:/ If i get the B in my exam, what will my overall grade be? ... OCR Computer Science A Level - Resource Guide; grade 9? GCSE Results Day Countdown - 24th August 2023 TODAY - #BeResultsProud! A level subjects;
The document discusses the challenges of writing coursework, especially for complex subjects like OCR ICT A Level. It notes that coursework requires in-depth understanding, practical application, and meeting grade boundaries, adding stress. Balancing coursework with other commitments can feel overwhelming. The document then introduces HelpWriting.net as a service that can provide expert ...
We know it's useful to see how students did in each component so we also publish component grade boundaries. These show what the grade would be if we gave out grades for components. 'Grades' at component level don't automatically add up to the same grade at qualification level. For more information about results and grade calculations ...
Ocr computer science a level (h446) Hello, I hope you all are well. I am currently studying ocr computer science on my own. However, I am really struggling with the project both in terms of the writing bits and developing a solution so Im heading for a solid U. Luckily, I believe there are alot of helpful people on this site that can provide me ...
6 years ago. ns_2. Original post by mfaliuk14. If u look at the old spec, an A* was 56/80, and that was considering their course was 60% coursework and our theory is much harder, so I'm predicting the grade boundaries to be low, with a 9 between 60 and 65.