1 / 141

CS0004: Introduction to Programming

CS0004: Introduction to Programming. Problem Solving and Programming Tools. Review. Machine Language. Review. Machine Language is a system of instructions and data executed directly by a computer's central processing unit . Review.

yehudi
Download Presentation

CS0004: Introduction to Programming

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS0004: Introduction to Programming Problem Solving and Programming Tools

  2. Review • Machine Language

  3. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit.

  4. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages

  5. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand.

  6. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming

  7. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming is a paradigm in which the flow of programs are determined by events.

  8. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming is a paradigm in which the flow of programs are determined by events. • A program

  9. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming is a paradigm in which the flow of programs are determined by events. • A program is a collection of instructions.

  10. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming is a paradigm in which the flow of programs are determined by events. • A program is a collection of instructions. • A compiler

  11. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming is a paradigm in which the flow of programs are determined by events. • A program is a collection of instructions. • A compiler is a computer program that translates high-level language such as VB in Machine Language.

  12. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming is a paradigm in which the flow of programs are determined by events. • A program is a collection of instructions. • A compiler is a computer program that translates high-level language such as VB in Machine Language. • Running a program

  13. Review • Machine Language is a system of instructions and data executed directly by a computer's central processing unit. • Higher-Level Languages consists of instruction that people can understand. • Event-driven programming is a paradigm in which the flow of programs are determined by events. • A program is a collection of instructions. • A compiler is a computer program that translates high-level language such as VB in Machine Language. • Running a program is executing the instructions given a program.

  14. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages.

  15. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages. • Namely, 3 things:

  16. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages. • Namely, 3 things: • Takes in data

  17. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages. • Namely, 3 things: • Takes in data • Manipulates the data

  18. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages. • Namely, 3 things: • Takes in data • Manipulates the data • Produces some information

  19. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages. • Namely, 3 things: • Takes in data • Manipulates the data • Produces some information • If you can break a problem down into these steps, you can create a program to solve it.

  20. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages. • Namely, 3 things: • Takes in data • Manipulates the data • Produces some information • If you can break a problem down into these steps, you can create a program to solve it. • But do we start writing code as soon as we run into a problem?

  21. Programming Languages and Problem Solving • In this class we will be using Visual Basic, but there are many things it shares with most programming languages. • Namely, 3 things: • Takes in data • Manipulates the data • Produces some information • If you can break a problem down into these steps, you can create a program to solve it. • But do we start writing code as soon as we run into a problem? • Answer: No.

  22. Algorithms vs. Programs • An Algorithm is

  23. Algorithms vs. Programs • An Algorithm is a step-by-step procedure devised for the purpose of taking in data and producing the correct output.

  24. Algorithms vs. Programs • An Algorithm is a step-by-step procedure devised for the purpose of taking in data and producing the correct output. • A program is the actual implementation of an algorithm in a programming language.

  25. Algorithms vs. Programs • An Algorithm is a step-by-step procedure devised for the purpose of taking in data and producing the correct output. • A program is the actual implementation of an algorithm in a programming language. • Before writing a program, you must develop an algorithm to solve a problem.

  26. Algorithms vs. Programs • An Algorithm is a step-by-step procedure devised for the purpose of taking in data and producing the correct output. • A program is the actual implementation of an algorithm in a programming language. • Before writing a program, you must develop an algorithm to solve a problem. • Very Important: It is highly recommended to think about the problem first, then develop an algorithm, then write the program.

  27. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps:

  28. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps: • Analyze the problem

  29. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps: • Analyze the problem • Plan a solution

  30. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps: • Analyze the problem • Plan a solution • Design an interface

  31. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps: • Analyze the problem • Plan a solution • Design an interface • Write the code

  32. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps: • Analyze the problem • Plan a solution • Design an interface • Write the code • Test and debug

  33. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps: • Analyze the problem • Plan a solution • Design an interface • Write the code • Test and debug • Document the program

  34. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps • Analyze the problem • Plan a solution • Design an interface • Write the code • Test and debug • Document the program • (Not done in this class) Maintain the program

  35. Program Development Cycle • When Developing a program in both the real world AND in this class, there are 6 steps • Analyze the problem • Plan a solution • Design an interface • Write the code • Test and debug • Document the program • (Not done in this class) Maintain the program • To be successful in this class, you must perform each of these steps.

  36. Analyze the Problem • Understand what the problem is and what the solution should be

  37. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do.

  38. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User –

  39. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User – Anyone who uses the program.

  40. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User – Anyone who uses the program. • End User –

  41. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User – Anyone who uses the program. • End User – The person whom the program was designed for him/her to use.

  42. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User – Anyone who uses the program. • End User – The person whom the program was designed for him/her to use. • Also keep in mind what the CORRECT solution to the problem is.

  43. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User – Anyone who uses the program. • End User – The person whom the program was designed for him/her to use. • Also keep in mind what the CORRECT solution to the problem is. • This needs to be done before ANY of the following steps can take place.

  44. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User – Anyone who uses the program. • End User – The person whom the program was designed for him/her to use. • Also keep in mind what the CORRECT solution to the problem is. • This needs to be done before ANY of the following steps can take place. • People have this job in real life: http://en.wikipedia.org/wiki/Software_analyst

  45. Analyze the Problem • Understand what the problem is and what the solution should be • Keep in mind what the End User should be able to see and do. • User – Anyone who uses the program. • End User – The person whom the program was designed for him/her to use. • Also keep in mind what the CORRECT solution to the problem is. • This needs to be done before ANY of the following steps can take place. • People have this job in real life: http://en.wikipedia.org/wiki/Software_analyst

  46. Plan a Solution • Once you understand the problem, you can develop an algorithm.

  47. Plan a Solution • Once you understand the problem, you can develop an algorithm. • Create precise steps for the entire flow of the program. Usually in the form of:

  48. Plan a Solution • Once you understand the problem, you can develop an algorithm. • Create precise steps for the entire flow of the program. Usually in the form of: • Get Input

  49. Plan a Solution • Once you understand the problem, you can develop an algorithm. • Create precise steps for the entire flow of the program. Usually in the form of: • Get Input • Validate Input

  50. Plan a Solution • Once you understand the problem, you can develop an algorithm. • Create precise steps for the entire flow of the program. Usually in the form of: • Get Input • Validate Input • Manipulate Input

More Related