As Salamu Alaykum Wa Rahmatullahi Wa Barakatuh World!
Here's the next set of resources that I have previously shared on this blog about section 1.2 all in a single Drive folder. In other news, i'm looking to complete my summary presentation series (or at least Component 2) by the end of next week InShaAllah. That's all for now.
Here's the link: 1.2 Software and software development
Hope this helps!
Showing posts with label 1.2 Software and software development. Show all posts
Showing posts with label 1.2 Software and software development. Show all posts
Thursday, 14 December 2017
Friday, 10 November 2017
Road To 200 OCR A Level Computer Science Resources: 2 Stages Of Compilation Resources
As Salamu Alaykum Wa Rahmatullahi Wa Barakatuh World!
2 stages of compilation resources count as # 181 and 182. I think these are the first ones for this topic as well. They're both useful in their own ways but I'd say the first one is more relevant to the OCR spec than the latter.
Here's the links:
2 stages of compilation resources count as # 181 and 182. I think these are the first ones for this topic as well. They're both useful in their own ways but I'd say the first one is more relevant to the OCR spec than the latter.
Here's the links:
Hope this helps!
Monday, 9 October 2017
Road To 200 OCR A Level Computer Science Resources: 2 OOP Resources
As Salamu Alaykum Wa Rahmatullahi Wa Barakatuh World!
I think I can reach 200 a lot earlier than previously expected. After that I'll have more time to create my own resources. Anyway, resources # 162 and 163 take the form of 2 OOP resources (that's Object Oriented Programming for those of you who haven't come across this topic before).
These are also the first OOP resources I'm sharing on this blog somehow. After realising what topics were already covered in the big list, I have a better idea now of what topics are still unaccounted for.
One resource is a PDF covering pretty much everything about OOP and the other's a presentation specifically on encapsulation. As far as the theoretical side goes, OOP (like any other topic) is quite easy to understand but when you get to the programming side, things can get a bit tricky.
In my opinion Procedural languages are easier to code than OOP but maybe that's because I'm a Python guy and I haven't really learnt an OOP language yet (apart from VB.NET but I don't really like that).
Here's the links:
Hope this helps!
Monday, 2 October 2017
Here's A Couple Of Software Development Resources
As Salamu Alaykum Wa Rahmatullahi Wa Barakatuh World!
I don't think I've ever shared a software development resource before but I found these 2 resources which aren't specifically for the H046/H446 spec (they aren't even specifically for A level, let alone for OCR) but hey, when resources are scarce you have to make do with anything you find.
They only cover 2 out of the 5 software development methodologies you need to know: the waterfall life-cycle and agile development methods. Obviously if you want all 5 covered in the detail that the spec requires you can always take a look at the sneak peek of my revision guide.
Anyway, the whole software development topic, like any other theoretical one, is quite simple. You just have to know what each method is along with the relative pros and cons of each.
I think i'll make a post soon that has ALL the resources I've ever shared on this blog all in one folder so all you lovely people don't have to go searching for them by clicking on different posts (at times like this I wish I made a website *cries*).
Here's the links:
I don't think I've ever shared a software development resource before but I found these 2 resources which aren't specifically for the H046/H446 spec (they aren't even specifically for A level, let alone for OCR) but hey, when resources are scarce you have to make do with anything you find.
They only cover 2 out of the 5 software development methodologies you need to know: the waterfall life-cycle and agile development methods. Obviously if you want all 5 covered in the detail that the spec requires you can always take a look at the sneak peek of my revision guide.
Anyway, the whole software development topic, like any other theoretical one, is quite simple. You just have to know what each method is along with the relative pros and cons of each.
I think i'll make a post soon that has ALL the resources I've ever shared on this blog all in one folder so all you lovely people don't have to go searching for them by clicking on different posts (at times like this I wish I made a website *cries*).
Here's the links:
Hope this helps!
Thursday, 7 September 2017
A Fairly Thorough Memory Addressing Resource
As Salamu Alaykum Wa Rahmatullahi Wa Barakatuh World!
As promised, today's post will not feature an algorithms resource but something different. This resource isn't even a presentation but a document that goes through all the modes of addressing that you need to know (plus relative addressing which you don't).
This resource was probably made with the old H047/H447 spec in mind but it still covers pretty much all the content needed for the new H046/H447 spec as well. As usual, the spec mentions this topic in a vague fashion by simply stating each mode of addressing you need to know (immediate, direct, indirect and indexed).
However, a closer inspection of the subject content clarification guide gives us a better understanding as to what knowledge is required:
There's a lot going on above so let's break it down. Firstly, you need to have a general understanding of memory addressing along with all of the modes aforementioned. Secondly, just knowing the theory isn't enough, you need to integrate your understanding of memory addressing with assembly language (which you should already be familiar with before learning this. So basically, you need to be able to work with the modes of addressing mentioned whilst dealing with assembly language.
Despite being essentially a theoretical topic, memory addressing can be a bit tricky at first. However, practicing questions from past papers can greatly increase your confidence when dealing with addressing. You can find loads of addressing questions in the advanced computing theory papers of the old spec but doing the new spec questions are more worthwhile.
Being good at assembly language helps a lot in this topic so I guess this is a bit related to the practical side of things rather than the theoretical. But anyway, I recommend using the document below to gain an understanding of the topic and use The Ultimate OCR A Level Computer Science Dictionary to remind yourself of the definitions of each mode of addressing.
Here's the link: Memory Addressing Document
Hope this helps!
As promised, today's post will not feature an algorithms resource but something different. This resource isn't even a presentation but a document that goes through all the modes of addressing that you need to know (plus relative addressing which you don't).
This resource was probably made with the old H047/H447 spec in mind but it still covers pretty much all the content needed for the new H046/H447 spec as well. As usual, the spec mentions this topic in a vague fashion by simply stating each mode of addressing you need to know (immediate, direct, indirect and indexed).
However, a closer inspection of the subject content clarification guide gives us a better understanding as to what knowledge is required:
"Candidates need an understanding of addressing, which should be integrated with assembly language. Candidates should have experience of using immediate, direct, indirect and indexed addressing in the writing, reading and tracing of programs written in assembly language."
There's a lot going on above so let's break it down. Firstly, you need to have a general understanding of memory addressing along with all of the modes aforementioned. Secondly, just knowing the theory isn't enough, you need to integrate your understanding of memory addressing with assembly language (which you should already be familiar with before learning this. So basically, you need to be able to work with the modes of addressing mentioned whilst dealing with assembly language.
Despite being essentially a theoretical topic, memory addressing can be a bit tricky at first. However, practicing questions from past papers can greatly increase your confidence when dealing with addressing. You can find loads of addressing questions in the advanced computing theory papers of the old spec but doing the new spec questions are more worthwhile.
Being good at assembly language helps a lot in this topic so I guess this is a bit related to the practical side of things rather than the theoretical. But anyway, I recommend using the document below to gain an understanding of the topic and use The Ultimate OCR A Level Computer Science Dictionary to remind yourself of the definitions of each mode of addressing.
Here's the link: Memory Addressing Document
Hope this helps!
Subscribe to:
Posts (Atom)