Book Image

Learn Human-Computer Interaction

By : Christopher Reid Becker
Book Image

Learn Human-Computer Interaction

By: Christopher Reid Becker

Overview of this book

Human-Computer Interaction (HCI) is a field of study that researches, designs, and develops software solutions that solve human problems. This book will help you understand various aspects of the software development phase, from planning and data gathering through to the design and development of software solutions. The book guides you through implementing methodologies that will help you build robust software. You will perform data gathering, evaluate user data, and execute data analysis and interpretation techniques. You’ll also understand why human-centered methodologies are successful in software development, and learn how to build effective software solutions through practical research processes. The book will even show you how to translate your human understanding into software solutions through validation methods and rapid prototyping leading to usability testing. Later, you will understand how to use effective storytelling to convey the key aspects of your software to users. Throughout the book, you will learn the key concepts with the help of historical figures, best practices, and references to common challenges faced in the software industry. By the end of this book, you will be well-versed with HCI strategies and methodologies to design effective user interfaces.
Table of Contents (17 chapters)
1
Section 1 - Learn Human-Computer Interaction
5
Section 2 - How to Build Human-Centered Software
11
Section 3 - When to Improve Software Systems

Iterating software solutions

As we discussed, HCI is an iterative practice and the prototypes we have built up to this point are a reflection of the idea that design can be altered over time for the better. Fundamentally, this is why we do user testing. If we thought our ideas and software solutions were perfect and solved all our user's problems with no issues, we would skip all this work. However, that is not how the real world works. Software is very risky, as we have already discussed, and therefore we take all the precautions we can throughout the process to decrease the risk. HCI software prototypes are not risk-averse, but rather they are risk sponges. Every validation user test is sucking up a set of business risks. As a prototype moves past validation, it needs to be usable and the prototype evolves through iteration. It is then tested for usability and iterated again, and the process repeats itself until the end of time. The HCI design process is then improved by the practice...