Integrating HCI concerns into a UML based software engineering course

Software Engineering (SE) and HCI (Human Computer Interaction) are not the same age, do not have the same history, background or foundations, and did never share design principles and design models. The separation principle, by encouraging separate concerns and techniques to design the interactive and the computational layers of a software system - despite being absolutely correct from several SE crucial design principles, like modularity, separation of concerns, encapsulation, context independence and so on -, has sometimes been misjudged and mistakenly used. Therefore, instead of bridging the gap between the two separate de- signs, it helped widening that gap. However, the principle does not mention and does not impose any restrictions on how the integration should be done. In the context of a software engineering course the authors have been involved with for some years, the need has arisen to provide students with HCI skills. Several attempts at integrating HCI into software engineering can be found in the literature. However, none seemed amenable to application in the context of the course, basically because none of them could be taught and learnt in such a way (methodology) that could easily be blent into the software engineering design process. We present a methodological process that we have been teaching that aims at shortening the gap that software engineering students face when trying to adapt SE techniques to the interactive layer

HCI Support Card: Creating and Using a Support Card for Education in Human-Computer Interaction

Support cards summarise a set of core information about a subject. The periodic table of chemical elements and the mathematical tables are well-known examples of support cards for didactic purposes. Technology professionals also use support cards for recalling information such as syntactic details of programming languages or harmonic colour palettes for designing user interfaces. While support cards have proved useful in many contexts, little is known about its didactic use in the Human-Computer Interaction (HCI) field. To fill this gap, this study proposes and evaluates a process for creating and using an HCI support card. The process considers the interdisciplinary nature of the field, covering the syllabus, curriculum, textbooks, and students' perception about HCI topics. The evaluation is based on case studies of creating and using a card during a semester in two undergraduate courses: Software Engineering and Information Systems. Results show that a support card can help students in following the lessons, remembering and integrating the different topics studied in the classroom. The card guides the students in building their cognitive maps, mind maps, and concept maps to study human-computer interaction. It fosters students' curiosity and permanent engagement with the HCI topics. The card usefulness goes beyond the HCI classroom, being also used by students in their professional activities and other academic disciplines, fostering an interdisciplinary application of HCI topics.Comment: Workshop on HCI Education (WEIHC '19

Human Activity Modelling in the Specification of Operational Requirements: Work in Progress

This paper describes our experience of integrating HCI concepts and techniques into a concurrent requirements engineering process called RESCUE. We focus on the use of a model of current human activity to inform specification of a future system. We show how human activity descriptions, written using a specially designed template, can facilitate the authoring of use case descriptions to be used in the elicitation of requirements for complex socio-technical systems. We describe our experience of using descriptions of human activity, written using the template, to support specification of operational requirements for DMAN, a system to support air traffic controllers in managing the departure of aircraft from airports. We end with a discussion of lessons learnt from our experience and present some ideas for future development of work in this area

Finding and Resolving Security Misusability with Misusability Cases

Although widely used for both security and usability concerns, scenarios used in security design may not necessarily inform the design of usability, and vice- versa. One way of using scenarios to bridge security and usability involves explicitly describing how design deci- sions can lead to users inadvertently exploiting vulnera- bilities to carry out their production tasks. This paper describes how misusability cases, scenarios that describe how design decisions may lead to usability problems sub- sequently leading to system misuse, address this problem. We describe the related work upon which misusability cases are based before presenting the approach, and illus- trating its application using a case study example. Finally, we describe some findings from this approach that further inform the design of usable and secure systems

DEMO: Attaching InternalBlue to the Proprietary macOS IOBluetooth Framework

In this demo, we provide an overview of the macOS Bluetooth stack internals and gain access to undocumented low-level interfaces. We leverage this knowledge to add macOS support to the InternalBlue firmware modification and wireless experimentation framework.Comment: 13th ACM Conference on Security and Privacy in Wireless and Mobile Network