We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17
T he P
roces s of Progr Execu a m tion Com. Prog. About Program
• The most important person involves in this
module is the computer programmer. He creates instructions that tells the computer what to do by writing and testing code that allows applications and software programs to operate successfully. Process of program execution are the following: Define the problem to solve Design a solution Draw a flowchart Create a pseudo-code Write the program Test the program Document the program I. Define the Problem • A programmer creates program to solve a problem. So, it is very important to know first the problem to work on. And also, the requirements of the client on how it will appear, display, and work. Another thing to consider is the ability of the end users to operate the program. III. Draw a Flowchart • A flowchart is a pictorial representation of a sequential process of a program to solve a problem. It comprises of arrows for the direction, boxes and other symbols representing actions. It serves as a map of the program on what and how to do it. This will be discussed in the future module. IV. Create a Pseudo-code • Pseudocode is an English-like nonstandard language used in informal way of programming description that does not require any strict programming language syntax or underlying technology considerations. IV. Create a Pseudo-code • It is used for creating an outline or a rough draft of a program. Pseudocode summarizes a program’s flow, but excludes underlying details. It permits the programmer to focus on the program logic without having to be concerned about the precise syntax of a particular programming language. However, pseudocode is not executable on the computer. V. Write/Code the Program • In writing or coding a program, the programmer will use his chosen programming language. There are many programming languages: BASIC, COBOL, FORTRAN, and C are some examples. • On this stage, the programmer has to sit and type the command lines of a program. Coding is the act of translating the design into an actual program, written in some form of programming language. It is like writing an essay. And, like essays, there are things needed to include in the program such as titles, introductions, references etc.). VI. Test the Program • In writing or coding a program, the programmer will use his chosen programming language. There are many programming languages: BASIC, COBOL, FORTRAN, and C are some examples. 1. Desk-checking • This phase is similar to proofreading that sometimes avoided by the programmer who looks for a shortcut and eager to run the program on the computer once it is written. With careful desk-checking you may discover several errors and possibly save time in the long run. 2. Compiling • Compilation is the process of turning the program written in some programming language into the instructions made up of 0's and 1's that the computer can actually follow. • Compilers are translators that can read a programming language, translate it and write out the corresponding machine code. A translator is a program that (1) checks the syntax of your program to make sure the programming language was used correctly, giving you all the syntax-error messages, called diagnostics, and (2) then translates your program into a form the computer can understand. • (Different translators may provide different wording for error messages.) The translation involves your original program, called a source module, which is transformed by a compiler into an object module. 3. Debugging • Debugging is the process of detecting and removing of existing and potential errors (also called as ‘bugs’) in a software code that can cause it to behave unexpectedly or crash. To prevent incorrect operation of a software or system, debugging is used to find and resolve bugs or defects. VII. Document the Program • Documentation is a written detailed description of the programming cycle and specific facts about the program. Typical program documentation materials include the origin and nature of the problem, a brief narrative description of the program, logic tools such as flowcharts and pseudocode, data-record descriptions, program listings, and testing results.