Thursday, 23 October 2014

Specifications and Broken Programs

Today we started off with probably the hardest quiz on the planet. The questions required someone with eagle eye vision at the very least. I achieved a score of three and one third which fortunately means I don't have to do the quiz next week because I'm just that good.

We then moved on to working in groups to try and come up with flow charts, pseudo code and specification for a greenhouse that must be kept at twenty eight degrees throughout the day. I felt this task went very well because our team successfully came up with a good specification a flow chart that was wrong but none the less a flow chart and some pseudo code that was wrong as well. Personally I felt we should have won because of the amazing team name called "One wheel short of a unicycle" I came up with this name so credit goes to me.

We then moved on to looking at the scenario for assignment three which is to come up with a program that adds up the cost of painting a room. I felt that the scenario made sense but the coding part will make my head explode when we begin to code it after half term.

Finally we came up with our own specifications from this scenario and we categorised them into output, input, assumptions and process. I felt this task was easy because it was essentially matching up information with the categories mentioned above.

Overall today was a good day because the work wasn't overly complicated and I got to work in a group which does not happen very often. I enjoyed the team work aspect of the day the most because it means I can get help from fellow team mates when stuck with a task. I least enjoyed looking at the scenario because it just made me panic about the assignment and how much coding has to be done.      

No comments:

Post a Comment