WJEC Applied ICT A Level Unit 2 - eSkills
I no longer teach A Level Applied ICT but I'll leave these pages up as an archive which might still be helpful for someone, somewhere.
Part 3 - Spreadsheet Implementation
There are 15 marks for implementing your spreadsheet effectively...
This doesn't have to mirror your design exactly - it's absolutely fine to have made changes; in fact, it's expected. If the implementation is exactly the same as the design then the marker may think you implemented before you designed - which would lose you marks.
Some key points to note:
- keep to the brief. Produce all the "required outcomes";
- take care with the naming of items. There are marks for labelling everything sensibly. If you can keep to a standard protocol (such as the Leszynski naming convention) then that's a good idea
- keep in mind accessibility, usability and efficiency. The system should be easy to use and should be safe to use - lock cells down that the user doesn't need to get into
- if you want to use user forms to do the work for you then go ahead - but take care! These are complex and can become a time sink. It's more important to get a working solution
- test and then test again. Try and break it. I will when I mark it...
If you password protect anything please use the password "password". And make sure you tell the marker this in your e-portfolio. And, preferably, provide a version with no passwords on and no stuff hidden on it!
Strategies for dealing with errors on a spreadsheet. These will help gain marks in terms of using validation rules (the worksheets row of the markgrid), aiding data entry (input row) and in terms of a user interface (the interface row). Loads of marks in other words...
The Markgrid
Spreadsheet implementation markgrid - PDF version of markgrid