A-level Computer Science Study Group 2022-2023

hi there, im in year 12 and really anxious about the a level. Even tho im not as competent on the programming side of things, i know i just have to keep it consistent and it will eventually get better. As for theory, what resources helped you the most and how did you revise. Because the OCR Mark schemes and exam papers are so different and specific compared to what we learn in the class with the PG Online powerpoints.

hi all, im doing OCR and im in year 13 rn, my paper 1 mock is tomorrow lol. just curious as to what people are doing their nea projects on and which language and platform are they coding on?

Hey all! I'm in year 12 with my exam in June I'm doing Pearson btec. I'm currently predicted a pass and find it difficult to find ways to revise. Any advice would be greatly appreciated.

Hey all! I'm in year 12 with my exam in June I'm doing Pearson btec. I'm currently predicted a pass and find it difficult to find ways to revise. Any advice would be greatly appreciated.

Hey guys! I'm currently in year 12, and we are beginning our plans for our computer science NEAs. And I have realised that I CAN'T CODE AT ALL. So far I've been using the method of 'fake it till you make it' and honestly, I prefer the theory side to it all. But I'm really scared for my nea because I have no confidence in my coding skills, and I don't think I'll be able to learn coding within a year :'(. SOMEONE HELP! (my nea is based around an adaptive quizzing tool).

Don't worry!! I was pretty rubbish at coding myself, but I manged to pull it up somehow and I got a 61/70. Just ensure that you plan out each and every module and its functionalities, how it will work, the variables used, how it will look as a GUI, the other modules that it will be connected to. Plan every little thing for every single module. Break it down as much as possible. Do it on paper or online (This is a form of decomposition!) . This is the first stage. Once you do this, you can see that each section is easily solvable using simple types of coding. This can be done by searching on YouTube, or the internet ( geeksforgeeks, is a good website) for that specific functionality ( obviously don't literally copy it), to implement in your own work. Just remember to start early. Even if you don't start to code immediately, ensure that the first stage, that is mentioned above, is completed when your Analysis section is also completed, at the very latest. This puts you in a good place, where you know exactly where you want to go with your project, and you won't be stressed on exactly where to start because you have it all planned out. The project will look less daunting because you just have to focus on each section bit by bit, consistently. Another tip is used to past examples of A* projects, for the layout of how the examiners expect the documentation to be. Just follow a framework that you find the most easy to understand. Another tip would be to use the project specification (can be found on the exam board website) as checklist. In your documentation, ensure that each section is fully completed, with every point on the specification. The last tip would be to use your teachers! I was lucky to have really good teachers who would set up up a meeting at every stage (Analysis, Design, Development and Evaluation). Just getting feedback from your teachers will really allow you to see where you can improve from a different perspective. That's all for now, to get you started. Of course there are many more, but stick to these and you will be fine! I was in hospital for 6 weeks and missed around a term for yr 13, so I was really behind on this project. But through lots of hard work and through lots of tears and prayers, I managed to pull through. So can you! Good Luck!