Robust Beefy Program!

Today was an eventful and thriving Monday!

For starters, "Jovial John" challenged all of us to do a game called "countdown" where we select random big and small numbers, then using basic maths skills to try and reach a randomly generated number. I used to do these everyday was I exceptionally fast, but I did not get as close to the numbers as other people did. This was a good wake-up exercise since Mondays are madness.

Next, we did a programming test consisting of 14 questions. The questions were about what we had learnt previously in this unit overall. I found all of the questions easy as I unexpectedly had a good memory for all of these information. However, I worded some questions differently and as a result I got a total of 11 and a 1/2 marks out of 14 due to my use of English. This was a good exercise as it wakes us up as well as allows us to refresh our minds. A way I can improve is to use more keywords than descriptive when answering a question.

Afterwards, "Jovial John" discussed with us the criteria of A3 and mentioned some issues that the Level 2 had encountered previously, this is to allow us to avoid the same mistakes in future. Furthermore, "Jovial John" also wrote down a list of everything we need to have done by tomorrow for hand in. This includes:

A3T1:

• Flowcharts (.png)
• Mindmaps (.pdf)
• Pseudocode, including justification for data types and code structures.

A3T2:

• Painted Program (.exe)
• Painted Program (.sb)
• Copy of Painted Program Code (.docx)
• Evidence of Testing (.docx or .exls)

Moving on towards the day, I ticked off everything from A3T1 and firstly began to improve the readability and quality of code for my program in A3T2. I made the measurements of the walls and windows more specific using the math.round function. Moreover, I also got other people to test my program and try and break it. As a result, I had some minor errors, which I amended quickly. Additionally, I improved the quality by replacing my 'Goto' statements to 'Sub' routines, this makes it easier for the user to read.

I plan to continue to make my program even more robust by increasing validation and looking for small errors within the program at home. I will also try to complete the excel spreadsheet to show evidence for the testing of my program.