Solving Complex Problems Through Programming
Monday 14 November 2022 - Block 7
← previous note | most current note | next note →Daily Note
Hello
Today we will learn about Section B of the design cycle.
I will read the more comfortable / less comfortable part of our daily notes.
- We will learn about success criteria:
- Success criteria will be very concrete
- Success criteria will be how you decide if you have been successful
- Success criteria will be directly related to the problem you are solving
- In general, you should only have 5 to 9 success criteria.
- Most of the time people don't get this right on the first try :-)
- Here is an example of success criteria:
- My application will have 10-15 recipes.
- My application will have images for every dish.
- My application will have a list of ingredients in the form of a checklist.
- My application will have the functionality to add ingredients to a cart (shopping list).
- My application will have the functionality to filter recipes by diet and the level of difficulty.
- My application will have a rating system.
- My application will have login functionality.
- My application will have register functionality.
- My application will have a logout system.
We will go through the four parts of the design cycle
- We wil register for lucid chart:
- Make sure you register using your google at ASW
- Please follow along as we create a new document, paying attention to the two different shapes we use.
- I will be conferencing with you to review your success criteria
- Please reference ACCESSFM: a tool to help us answer the question "what should my success criteria look like"
- It is very important we work through our review / reflection today as this is a new unit of instruction.
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
Our Big idea
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.
Reminders & routines:
IF (this_block == first_block_day) {
read_daily_bulletin;
}
IF (today == Friday) {
computing_careers
}
As I am taking attendance:
- Please check now: is visual studio code working from my programming folder?
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.