Designing Solutions Through Programming
Tuesday 29 March 2022 - Block 2
← previous note | most current note | next note →A little less comfortable
Content
There are two very important parts of part B. First of all, you should have very specific, well-written success criteria. These success criteria will drive your project. Your success criteria will also help you evaluate your project. In the front of your mind must be: are these success criteria clearly going to solve the problem? The second important part of part B are the diagrams you develop to describe how your solution will work. This is a time when you start to think about how your solution will work. Flowcharts are powerful tools to imagine the logic in a program. A good flowchart can easily be converted into a computer program.
Process
You must carefully link your success criteria to your research. Every success criteria should be linked to some research you have done during section A. Your diagrams should begin as overviews, or very broad generalizations of how your program works. Then you should slowly become more specific. The magic moment comes when you show a friend a diagram and they can explain (very specifically) how your program works.
When you first start creating diagrams you will find it challenging. It can be difficult to create the right level of detail and learn how to visually represent your program. This is a skill that needs practice, practice, practice.
Product
You should have:
- 5 to 9 very specific success criteria
- 5 to 9 very specific diagrams
A little more comfortable
Content
There are two very important parts of part B. First of all, you should have very specific, well-written success criteria. These success criteria will drive your project. Your success criteria will also help you evaluate your project. In the front of your mind must be: are these success criteria clearly going to solve the problem? The second important part of part B are the diagrams you develop to describe how your solution will work. This is a time when you start to think about how your solution will work. Flowcharts are powerful tools to imagine the logic in a program. A good flowchart can easily be converted into a computer program.
One of the big differences we have between more comfortable and less comfortable is the types of diagrams you make. There are many different types of diagrams, and each diagram helps us to understand a different part of your program. This is really hard to get right and takes lots of practice.
Process
You must carefully link your success criteria to your research. Every success criteria should be linked to some research you have done during section A. Your diagrams should begin as overviews, or very broad generalizations of how your program works. Then you should slowly become more specific. The magic moment comes when you show a friend a diagram and they can explain (very specifically) how your program works.
One of the differences between good success criteria and great success criteria is how tightly focused the success criteria are on solving the problem. It is also important you have challenging success criteria.
When you first start creating diagrams you will find it challenging. It can be difficult to create the right level of detail and learn how to visually represent your program. This is a skill that needs practice, practice, practice.
Product
You should have:
- 5 to 9 very specific success criteria
- 5 to 9 very specific diagrams - the more specific the better
Statement of Inquiry
The big idea for today is Design: Developing Ideas.
The essential questions for this topic are:
Every design has a success criteria which are used to build your solution to a problem.
It takes time to explore and really understand a big idea. If you want to
learn more about
design: developing ideas (which is connected to today's daily note),
please click here
.
We are learning this because as a designers must understand scientific and technical innovation. Designers use systems, models, methods, and processes to solve problems.
Standards
Develop a design specification which clearly states the success criteria for the design of a solution Develop a range of feasible design ideas which can be correctly interpreted by others Present the final chosen design and justify its selection Develop accurate and detailed planning drawings/diagrams and outline the requirements for the creation of the chosen solution
Reminders & routines:
IF (today == testing_day_for_me) {
remember to go get tested!;
}
IF (this_block == first_block_day) {
read_daily_bulletin;
}
IF (today == Friday) {
current_event_activity();
}
As I am taking attendance:
- For students who are physically at ASW: Please check now: am I connected to the American School of Warsaw wireless network
- Please check now: is visual studio code working from my programming folder?
To remember:
- All the files you need for this course can be found at this link. Please pay attention to the time the file was last updated.
- You can access a web-based view of your database by clicking this link.
- Please be aware of course videos to help you understand our content.
Our learning
This is a beta feature. Please let me know if you have any feedback.
Please click here to reflect on our learning for today's class.