If you have picked up this book and are browsing the Preface, you may well be asking yourself"What makes this book different from the large number I can find on amazon. com?". Well, the answer is a blend of the academic and the practical, and views of the subject you won't get from anybody else: how psychology and linguistics influence the field of requirements engineering (RE). The title might seem to be a bit of a conundrum; after all, surely requirements come from people so all requirements should be user-centred. Sadly, that is not always so; many system disasters have been caused simply because requirements engineering was not user-centred or, worse still, was not practised at all. So this book is about putting the people back into com puting, although not simply from the HCI (human-computer interaction) sense; instead, the focus is on how to understand what people want and then build appropriate computer systems.

Written by psychologists, this book focuses on the design of computer systems from the perspective of the user. The authors place human beings firmly at the centre of system design and so assess their cognitive and physical attributes as well as their social needs. The model used specifically takes into consideration the way in which computer technology needs to be designed in order to take account of all these human factors. The text comprises a careful mix of theory and applications and is spiced throughout with practical examples of do's and don'ts in designing systems.

Looks at the application design process, describing how to create user-friendly applications.

A new product can be easy or difficult to use, it can be efficient or cumbersome, engaging or dispiriting, it can support the way we work and think - or not. What options are available for systematically addressing such parameters and provide users with an appropriate functionality, usability and experience? In the last decades, several fields have evolved that encompass a user-centred approach to create better products for the people who use them. This book provides a comprehensible introduction to the subject. It is aimed first and foremost at people involved in software and product development – product managers, project managers, consultants and analysts, who face the major challenge of developing highly useful and usable products. Topics include: The most important user-centred techniques and their alignment in the development process Planning examples of user-centred activities for projects User-oriented approaches for organisations Real-life case studies Checklists, tips and a lot of background information provide help for practitioners

Developing today's complex systems requires more than just good software engineering solutions. Many are faced with complex systems projects, incomplete or inaccurate requirements, canceled projects, or cost overruns, and have their systems' users in revolt and demanding more. Others want to build user-centric systems, but fear managing the process. This book describes an approach that brings the engineering process together with human performance engineering and business process reengineering. The result is a manageable user-centered process for gathering, analyzing, and evaluating requirements that can vastly improve the success rate in the development of medium-to-large size systems and applications. Unlike some texts that are primarily conceptual, this volume provides guidelines, "how-to" information, and examples, enabling the reader to quickly apply the process and techniques to accomplish the following goals: * define high quality requirements, * enhance productive client involvement, * help clients maintain competitiveness, * ensure client buy-in and support throughout the process, * reduce missing functionality and corrections, and * improve user satisfaction with systems. This volume clearly details the role of user-centered requirements and knowledge acquisition within Scenario-Based Engineering Process (SEP) and identifies SEP products and artifacts. It assists project personnel in planning and managing effective requirements activities, including managing risks, avoiding common problems with requirements elicitation, organizing project participants and tools, and managing the logistics. Guidelines are provided for the following: selecting the right individual and group techniques to elicit scenarios and requirements from users; subject matter experts, or other shareholders; and ensuring engineers or analysts have the necessary skills.

This book examines the possibilities of incorporating elements of user-centred design (UCD) such as user experience (UX) and usability with agile software development. It explores the difficulties and problems inherent in integrating these two practices despite their relative similarities, such as their emphasis on stakeholder collaboration. Developed from a workshop held at NordiCHI in 2014, this edited volume brings together researchers from across the software development, UCD and creative design fields to discuss the current state-of-the-art. Practical case studies of integrating UCD in Agile development across diverse contexts are presented, whilst the different futures for UCD and other design practices in the context of agile software development are identified and explored. Integrating User Centred Design in Agile Development will be ideal for researchers, designers and academics who are interested in software development, user-centred design, agile methodologies and related areas.