Things to include in your development section

In the development section should be details of the tests you have written, and the development you have completed.

You need to have tests - either performed manually, or better - automatically. The test code if you have run it automatically should be snipped using the snipping tool and put into the report.

You should also have comments in your code, and variable names should be expressive of what they are to contain.  ie use 'currency' instead of 'c'.

You need to explain the code that you use, it should be sufficient to use comments in your code, which is placed into your report.  It is also advisable to have a particular discussion on the variables you have used.  Use the table format that we used in our sorting exercise to help you.  you may need to look at https://github.com/ams-bjones/sorting for a reminder with this.

Things to include in your design section

Okay today is a pressure day - we are writing up our Reports for our A453 Controlled assessment.

A little formatting guidance - Please put in the page header your name,  center name, center number and candidate number.

Please also include the page number.

Things to include;

User requirements

These are an analysis of the task - what are you expected to produce in your development stage.  Don't try to get too clever here - read the task, and extract the things that you need to do.  Don't be afraid of using bulleted lists here.

Success Criteria

Your success criteria are questions that have True or False answers that you can test for.  Note that these should be done before you start the development section.  Again these could be in bulleted statements.  These could be in the form of test data and expected results.  ie squaring 3 should return 9.

Algorithm

Your design section should include an algorithm.  You could use pseudocode or, a flow chart, or both.

Example design section from last year, at C standard

Task Number 1:

For task 1 I have to design code and test a programme that will simulate a dice with the side numbers of 4, 6 and 12. The programme needs to output the dice outcome. There needs to be a loop to allow the user to roll the dice as many times as required. To attempt this question I will initially create a flowchart to represent the thought process behind the programme and how it will operate. To work alongside the flowchart I will also write some pseudo code. I will then research similar programmes used on scratch and represent what I’ve found in a table. After my research and my planning are completed I will start to write my code and test it.  

Success Criteria

To be successful the program should:

·      Show the dice being rolled

·      The six sided dice when being rolled 100 time should

o   Never roll a number higher than a 6

o   Never roll a 0 or below

o   Each number [1-6] should appear about the same number of times, the lowest frequency should not be less than half of the highest frequency number

o   No number should not be rolled in 100 rolls.

The same criteria apply to the other dice.

 

                          

Pseudo code:

SELECT DICE

IF DICE = 4SD

     OUTPUT “4 Sided Dice!!”outcome =”1-4 ROLL”

IF DICE = 6SD

     OUTPUT “6 Sided Dice!!”outcome =”1-6 ROLL”

IF DICE = 12SD

     OUTPUT “12 Sided Dice!!” outcome =”1-12 ROLL”

Year 10 Controlled Assessment

Its time for some controlled assessment!




This work should all be in its own repository. Please create that now.
 
Controlled Assessment is carried out under fairly direct instructions from the Exam board.  See the syllabus pages 21 - 31 for full details.

Before you start you should be aware of a few things.  Firstly what does 'controlled' mean?

The aim of the 'controlled' in 'controlled assessment' is to establish that the work you produce and turn in is your own.

To that purpose - As your teacher I have certain guidelines that I must follow, see pages 22 - 23 of the syllabus.  I am allowed to lay out the task for you, and give you fairly generic advice.  I can offer approaches and places to look for research, but I cannot help you much.  For the final part of the assignment - the writing up we will work in formal supervision.  This will be the time we are working in silence with no communication.  This will occur on Wednesday 25th June.

General advice:

Firstly remember the practice you have had, design the task first, write your test before your pseudo code, write the algorithm in pseudocode before you write your code, and keep your tests for each time you change the code.  Build it one brick at a time.

Your last unit will inform you to what you need to include. In particular consider the testing tables, and discussion of variables that we used.  You can refer to any previous work to help you with this.

Keep your work up to date, and push to Github regularly.  You should push to github at least once per lesson, and once during each home learning session.