GCSE Computer Science (9–1) Non-Exam Assessment (NEA) Guide

[Pages:81]GCSE Computer Science (9?1) Non-Exam Assessment (NEA) Guide

for OCR J276

Examples, tips and advice on completing the NEA

1st Edition

Ceredig Cattanach-Chell

Axsied ak'seed

Axsied ak'seed

Axsied is producing many new products to support Computer Science for both OCR and other exam boards.

Be the first to find out about new products, information and free resources.

Stay up to date at update

For more information and to download free resources visit today

Exam-related

OCR GCSE Workbook Student/Teacher Bundle

GCSE Activities Book (All boards)

101 Activities for GCSE Computer Science - Teacher Edition

for 9-1 specifications

Crosswords, wordsearches, quizzes and general activities

1st Edition

BeNsots.e1ller

James Franklin Jonathan Fisher

Axsied ak'seed

NEA-related

Easy Python Docs Examples and syntax for offline use in NEA

AQA/OCR Pseudocode to Python Guide (free)

Easy Python Docs for GCSE Computer Science NEA offline Python site

1st Edition

Syntax, explanations, and examples for the NEA

James Franklin

Axsied ak'seed

Free

GCSE Computer Science (9?1) Non-Exam Assessment (NEA) Guide

for OCR J276

Examples, tips and advice on completing the NEA

1st Edition

Ceredig Cattanach-Chell

Axsied ak'seed

Axsied ak'seed

GCSE Computer Science (9?1) Non-Exam Assessment (NEA) Guide for OCR J276 by Ceredig Cattanach-Chell

Disclaimer No part of this publication has been endorsed by OCR. Material presented within the publication is an interpretation of how students can meet requirements for the non-exam assessment (NEA). This publication does not define any standard and any references to assessment are the author's and publisher's interpretation of the specification requirements. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, and no liability is assumed for damages resulting from the use of the information contained herein.

The publisher welcomes comments and suggestions regarding future editions of both this and other publications. Please contact publishing@.

Ceredig Cattanach-Chell 2017 The right of Ceredig Cattanach-Chell to be identified as the author of this Work has been asserted by them in accordance with sections 77 and 78 of the Copyright, Designs and Patents Act 1988. Apart from the permitted terms of any license purchased from the publisher, no part of this publication may be reproduced, held in any information storage or retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without permission in writing from the publisher.

ISBN: 978-1-911518-03-7

Contents

1 Non-Exam Assessment

3

Method 1: Designing with flowcharts

25

What is non-exam assessment (NEA)? What does the NEA consist of? Using the programming techniques Appropriate use of techniques Additional use of techniques Creating a challenging solution Core information Headers and footers

3 3 5 6 6 6 7 7

Method 2: Designing with pseudocode Benefits of pseudocode Creating pseudocode Formatting ideas Variables and data structures Designing a test plan Modular testing User testing Testing your success criteria

27 27 27 28 29 31 31 31 31

2 Setting Up Your Report

7

Testing for robustness Thorough testing

31 33

Use of fonts

8

Designing the user interface

34

Using font styles for headings

9

Discussing user interface features

34

Making a table of contents

10

Referencing your work

11

6 Development

36

Creating a cover page

12

Developing the solution

36

3 The Problem

13

Detailed evidence Using screenshots to support development

36 36

Sample problem

13

Refining your solution

37

Record of resources used

37

4 Analysis

14

Evidencing a development cycle

38

Creating a detailed analysis

14

Modular testing

40

Decomposition of the problem

14

Using your previous modular testing tables

40

Method 1: Using top-down decomposition

14

Testing code

40

Method 2: Grouping common themes

17

Documenting test tables and evidence

42

Method 3: Work through step by step

18

Dealing with test failure

43

Requirements specification and success criteria 18

User testing and user interface testing

44

Justifying your approaches

19

Modular evaluation

45

Discussion of testing

20

Good code maintenance

45

Real-world utility

21

Commenting

45

Creating a robust program through validation 21

Code maintenance

46

Common data entry checks

22

Variable naming

46

Use of loops in validation Importance of validation

22 22

7 Testing, Evaluation & Conclusions

48

Discussing success criteria and validation

24

Checking the completed test plan

48

Evidence log

24

Showing the solution relates to success criteria 48

Discussing unresolved issues

49

5 Design

25

Evaluation against success criteria

50

Planning the component parts

25

Final evaluation comments

51

v

Guide to the NEA

8 Guide to Techniques

52

Techniques covered

52

Creating headers and footers

52

Numbering your pages

53

Automatically creating a table of contents

54

Creating a top-down design

54

Menu options for a top-down design

55

Creating a cover page

56

vi

Introduction

About this book

This book has been written by an experienced teacher of computer science and non-exam assessment (NEA). It describes the techniques and methods which the author and publisher believe are currently best practice at the time of publication.

You may wish to use different ways to record your evidence. Marks are given for evidence that meets the mark scheme criteria, even if this is different to that recommended in this guide.

This book is not a writing framework. You are allowed to use it in the NEA itself. The book gives numerous examples of how you could evidence your work, but you will need to write your own evidence from scratch.

This book does not define any standards that may be set by OCR as these are set during the examination series for the relevant year. However, this book does show some excellent ways in which you can evidence all the criteria that are required on the mark scheme.

Features used in this book

As you go through the book, you will notice a number of features to help you.

Examples of how you can present evidence are given in a page with torn edges. You should not copy these into your NEA as they are for a different problem, but you can use them to get ideas.

These success criteria should allow a valid name to be stored and entered for the game. I have added the limit of 20 characters to the success as I think this is a sensible limit.

As you go through the book, you will notice a number of boxes.

Hint boxes give you advice that saves you time, alternative ideas or general hints.

Hint

There is nothing to stop you drawing designs by hand. Your teacher may be able to scan them in, or insert them into your submission for you. This may save you time, if you find designing these on computer is difficult.

Help boxes let you know that there is further information on how to do a technique at the end of the book.

Help

There is a guide to creating headers, footers and page numbers at the end of this book.

Important boxes give you important information and advice related to the evidence you will need.

Important

There is no requirement to complete both flowcharts and pseudocode as long as your designs are detailed and cover all the requirements. If choosing flowcharts only, you must make sure they are detailed enough to code from.

1

2 Setting Up Your Report

Setting up your report

Keeping your document clear and easy to follow is very important. Moderators will need to find evidence to support the mark your teacher gives you. Making it easy to find evidence therefore makes sense.

Core information

The following things must be included as part of your work: ?? Candidate name ?? Candidate number ?? Centre name (school) ?? Centre number ?? Assignment title ?? Component code ?? Page numbers

These pieces of information are key. You should ensure that they appear on every page of your work, or at least at the start of the report.

Headers and footers

You can choose how you lay out your headers and footers. Typically, they will look similar to one of the following examples. Example 1 - Using a header and footer

Help

There is a guide to creating headers, footers and page numbers at the end of this book.

Candidate: Emily Smith Header

Computer Science NEA Project

Candidate Number: 1234

7

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download