Human Software is a book of poems, complemented with witty commentary and beautiful art. The poetry reflects how information is delivered, processed, and received throughout a lifetime. It takes the reader through a gutsy exploration of American psychology, history, art, science, religion, nature, current affairs, gender studies, and cultural/social studies. Additionally, the beautiful, unfiltered art drives home the raw feelings and emotions being explored throughout the book. The increasing social disturbances in America since 2016 motivated Jacob Stephens to combine his skills teaching civics with his love of writing poetry in the hopes of bettering his family and humanity. The urgency to replace toxic ideologies and indoctrination with love, tolerance, and scientific discovery motivates this poetry. Changing the hearts and minds of his family, friends, and humanity, so we can have a more peaceful and equitably prosperous future, is Stephens’s greatest passion. As evidenced by human history and the author’s own experiences, writing and art has the capacity to change the world. All it needs is for good people to lift it up and shout it out.

Motivation for a psychological approach; Research methods; Programming as human performance; Programming style; Software quality evaluation; Team organizations and group processes; Database systems and data models; Database query and manipulation languages; Natural language; Interactive interface issues; Designing interactive systems.

Activity theory is a way of describing and characterizing the structure of human - tivity of all kinds. First introduced by Russian psychologists Rubinshtein, Leontiev, and Vigotsky in the early part of the last century, activity theory has more recently gained increasing attention among interaction designers and others in the hum- computer interaction and usability communities (see, for example, Gay and H- brooke, 2004). Interest was given a signi?cant boost when Donald Norman suggested activity-theory and activity-centered design as antidotes to some of the putative ills of “human-centered design” (Norman, 2005). Norman, who has been credited with coining the phrase “user-centered design,” suggested that too much attention focused on human users may be harmful, that to design better tools designers need to focus not so much on users as on the activities in which users are engaged and the tasks they seek to perform within those activities. Although many researchers and practitioners claim to have used or been in?uenced by activity theory in their work (see, for example, Nardi, 1996), it is often dif?cult to trace precisely where or how the results have actually been shaped by activity theory. Inmanycases, evendetailedcasestudiesreportresultsthatseemonlydistantlyrelated, if at all, to the use of activity theory. Contributing to the lack of precise and traceable impact is that activity theory, - spite its name, is not truly a formal and proper theory.

This book constitutes the refereed conference proceedings of the 9th IFIP WG 13.2 International Conference on Human-Centered Software Engineering, HCSE 2022, which was held in Eindhoven, The Netherlands, during August 2022. The 11 full papers presented together with 2 poster and demo papers were carefully reviewed and selected from 25 submissions. The papers focus on the interdependencies between user interface properties and contribute to the development of theories, methods, tools and approaches for dealing with multiple properties that should be taken into account when developing interactive systems. They are organized in the following topical sections: user-centred design approaches; model-based and model-driven approaches; software development strategies; and posters and demos.

This book constitutes the refereed proceedings of the 5th IFIP WG 13.2 International Conference on Human-Centered Software Engineering, HCSE 2014, held in Paderborn, Germany, in September 2014. The 13 full papers and 10 short papers presented together with one keynote were carefully reviewed and selected from 35 submissions. The papers cover various topics such as integration of software engineering and user-centered design; HCI models and model-driven engineering; incorporating guidelines and principles for designing usable products in the development process; usability engineering; methods for user interface design; patterns in HCI and HCSE; software architectures for user interfaces; user interfaces for special environments; representations for design in the development process; working with iterative and agile process models in HCSE; social and organizational aspects in the software development lifecycle; human-centric software development tools; user profiles and mental models; user requirements and design constraints; and user experience and software design.

Human-CenteredSoftwareEngineering: BridgingHCI,UsabilityandSoftwareEngineering From its beginning in the 1980’s, the ?eld of human-computer interaction (HCI) has beende?nedasamultidisciplinaryarena. BythisImeanthattherehas beenanexplicit recognition that distinct skills and perspectives are required to make the whole effort of designing usable computer systems work well. Thus people with backgrounds in Computer Science (CS) and Software Engineering (SE) joined with people with ba- grounds in various behavioral science disciplines (e. g. , cognitive and social psych- ogy, anthropology)inaneffortwhereallperspectiveswereseenasessentialtocreating usable systems. But while the ?eld of HCI brings individuals with many background disciplines together to discuss a common goal - the development of useful, usable, satisfying systems - the form of the collaboration remains unclear. Are we striving to coordinate the varied activities in system development, or are we seeking a richer collaborative framework? In coordination, Usability and SE skills can remain quite distinct and while the activities of each group might be critical to the success of a project, we need only insure that critical results are provided at appropriate points in the development cycle. Communication by one group to the other during an activity might be seen as only minimally necessary. In collaboration, there is a sense that each group can learn something about its own methods and processes through a close pa- nership with the other. Communication during the process of gathering information from target users of a system by usability professionals would not be seen as so- thing that gets in the way of the essential work of software engineering professionals.

Proceedings of the 15th International Conference on Applied Human Factors and Ergonomics and the Affiliated Conferences, Nice, France, 24-27 July 2024.