So the million dollar question for this feedback is: Did I understand the algorithm through your flowchart?
The group flowcharts are obviously easier to understand than the individual flowchart because there's a big difference in complexity between explaining a concept and explaining a complete piece of program.
But overall, I get the point of the individual flowchart too, even though it had lots of blocks and arrows pointing at each other. But there are some "lacks" in this flowchart: like at "GAME OVER", how come it doesn't just go to "End game" but also goes to "Is the spaceship on the screen"? I got a little confused since it looks like the game starts over again when game's over? But then it should be connected to the "Reset" blocks?
I also got a little confused at the "pick one of the five levels". Since it was a rhombus I assumed that it would have a yes and no arrow pointing toward something else, but it didn't. Contradictively it had an arrow pointing into itself(maybe it should have been a parallelogram since there's no true/false decision and it can be seen as a kind of input. But I also understand why it's a rhombus because it's a decition the user makes... ).
And because of the arrow going into the rhombus I then started to look at what was pointing to it, and thus skipped a couple of blocks and read a bit of the flowchart backwards.... It sort of ruined the flow 😓
But it's hard to make a flowchart simple and understandable by others. It's a constant ballance between simplicity and complexity - an abstraction of the program - and at the same time keeping your tongue in your mouth (such a good Danish expression that doesn't sound as good in English!) and having a good overview of the flowchart.
BUTT the important thing is, that I understood the overall elements in the program by just looking at the flowchart. So you did a good job! And I hope some of my confusions can help you make a better flowchart in your final project! 😉
I also do miss your take on the reflection of algorithm and flowcharts in a cultural context... It could maybe something about how abstraction is fundamental in flowcharts and also algorithms, and how that has consequences on how we percieve the world and blah blah blah...?
So the million dollar question for this feedback is: Did I understand the algorithm through your flowchart?
The group flowcharts are obviously easier to understand than the individual flowchart because there's a big difference in complexity between explaining a concept and explaining a complete piece of program. But overall, I get the point of the individual flowchart too, even though it had lots of blocks and arrows pointing at each other. But there are some "lacks" in this flowchart: like at "GAME OVER", how come it doesn't just go to "End game" but also goes to "Is the spaceship on the screen"? I got a little confused since it looks like the game starts over again when game's over? But then it should be connected to the "Reset" blocks?
I also got a little confused at the "pick one of the five levels". Since it was a rhombus I assumed that it would have a yes and no arrow pointing toward something else, but it didn't. Contradictively it had an arrow pointing into itself(maybe it should have been a parallelogram since there's no true/false decision and it can be seen as a kind of input. But I also understand why it's a rhombus because it's a decition the user makes... ). And because of the arrow going into the rhombus I then started to look at what was pointing to it, and thus skipped a couple of blocks and read a bit of the flowchart backwards.... It sort of ruined the flow 😓
But it's hard to make a flowchart simple and understandable by others. It's a constant ballance between simplicity and complexity - an abstraction of the program - and at the same time keeping your tongue in your mouth (such a good Danish expression that doesn't sound as good in English!) and having a good overview of the flowchart.
BUTT the important thing is, that I understood the overall elements in the program by just looking at the flowchart. So you did a good job! And I hope some of my confusions can help you make a better flowchart in your final project! 😉
I also do miss your take on the reflection of algorithm and flowcharts in a cultural context... It could maybe something about how abstraction is fundamental in flowcharts and also algorithms, and how that has consequences on how we percieve the world and blah blah blah...?