1 / 20

Mastering the Problem Solving Process: Steps, Strategies, and the Role of Computers

This lecture explores the comprehensive process of solving problems, emphasizing key steps such as defining the problem, identifying subparts, and solving each component methodically. We discuss the significance of utilizing computers in problem-solving and highlight the characteristics of effective problem solvers. Various strategies and guidelines are shared to assist in the breakdown and resolution of complex issues. Key aspects of requirements engineering, testing, and collaboration are also examined to ensure successful solution implementation and user satisfaction.

mingan
Télécharger la présentation

Mastering the Problem Solving Process: Steps, Strategies, and the Role of Computers

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. ITEC 109 Lecture 2 The Process of Solving Problems

  2. Review • What are the steps of the problem solving process? • Why do we use computers to solve problems? • What is one hallmark of a good problem solver? • Lab

  3. Process • Define the problem • Requirements engineer • Identify subparts of the problem • Figure out how to solve each part • Solve each part • Put the parts together • See if you did it right

  4. Define the problem • All may not be as it seems

  5. Guidelines • Define what the problem is and isn’t • Walkthrough or flow-chart • Define what a successful solution is • Goal: Not having to come back and ask questions about the problem • Is ok to show progress

  6. Computers • Guidelines for what to build • Requirements engineering • Don’t tack it on

  7. Identify subparts of the problem • Rome wasn’t built in a day

  8. Strategies • Figure out granularity • Identify pieces • Figure out how they go together • Blueprints not materials list

  9. Computers • Functions • Flow of the program • Tests to see if it works

  10. Create Solutions • Components • Lumber, nails • Algorithms • A recipe for how to create X • Sort a list of numbers • Manage communication between airplanes

  11. Computers • Math • Building construction • Philosophy

  12. Solving Parts • Physical labor • Writing software • Languages • Testing

  13. Put Parts Together • Large projects can’t be done in one fell swoop • Dozens of peoples work have to be put together • Some, but not considerable practice here at RU

  14. Computers • Hardest part of the process • Slight deviations from the plan • Expectations gone wrong • Drawing board

  15. Does it work? • Actual working products are important

  16. Computers • Give it to the user and say do X • Cross fingers • Take notes

  17. Perspective • Can’t be an architect on Day 1 • Start with the basics • Become a brick layer (Solving parts) • Be aware of the higher layers • Observe and learn • Find your niche

  18. Example • Virtual Reality • Engine replacement • Application

  19. Lessons • Learning tools overwhelms you • Easy to lose sight of big picture • Takes years to move up the chain • Work • Direction

  20. Review • Steps of problem solving • Unique aspects relating to computers • Focus is on brick laying

More Related