computer science NEA documentation

2

hi!! I’m in y12, and I’m somewhat close to finishing the design section of my computing NEA, so I’ll be starting the coding documentation stuff kinda soon! issue is I genuinely don’t understand how you’re meant to document the code?? I’ve checked the mark schemer and other resources and I still don’t really understand 😭😭 how exactly do you do it?

Reply 1

kanji13

9

hi, im also doing the design section of my computing NEA (OCR) rn. when documenting code, i think u're supposed to write the code & when taking screenshots, do it to the way u categorised it in the top down diagram. i.e, in a yr top down diagram, if there was a category for a sign up window, so u can take a screen shot of that part of the code & paste it under there.

u have to make sure the code is appropriately annotated (comments) & like if u get errors & bugs, u still have to show that code, then explain what u did to correct that & put the final correct code for that part (prototype versions). And, also do tests while coding each part & explaining what happened if it fails/ what u did to fix it....

This is the OCR marking scheme for this btw:

Reply 2

I. T

4

Hi, im also doing alevel computer science ocr and wondering how have u guys started ur nea's already, my teachers haven't even mentioned it yet 😭.
Should i begin it on my own or wait for my teacher?? How long do i need for this?

Reply 3

foxin

OP

2

Original post

by I. T

Hi, im also doing alevel computer science ocr and wondering how have u guys started ur nea's already, my teachers haven't even mentioned it yet 😭.
Should i begin it on my own or wait for my teacher?? How long do i need for this?

my class was told to start in about November, but I’m not sure if that’s the standard ^^ I think you should ask your teacher, and the time needed definitely depends on what you do for it because the project is due in for May next year I believe

Reply 4

foxin

OP

2

Original post

by kanji13

hi, im also doing the design section of my computing NEA (OCR) rn. when documenting code, i think u're supposed to write the code & when taking screenshots, do it to the way u categorised it in the top down diagram. i.e, in a yr top down diagram, if there was a category for a sign up window, so u can take a screen shot of that part of the code & paste it under there.
u have to make sure the code is appropriately annotated (comments) & like if u get errors & bugs, u still have to show that code, then explain what u did to correct that & put the final correct code for that part (prototype versions). And, also do tests while coding each part & explaining what happened if it fails/ what u did to fix it....
This is the OCR marking scheme for this btw:

hmm… I’ve seen the ocr marking scheme and I honestly still don’t get it 😓😓😓 it feels awfully vague to me

Reply 5

I. T

4

Original post

by foxin

my class was told to start in about November, but I’m not sure if that’s the standard ^^ I think you should ask your teacher, and the time needed definitely depends on what you do for it because the project is due in for May next year I believe

Ok thanks, i will ask! Just curious, what are u doing for ur nea? Dont answer if u dont wanna!

Reply 6

kanji13

9

Original post

by I. T

Ok thanks, i will ask! Just curious, what are u doing for ur nea? Dont answer if u dont wanna!

yea, i posted a survey here for my NEA. u can check it out:
https://www.thestudentroom.co.uk/showthread.php?t=7644139&p=101071075&page=1#post101071075

p.s. there's 2 surveys in the link, one which i did for the analysis section, which i stopped accepting responses (cuz the analysis is done), the active form is most recent one, for the design section

Reply 7

I. T

4

Original post

by kanji13

yea, i posted a survey here for my NEA. u can check it out:
https://www.thestudentroom.co.uk/showthread.php?t=7644139&p=101071075&page=1#post101071075
p.s. there's 2 surveys in the link, one which i did for the analysis section, which i stopped accepting responses (cuz the analysis is done), the active form is most recent one, for the design section

Ooh wow thats really cool

Reply 8

kanji13

9

ty 😇

Reply 9

foxin

OP

2

Original post

by I. T

Ok thanks, i will ask! Just curious, what are u doing for ur nea? Dont answer if u dont wanna!

I’m doing a database system for floriography ^^ I planned to do a game but I couldn’t be bothered learning code for that lololol

Reply 10

I. T

4

Original post

by foxin

I’m doing a database system for floriography ^^ I planned to do a game but I couldn’t be bothered learning code for that lololol

Ah that really niche, i was thinking a typing game; smth like monkeytype or type racer 🤷*♀️

Reply 11

StaffsRep Aura

Official Rep

11

Original post

by foxin

hi!! I’m in y12, and I’m somewhat close to finishing the design section of my computing NEA, so I’ll be starting the coding documentation stuff kinda soon! issue is I genuinely don’t understand how you’re meant to document the code?? I’ve checked the mark schemer and other resources and I still don’t really understand 😭😭 how exactly do you do it?

Hey hey,
Great question and don't stress. When I was doing my NEA I followed the mark scheme mainly and then filled in the bits and bobs between. Unsure which board you are looking at sadly, though I did OCR. This cover sheet may be useful in blocking out your overall sections.

As you mentioned you are on design, here's some things you may choose to cover:
-Design requirements as a clear description of how your system will work end-to-end and what it will attempt to solve. This should flow nicely from your Analysis where you looked into research for past tools/existing works.
-Modular flowcharts of each piece of code + Overall flowchart of how they interact together. These 2 show how data flows between them and overall design for code. Pseudocode here also is a bonus. I went overboard in mine here and also stated in tables every variable I would use, their type (Int, bool, string etc), reasoning behind it and usage. If you can provide you are trying to be efficient, looked into data structures (e.g. using array over dictionary and reasoning) and logic you can get really good marks.
-If need be cover more into data design and structures if you are using them
-Explain module purpose and aims.
-If you focus on UI, go crazy here on design! Document rough sketches on how you wish for it to look using UX/UI practices, layouts, navigation flows and user interactions. Usability is a great thing to look at, especially with new accessibility laws coming out.
-Discuss constraints and feasibility and how you may account for them e.g. if your software is designed to run only on certain OS, hardware etc say why!

At every point in design you need to justify why things are needed and why your way is the best! E.g. If you decide to use a library over another, be clear on why. The why is important, I was told to imagine there is someone marking my work who has no knowledge of software development and is always asking questions. This got me near maximum marks!

Development is the section after followed by testing and evaluation. Try to keep these separate for ease of marking. The biggest advantage is there is no wordcount/limit from what I remember so go crazy!

Hope that helps,
Aura (Uni of Staffs Comp Sci)

Reply 12

Macclesfield

11

Original post

by kanji13

hi, im also doing the design section of my computing NEA (OCR) rn. when documenting code, i think u're supposed to write the code & when taking screenshots, do it to the way u categorised it in the top down diagram. i.e, in a yr top down diagram, if there was a category for a sign up window, so u can take a screen shot of that part of the code & paste it under there.
u have to make sure the code is appropriately annotated (comments) & like if u get errors & bugs, u still have to show that code, then explain what u did to correct that & put the final correct code for that part (prototype versions). And, also do tests while coding each part & explaining what happened if it fails/ what u did to fix it....
This is the OCR marking scheme for this btw:

I do Eduqas so sorry if my answer doesnt apply!!

Your NEA code needs to "show you know what you're doing" essentially, and you can do this in 2 different ways:

•

Write good code

•

Write justified code

For the "good" part; This is following general standards in programming (And having standards in your code!), having self-documenting variable names, using comments *where necessary* to explain what complicated code does, etc.

For the "justified" part - Do research on what you're programming, see how other people do it, and write about what you're taking from every implementation in your NEA. You essentially need to show the examiner what you're doing, why, pros and cons, and what this means for your project going forward.

Good luck!!

Reply 13

hazdasavage

1

Original post

by I. T

Hi, im also doing alevel computer science ocr and wondering how have u guys started ur nea's already, my teachers haven't even mentioned it yet 😭.
Should i begin it on my own or wait for my teacher?? How long do i need for this?

im in y13, id say deffo wait for your teacher to bring it up before you start it makes it farrrr easier to manage

computer science NEA documentation

Quick Reply

Related discussions

Articles for you

How The Student Room is moderated