1 / 27

Reminders

Data: Programming Design and Modularization IS 101Y/CMSC 101 Computational Thinking and Design Tuesday, September 24, 2013 Carolyn Seaman University of Maryland, Baltimore County. Reminders. Send me your team name!! Processing Assignment #2 Due BEFORE class on Thursday

obelia
Télécharger la présentation

Reminders

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. Data: Programming Design and ModularizationIS 101Y/CMSC 101Computational Thinking and DesignTuesday, September 24, 2013Carolyn SeamanUniversity of Maryland, Baltimore County

  2. Reminders • Send me your team name!! • Processing Assignment #2 • Due BEFORE class on Thursday • Both electronic and paper submissions • Friday office hours • Grades • Quiz grades – secret to increasing them • Checking on Blackboard

  3. 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

  4. 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

  5. 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

  6. 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

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

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

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

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

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

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

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

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

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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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

  22. Semester Game • Basic scenario • Player makes choices about how to allocate time in each of 15 weeks • Game simulates outcomes • Possible choices for outcomes • Happiness • Grades • Wealth • Possible choices for time (for 168 total hrs/wk) • Going to class • Paying attention during class • Leisure activities (solitary and with others) • Studying alone • Working • Study in groups • Visiting academic resources • Self care (sleeping, eating, exercising, etc.)

  23. Modeling Exercise 1 • In your group, discuss the following choice: • Hours spent studying and working on assignments by yourself • For this choice, • Specify a reasonable range (might depend on number of credits taken this semester) • Model the effect on each outcome with a mathematical rule • E.g. “for each hour spent over 100, happiness goes down by 5%” or “for each hour spent, grades go up by 50%” • Be prepared to share your model and argue why it is superior to other models.

  24. Competing models for hours spent studying… • For every hour over 22, happiness goes down 12% and grades go up 2% • For every hour over 3 per day, happiness goes down 15% • For every hour over 24.5 per week, happiness goes down 1.05% • For every hour, happiness goes down .7% and grades go up 2.3% • For every hour over 4 per day, happiness goes down 11% and grades go up 3% • Reasonable range 10-15 hrs per week • For every hour over 15, happiness goes down 5% and grades go up 2%

  25. Initial rules

  26. Modeling Exercise 2 • In your group, discuss two of the choices in the game (you’ll be assigned two) • For this choice, • Specify a reasonable range (might depend on other variables) • Model the effect on each outcome with an equation • Look at the initial rule for inspiration, but don’t be bound by it • Be prepared to report out your model and argue why it is superior to the initial rule.

  27. Semester Project • Highlights • Implement the Semester Game in Processing • Five deliverables • Completed with your project team • Individual contributions and grading • We’ll be working on some pieces of the project in class • We started today • I’ll post the final version of the game rules on the online schedule

More Related