 This is more of a when you design a program. When you're designing a program, these are the steps. It's almost like in reverse, where you push the output back to the top, edit the inputs in the middle, your process at the end. It looks a little different from the other way around. So right down here, so as you can see, you want to find a program to define or find how fast a car travels. If it goes 50 miles in two hours, right? To solve such a problem, you need to know the outputs first. So most programs, that's what happens first, the outputs. Think about, say, when you want to build a house, you don't just go and start building a house, right? You define, you draw the blueprint. You want to have to look like what color you need, what material you need, how big the house is, how many rooms you need. All those are the output array. You already know what you want. So that's the output process. A program is the same thing. You write a program to, say, a tic-tac-toe game. What does the interface look like? How many rows and columns you need and things like that. So that's the output process, the design process. And you want to do that first because you don't want to start coding and then suddenly, things don't match the way you want it. Of course, in a very simple program, you don't have to draw it out. You know, in your head, you can just do it very quickly. But a complex program, you need to draw out the output first. So that's that one. And then once you define the output, you know exactly what you want, then the next thing is the input. Input is like what kind of data you need, what kind of material you need to build the house. You get the resources. Once you have all the materials you need, you get all the input data you need, and then you start processing the information. And that's where the process comes into the picture. You start building right away, or you start your calculations, or creating colors, or building other objects out of that. So this is a typical process when you build a writer program. The process in part is input, process, output. Designing part is output, input, process. So if you can understand this logic, it'll make things so much simpler for you later on, you write your code. So I'm going to fall back to this two really simple concept when you write programs later. And this can be applied to the entire program itself, or to Chinese sub-programs we call functions. So we will be talking about this quite extensively throughout the course when we write functions and other sub-routines with sub-programs.