The Programming Development Life Cycle (Pdlc)
The Programming Development Life Cycle (PDLC)
Programming can be defined as the development of a solution to an identified problem, and the setting up of a related series of instructions which, when directed through the computer hardware, will produce the desired results.
The notification that there is a problem can come from a systems analyst, an end user, or management. The problem needs to be defined so that the correct solution to solve it can be a program. Once a program is written, it is correct if it does what it is supposed to do.
Before a programmer ever sits down to code (write the program, using a programming language), he will first write the program out on paper. He will then look at each line that he has written (this is called desk checking or tracing) to make sure that each line will do what is expected and that the program will achieve the desired results. Only after tracing the program and testing that the logic works, will the programmer code the program.
The formal creation process of programming is known as the PDLC, the programming development life cycle. There are seven steps to this: define, outline, develop, test, code, run, and document and maintain. These are the steps that you will take to develop your projects. As the semester progresses, we will look into these topics more in depth.
Define - to decide what real world problem is to be solved and how a program can do this. The decisions of what the program should do. Looking at the flow of the data, the form of the input and output, the process needed and the user interaction.
A defining diagram helps the programmer to see the components. If I were asked to write a program which would compute the cost per square foot of living space for a house, given the dimensions of the house, the number of stories, the size of the nonliving space, and the total cost of the land, I would know that any noun or adjective is input or output and any verb is process.
Design Diagram
|Input
Programming can be defined as the development of a solution to an identified problem, and the setting up of a related series of instructions which, when directed through the computer hardware, will produce the desired results.
The notification that there is a problem can come from a systems analyst, an end user, or management. The problem needs to be defined so that the correct solution to solve it can be a program. Once a program is written, it is correct if it does what it is supposed to do.
Before a programmer ever sits down to code (write the program, using a programming language), he will first write the program out on paper. He will then look at each line that he has written (this is called desk checking or tracing) to make sure that each line will do what is expected and that the program will achieve the desired results. Only after tracing the program and testing that the logic works, will the programmer code the program.
The formal creation process of programming is known as the PDLC, the programming development life cycle. There are seven steps to this: define, outline, develop, test, code, run, and document and maintain. These are the steps that you will take to develop your projects. As the semester progresses, we will look into these topics more in depth.
Define - to decide what real world problem is to be solved and how a program can do this. The decisions of what the program should do. Looking at the flow of the data, the form of the input and output, the process needed and the user interaction.
A defining diagram helps the programmer to see the components. If I were asked to write a program which would compute the cost per square foot of living space for a house, given the dimensions of the house, the number of stories, the size of the nonliving space, and the total cost of the land, I would know that any noun or adjective is input or output and any verb is process.
Design Diagram
|Input