1 / 119

Historical Perspective

Historical Perspective. 1965. 1 Got Married 2 First Computer Course. Got Married. Got Married. Got Married. Got Married. Got Married. Got Married. Got Married. Got Married. Got Married. First Computer Course Fortran. Fortran

mayda
Download Presentation

Historical Perspective

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. Historical Perspective

  2. 1965

  3. 1 Got Married 2 First Computer Course

  4. Got Married

  5. Got Married

  6. Got Married

  7. Got Married

  8. Got Married

  9. Got Married

  10. Got Married

  11. Got Married

  12. Got Married

  13. First Computer Course Fortran

  14. Fortran Fortran was only 8 years old Already Several Versions Fortran IV

  15. One of the Big Issues How do you get the program In the computer?

  16. Historical Computing • Computers were very expensive

  17. Historical Computing • Computers were very expensive • Could only run one program a time

  18. Historical Computing • Computers were very expensive • Could only run one program a time • So one object was to get the program into the computer as fast as possible

  19. A Good Media • The Punched Card • Card Readers

  20. A Fortran Cardand Key Punch Machine

  21. IBM 7094 • Fastest Machine • .35 MIPS • 32K Memory (36 bit word) • Very Expensive

  22. IBM 7094 • Fastest Machine • .35 MIPS • 32K Memory (36 bit word) • Very Expensive • Over 3 Million Dollars

  23. Contract Programmer • Go from Job to Job • Sometimes call ourselves gypsies • Subject to technical interviews

  24. Technical Interviews • Contract programmers • Level of questions are often quite simple • Have to do a lot of technical interviews

  25. Technical Interviews • What PROC do you use for printing?

  26. Technical Interviews • What PROC do you use for printing? • What manual describes the PROCs?

  27. Once in a discussion about the quality of questions, a fellow contractor spoke up and said that the best he ever got was:

  28. Can you describe the life cycle of a software system?

  29. This fellow had just reviewed software • development methods. • And answer was: Yes

  30. Needs analysis Systems analysis System design Unit design Unit coding Subsystem coding System coding System acceptance

  31. Needs analysis Systems analysis System design Unit design Unit coding Subsystem coding System coding System acceptance Then it goes forever into maintenance

  32. WOW

  33. That is what you might do for a Huge System • With dozens of pages of documentation • If not hundreds

  34. That is not what we are doing today! • For a small ad hoc program • ONE sheet (keep it simple)

  35. Needs analysis Analysis Design

  36. The Request • Usually an email • Stating what the requestor wants

  37. The Request – part 1 • The Marketing Group is planning to do a telephone survey to determine the interest level for using solar as part of an individual household electrical supply. Needed is a sample of 10,000 customers meeting for following qualifications:

  38. The Request – part 2Qualifications • Residential • Household income of at least $75,000 • Monthly power usage of at least 2500 Kwh • Live in the metro area

  39. The Request – part 3 • Needed for each person in the sample: Name Address Telephone number Age Solar user

  40. I build single sheet starting with three columns • Item number • Flag • User request

More Related