M.B. Rosson - DeveloPassion

# M.B. Rosson Mary Beth Rosson is an American computer scientist and a leading figure in [[Human-Computer Interaction (HCI)]] and computing education research. She is Professor of Information Sciences and Technology at Penn State University, where she co-founded the HCI program with [[J.M. Carroll]]. Her most influential work, the textbook *Usability Engineering: Scenario-Based Development of Human-Computer Interaction* (2002, with Carroll), established scenario-based design as a mainstream HCI methodology and remains widely used in university courses worldwide. Rosson's research spans end-user programming, computing education, and participatory design. Before Penn State, she held positions at Virginia Tech and IBM Research, where she investigated how non-programmers create and modify software. Her work on end-user development influenced how we think about empowering users beyond consumption to creation. She has contributed extensively to understanding how people learn programming and how technology can support collaborative learning. Her research consistently emphasizes making computing accessible and meaningful to diverse populations. ## Key Contributions | Contribution | Significance | |--------------|--------------| | **Usability Engineering** (with Carroll) | Definitive scenario-based design textbook | | **Scenario-based design** | Methodology development and teaching | | **End-user programming** | Empowering non-programmers | | **Computing education** | Research on learning to program | | **Claims analysis** | Design rationale technique | | **Penn State HCI program** | Co-founder | ## Scenario-Based Design Framework ``` ┌─────────────────────────────────────────────────────────────┐ │ SCENARIO-BASED DESIGN (Rosson & Carroll) │ ├─────────────────────────────────────────────────────────────┤ │ │ │ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ │ │ ANALYZE │───▶│ DESIGN │───▶│ PROTOTYPE │ │ │ │ │ │ │ │ & TEST │ │ │ └─────────────┘ └─────────────┘ └─────────────┘ │ │ │ │ │ │ │ ▼ ▼ ▼ │ │ Problem Activity Interaction │ │ Scenarios Scenarios Scenarios │ │ │ │ │ │ │ ▼ ▼ ▼ │ │ + Claims + Claims + Claims │ │ Analysis Analysis Analysis │ │ │ │ Scenarios = Narrative descriptions of user activities │ │ Claims = Design implications with trade-offs │ │ │ └─────────────────────────────────────────────────────────────┘ ``` ## Claims Analysis | Element | Description | |---------|-------------| | **Claim** | Design feature with rationale | | **Upside** | Benefits, positive effects | | **Downside** | Costs, negative trade-offs | | **Dependencies** | Context that affects claim | ### Claims Analysis Example | Feature | Upside | Downside | |---------|--------|----------| | **Auto-save** | Prevents data loss | May save unwanted changes | | **Undo stack** | Encourages exploration | Uses memory, complex to implement | | **Tooltips** | Helps discovery | Can be intrusive | ## Research Areas | Area | Focus | |------|-------| | **Scenario-based design** | Narrative-driven design methodology | | **End-user development** | Non-programmers creating software | | **Computing education** | How people learn programming | | **Participatory design** | Users as co-designers | | **Community informatics** | Technology for communities | | **Collaborative learning** | Technology-supported learning | ## End-User Programming Research | Topic | Contribution | |-------|--------------| | **Spreadsheet programming** | Understanding informal programming | | **Web development** | End-users creating web content | | **Debugging** | How non-experts find errors | | **Reuse** | How users adapt existing code | | **Barriers** | Why non-programmers struggle | ## Career Timeline | Period | Position | |--------|----------| | 1980s | PhD, University of Texas at Austin | | 1980s-1990s | IBM Thomas J. Watson Research Center | | 1990s-2003 | Virginia Tech | | 2003-present | Penn State University | ## Major Publications | Work | Year | Co-author | |------|------|-----------| | *Usability Engineering* | 2002 | J.M. Carroll | | *Object-Oriented Design* | 1990 | - | | "Scenario-based design" | Various | J.M. Carroll | | "End-user programming" | Various | Various | ## Usability Engineering (2002) | Chapter Topic | Key Concepts | |---------------|--------------| | **Requirements analysis** | Stakeholders, field studies | | **Activity design** | Scenarios, metaphors | | **Information design** | Mental models, representations | | **Interaction design** | Affordances, feedback | | **Prototyping** | Low to high fidelity | | **Evaluation** | Usability testing, inspection | ## Teaching Contributions | Contribution | Impact | |--------------|--------| | **HCI curriculum** | Shaped university programs | | **Scenario methods** | Teachable design approach | | **Textbook adoption** | Widely used in courses | | **Student mentorship** | Trained many HCI researchers | ## Collaboration with Carroll | Joint Work | Nature | |------------|--------| | **Usability Engineering** | Co-authored textbook | | **Scenario-based design** | Co-developed methodology | | **Claims analysis** | Co-developed technique | | **Penn State HCI** | Co-founded program | | **Research projects** | Decades of collaboration | ## Design Principles (from Usability Engineering) | Principle | Application | |-----------|-------------| | **Understand users** | Fieldwork, personas, scenarios | | **Envision activities** | Activity scenarios before UI | | **Iterate** | Prototype, test, refine | | **Document rationale** | Claims capture trade-offs | | **Involve stakeholders** | Participatory methods | ## Quotes  ## Books  ## References - Rosson, M.B. & Carroll, J.M. (2002). *Usability Engineering: Scenario-Based Development of Human-Computer Interaction* - https://faculty.ist.psu.edu/rosson/ ## Related - [[J.M. Carroll]] - [[Human-Computer Interaction (HCI)]] - [[Usability]] - [[User Experience (UX)]]