I’ve tried to trawl through the three available papers to know exactly what to teach. I’ve emailed the SQA to make sure that some of my assumptions are correct and I’m waiting for a response.
I am assuming that anything that is mentioned explicitly in AH cannot be asked at Higher therefore, in the waterfall model of software development, we don’t need to go into as much detail as in the old higher.
For example, component, integrative, beta (acceptance) and final testing is AH only so no need to discuss alpha testing. Evaluation criteria mentioned at AH are usability, efficiency, effectiveness(goal-tracking), reliability and robustness so these terms should not appear at Higher. The three types of maintenance come at AH so no need to teach them at Higher.
However, I don’t think we can assume all of the rest since the course assessment specification mentions terms without giving us the detail of what might be asked.
For example, we were asked in 2015 to describe a method of compressing video files. Therefore, I think we might, in the future, be asked to describe how bitmapped graphics and audio files are compressed. They won’t mention RLE or LZW explicitly but the principles might be required.
Similarly, we had to calculate video file size in 2015 so I’d expect a graphic or audio file size question to be possible.
I have still taught memory read and write as this seems the logical extension to N5 for computer architecture although most questions have focused on cache memory.
Operating systems are mentioned under Technical Implementation(software requirements) and the 2015 paper asked about levels of access so who knows what might be asked?
To summarise, no one really knows as the assessment specification lacks the detail that can be found in Graphic Comms, Physics etc.
I’ll try and upload my course content document with detail I’ve added from the papers we have seen.