Quiz

1. Big Ideas:Computer ArchitectureComputing HistoryComputing CareersIS 101Y/CMSC 101Computational Thinking and DesignThursday, September 19, 2013Carolyn SeamanUniversity of Maryland, Baltimore County

2. Quiz • Individual quiz: 5 minutes • Team quiz: 5 minutes

3. Computer Architecture • Review quiz answers • Basic concepts you should know • CPU and its two parts, the controller and the ALU • Storage – different types and differences in terms of speed, capacity, volatility, and cost • Input and output • How it all works together • Questions? • Anything out of date in this chapter?

4. New Class Rule Laptops, cell phones, tablets must remain CLOSED until needed for an in-class exercise

5. From Tuesday:Exercise #1: Multiplication • Work in your team – OK to split into smaller groups of 2 or 3 when you’re at the implementation step • How would you multiply two numbers, using only the addition operator? • Understand the problem – state some examples • Write the solution in English • Test the English solution! • Write the solution in Processing • Test the program! • Concepts: iterations, efficiency

6. Multiplication exercise • Most of you probably came up with something like this: int X = 3; // try different values int Y = 5; // try different values inti; int product = 0; for (i=1; i<=Y; i++) { product = product + X; } println (product); • What if X=1 and Y=357? • How can you make it more efficient?

7. What’s the Deal With That Pesky For Loop?? for ( INIT ; TEST ; NEXT) { BODY} INIT NEXT Your for loop always, always, always must have this form – you can put different things for INIT, TEST, NEXT, and BODY, but the rest has to look just like this! TEST? yes BODY no

8. Movie Day • Computer History in 90 Seconds • Names you should be familiar with • World War II: ENIAC / “Top Secret Rosies” • So why aren’t programmers primarily women any more? • Careers in computer science • From Columbia University • Refers to CS, but Columbia doesn’t have Business Technology, IS, or Computer Engineering, so they’re really talking about Computing in general

9. Examples of Employers of UMBC Computing Majors • Booz Allen Hamilton • Northrop Grumman • Lockheed Martin • Care First Blue Cross Blue Shield • NSA • T Rowe Price • IBM • General Electric Finance Read Student Alumni Profiles at: http://www.careers.umbc.edu/profiles/ View Career Services & Shriver Calendar at: http://www.careers.umbc.edu/news_events/calendar.php

10. “Big Chunks” of the Computing Discipline • Software • How to get machines to do things • Majors: primarily Computer Science • Careers: Software Engineer, Software Architect, Programmer • Hardware • How to build machines that do things • Majors: primarily Computer Engineering • Careers: Electrical Engineer, Technician, Hardware Designer • Networks • How to enable people to communicate, tasks to be coordinated, and information to be shared • Majors: Computer science and Information systems • Careers: Network administrator, Network designer • Systems Analysis • How people and organizations can best use IT to get stuff done • Majors: Information systems and Business Technology Administration • Careers: Systems Analyst, Business Analyst, IT consultant, IT manager, CIO • Quality Assurance • Make sure a new system works and is useful • Majors: Information systems and Business Technology Administration • Careers: QA Manager, Tester, IT manager • Data • How to organize and manage data in the most efficient and useful way possible • Majors: Information Systems and Computer Science • Careers: Database Administrator, Database Designer • Applications • All of the above applied to specific areas of society • Security, intelligence, health care, games, graphics, business, etc.

11. A systems view of careers • What can you do with a system? • Envision it • Decide what it will do • Teach it • Design it • Build it • Build parts of it • Test it • Make it better • Configure and tailor it • Use it • Keep it going

12. A systems view of careers • What can you do with a system? • Envision it • Decide what it will do • Teach it • Design it • Build it • Build parts of it • Test it • Make it better • Configure and tailor it • Use it • Keep it going BTA

13. A systems view of careers • What can you do with a system? • Envision it • Decide what it will do • Teach it • Design it • Build it • Build parts of it • Test it • Make it better • Configure and tailor it • Use it • Keep it going IS

14. A systems view of careers • What can you do with a system? • Envision it • Decide what it will do • Teach it • Design it • Build it • Build parts of it • Test it • Make it better • Configure and tailor it • Use it • Keep it going CMSC

15. A systems view of careers • What can you do with a system? • Envision it • Decide what it will do • Teach it • Design it • Build it • Build parts of it • Test it • Make it better • Configure and tailor it • Use it • Keep it going CMPE

16. A process view of careers Problem Identification Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

17. A process view of careers IS, BTA Problem Identification Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

18. A process view of careers IS Problem Identification Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

19. A process view of careers IS, CMSC, CMPE Problem Identification Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

20. A process view of careers Problem Identification CMSC, CMPE Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

21. A process view of careers Problem Identification CMSC, CMPE, IS Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

22. A process view of careers Problem Identification IS, BTA Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

23. A process view of careers Problem Identification CMSC, CMPE, IS, BTA Analysis Design SDLC: Systems Development Lifecycle Implementation Testing Installation Maintenance

24. A component view of careers • Systems are comprised of: Hardware People void setup () { size (500, 500); smooth (); //Array of Squares for (inti=0; i<button.length; i++) { button[i] = new SquaresArray (200, 200, 20); } } Networks Software

25. A component view of careers • Systems are comprised of: BTA, IS Hardware People void setup () { size (500, 500); smooth (); //Array of Squares for (inti=0; i<button.length; i++) { button[i] = new SquaresArray (200, 200, 20); } } Networks Software

26. A component view of careers • Systems are comprised of: Hardware People IS, CMSC void setup () { size (500, 500); smooth (); //Array of Squares for (inti=0; i<button.length; i++) { button[i] = new SquaresArray (200, 200, 20); } } Networks Software

27. A component view of careers • Systems are comprised of: Hardware People void setup () { size (500, 500); smooth (); //Array of Squares for (inti=0; i<button.length; i++) { button[i] = new SquaresArray (200, 200, 20); } } CMSC Networks Software

28. A component view of careers • Systems are comprised of: CMPE Hardware People void setup () { size (500, 500); smooth (); //Array of Squares for (inti=0; i<button.length; i++) { button[i] = new SquaresArray (200, 200, 20); } } Networks Software

29. The Point • Each of you has declared a major of BTA, IS, CMSC, or CMPE • You can change your major • It’s better to change your major sooner rather than later • We want to help you make the right choice for you • If we do our jobs, you’ll have a much clearer idea of what major you want, what you can do with it, and why it’s right for you

30. Project Teams Get into your new teams and come up with answers to these questions: • Find one thing that you all have in common (other than being in this class. • Find one thing that’s different for all of you (other than having different names) • Pick a team name. (Maybe the answers to #1 and #2 will inspire you.) NOTE: For this and other team activities, any team member may be asked to present the answer to any question!