Interaction design for complex problem solving developing useful and usable software
Software for complex problem solving can dazzle people with advanced features and alluring visuals, but when actually put to use it often disappoints and even frustrates users. This software rarely follows the user's own work methods, nor does it give people the degree of control and choice th...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
San Francisco, CA : Oxford :
Morgan Kaufmann ; Elsevier Science
c2004.
|
| Edición: | 1st edition |
| Colección: | Morgan Kaufmann series in interactive technologies.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627160906719 |
Tabla de Contenidos:
- Front Cover; Interaction Design for Complex Problem Solving: developing useful and usable software; Copyright Page; TABLE OF CONTENTS; Preface; 1. Introductory Quotations; 2. What is in This Book?; 3. How is This Book Organized?; 4. Who Should Read This Book?; 5. Acknowledgements; References; Introduction; 1. What is Complex Problem Solving?; 2. Designing for Usefulness in the Whole Product; 3. Putting Usefulness in the Center of Usability and Software Engineering; 4. Where Does Interaction Design Come in?; 5. How far Along are We and are Useful Applications Possible?; 6. Setting the Stage
- ReferencesPART I: UNDERSTANDING THE WORK; Chapter 1. What Makes Complex Problem Solving Complex?; 1. Scenario: Should We Break Into a New Market Niche?; 2. Describing Contexts and Conditions Shaping Complex Problem Solving; 3. Identifying Dynamics and Traits of Complexity and Design Implications; 4. Conclusion: Revisiting Marty and the Software Support He Needs; References; Chapter 2. Usefulness: Focusing on Inquiry Patterns, Task Landscapes, and Core Activities; 1. Defining Usefulness; 2. Focusing on complex Problem Solving at a Practical Level
- 3. What is the Difference Between Inquiry Patterns and Design Patterns?4. Scenario: Analyzing the Root Causes of a Drug Overdose; 5. Summarizing Patterns of Inquiry and Task Landscapes in the RCA Case; 6. Focusing on Core Activities within Task Landscapes; 7. Focusing on Problem Solving Objectives for Core Activities; 8. Conclusion: Higher-Order Needs Versus Support Delivered; References; Chapter 3. Filling in the Gaps: Integrating Usefulness Into User-Centered Design; 1. Understanding and Re-Thinking Assumptions; 2. Gathering Data About Users and Their Work
- 3. Analyzing and Synthesizing Data4. Modeling Users' Work; 5. Conceptualizing Designs; 6. Conclusions: Putting it Together; References; PART II SOLVING PROBLEMS IN TECHNICAL, SOCIAL, AND CO-EMERGENT SYSTEMS; Chapter 4. Keeping the System Up and Running; 1. Scenario: Crisis in a Corporate Network; 2. Design Team Scenario: Analyzing and Modeling Contextual Data; 3. Design Team Scenario: Conceptualizing Design; 4. Designing Differently: Creating Integrated and Consolidated Models; 5. Designing Differently: Capturing Contextual Influences; 6. Conclusions; References; Chapter 5. Getting IT Right
- 1. Prelude to a Story: Looking at Only Select Parts of the Team's Efforts2. Introduction: Re-Grouping and Deciding How to Re-Design; 3. Analyzing What Troubleshooters Do to Validate a Problem; 4. Analyzing What Troubleshooters Do Validate a Problem; 5. Analyzing What Troubleshooters Do to Bound and Formulate a Problem; 6. Conceptualizing Designs for Saving, Commenting on and Recalling Views; 7. Conceptualizing Designs for Finding an Entry Point; 8. Conclusions; References; Chapter 6. Criteria, Constraints, and Choices: Optimizing the Mix in Merchandising; 1. Solving Product Mix Problems
- 2. Scenario: Deciding the Best Mix of Shortening and Oils for a Western Chain
