In a session today we started using FLOWOL to create a digital system which was a great way to start working with a systems approach. I found Flowol a little difficult to understand at first (even thought its apparently used in primary schools!?). when looking at it purely as a set of commands I couldn't really understand what was going on or off and what input and output were relating to and what I was asking the instructions to do?
To help me figure this out I tried to apply it to physical things which helped get my head around what I was asking the programme to do. I then started to apply it to a circuit with components such as LED'S and switches (see image below). Thinking of input 1 as a switch and output as a LED ..."IS THE SWITCH ON?....YES SO TURN THE LIGHT ON.....ACTUALLY NO ITS NO SO TURN THE LIGHT OFF"
I was again pretty correct about what a systems approach meant in relation to a circuit But need to explore this further. we had a quick look at 'basic' and pickaxe programmer whoever that just seemed like a step too far for my little brain today.
To help me figure this out I tried to apply it to physical things which helped get my head around what I was asking the programme to do. I then started to apply it to a circuit with components such as LED'S and switches (see image below). Thinking of input 1 as a switch and output as a LED ..."IS THE SWITCH ON?....YES SO TURN THE LIGHT ON.....ACTUALLY NO ITS NO SO TURN THE LIGHT OFF"
I was again pretty correct about what a systems approach meant in relation to a circuit But need to explore this further. we had a quick look at 'basic' and pickaxe programmer whoever that just seemed like a step too far for my little brain today.