1 / 28

ICS 131: Social Analysis of Computerization

ICS 131: Social Analysis of Computerization. Lecture 6: Social Aspects of Technical Issues - Software Packages. Announcements. Discussion sections today and Friday. If you are in the Monday section, you are encouraged to attend section today or Friday. Add Cards.

Jimmy
Télécharger la présentation

ICS 131: Social Analysis of Computerization

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. ICS 131: Social Analysis of Computerization Lecture 6: Social Aspects of Technical Issues - Software Packages

  2. Announcements • Discussion sections today and Friday. • If you are in the Monday section, you are encouraged to attend section today or Friday.

  3. Add Cards • Last check, 137 people enrolled • 47 Mon, 44 Wed, 48 Fri • I can sign a few add cards at the end of class if anyone needs signatures.

  4. Discussion Section • Make sure you are enrolled in one of the three discussion sections. • At least two people in this class are not registered for lecture, but only for section.

  5. First set of short assignments • Should be ready for pickup today.

  6. Feedback on first set of short assignments • On the whole, good. • Most people turned in all of the summaries, and had the requested content. • Biggest problem was with the summaries - not just rephrasing of abstract/conclusion • Also, make sure to tie second paragraph back to the reading (rather than “This reminded me of a weird looking dog I saw this morning. Wow, was it weird looking. Is that 150 words yet?”) • Technical points - staple the papers, have the summaries in the correct order, spell check first

  7. Negroponte Reading • If you turned in the Negroponte last Friday, please turn it in again on Friday. Since we’ll be grading it next week, if you don’t turn it in on Friday, you won’t get credit.

  8. General Questions? • Also, specific questions can be asked in the discussion section.

  9. Key Ideas • Many factors affect how people use software packages beyond the functionality of the software itself. • Understanding these additional factors can help you make software that works well (and is used a lot.)

  10. How today is different from the lecture on code (a week ago)… • The code lecture was about how/why people write code. • This lecture is about how/why people use code.

  11. Trying something vs. adoption • Factors that influence how someone first undertakes a certain behavioral pattern (such as software use) do not correlate fully with factors that determine whether or not that behavioral pattern becomes habitual.

  12. Factors that Affect Whether People Try a Software Package • Advertising • Word of Mouth • Expected Functionality • Social Implications

  13. Advertising • Learning about it from TV/Radio/Product Placement/magazines/etc. • Good part - expose willing purchasers to content that will make their lives easier/better. • Bad part - paid for by companies who are legally obligated to increase shareholder value, rather than to make purchasers lives easier/better.

  14. Word of Mouth • Learning about something from friends, family, etc. • Good part - trusted source, first-hand experience • Bad part - Limited scope, since people only share what they already know with people they already know. (Works fairly well coupled with people’s exploration of software functionality.)

  15. Expected Functionality • Derived from advertising, word of mouth, packaging. • Good part - helps people use things the right way • Bad part - Largely limited by what people already know or can learn in 30 seconds or less.

  16. Social Implications • Will this make me cool/efficient/effective? • Will it allow me to integrate with other people like me?

  17. Access • Is it in the right language? • Is it made for the correct platform/OS? • Can I afford it? • Do I have the necessary capabilities (net, etc.) • Is it available for purchase near me? • Can I try a demo?

  18. Compatibility • With other software • With other aspects of lifestyle

  19. Adoption • Many of the same factors apply again here, but also… • Usability • Functionality • Unexpected Benefits

  20. Usability • Can I get things done in an efficient and enjoyable manner? • Design - Herbert Simon - producing preferred situations (is it better than the old way?)

  21. Functionality • Is the real functionality as good as (or better than) the expected functionality?

  22. Unexpected Benefits • E.g., Roomba as cleaning partner

  23. Startup Cost of a New Technology • Both a barrier to adoption and a cause of irrational persistence.

  24. Combining software packages • Source of originality/complexity • Suites - made to work together

  25. Readings • Global problems vs. local problems

  26. Topic for Discussion • Pick a software package of your choice. • Question: • Aside from functionality, what factors of that software influence its distribution and adoption? • Discuss with neighbors - 5 minutes.

  27. Today’s guest speakers are... • Baniani, Borzoo • Hill, David Lancing • Min, Kyunghwan • Chan, Chi Fai • Teoh, Andrew Yu-king • Kim, Jason Minjae • Delapp, Ryan Lee • Chiang, Benjamin …come on down front!

  28. Next class • Social Aspects of Technical Questions - Networking • Readings: Watts, Greenhouse • Second Set of Reading Summaries due!

More Related