itec 109 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
ITEC 109 PowerPoint Presentation
Download Presentation
ITEC 109

Loading in 2 Seconds...

play fullscreen
1 / 20

ITEC 109 - PowerPoint PPT Presentation


  • 88 Views
  • Uploaded on

ITEC 109. Lecture 2 The Process of Solving Problems. 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. Process. Define the problem Requirements engineer

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'ITEC 109' - mingan


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
itec 109

ITEC 109

Lecture 2

The Process of Solving Problems

review
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
process
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
define the problem
Define the problem
  • All may not be as it seems
guidelines
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
computers
Computers
  • Guidelines for what to build
  • Requirements engineering
  • Don’t tack it on
identify subparts of the problem
Identify subparts of the problem
  • Rome wasn’t built in a day
strategies
Strategies
  • Figure out granularity
  • Identify pieces
  • Figure out how they go together
  • Blueprints not materials list
computers1
Computers
  • Functions
  • Flow of the program
  • Tests to see if it works
create solutions
Create Solutions
  • Components
    • Lumber, nails
  • Algorithms
    • A recipe for how to create X
      • Sort a list of numbers
      • Manage communication between airplanes
computers2
Computers
  • Math
  • Building construction
  • Philosophy
solving parts
Solving Parts
  • Physical labor
  • Writing software
    • Languages
    • Testing
put parts together
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
computers3
Computers
  • Hardest part of the process
  • Slight deviations from the plan
  • Expectations gone wrong
  • Drawing board
does it work
Does it work?
  • Actual working products are important
computers4
Computers
  • Give it to the user and say do X
  • Cross fingers
  • Take notes
perspective
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
example
Example
  • Virtual Reality
  • Engine replacement
  • Application
lessons
Lessons
  • Learning tools overwhelms you
  • Easy to lose sight of big picture
  • Takes years to move up the chain
    • Work
    • Direction
review1
Review
  • Steps of problem solving
  • Unique aspects relating to computers
  • Focus is on brick laying