Usability supporting architectural patterns (USAPs) have been shown to provide developers with useful guidance for producing a software architecture design that supports usability in a laboratory setting [7]. In close collaboration between researchers and software developers in the real world, the concepts were proven useful [2]. However, this process does not scale to industrial development efforts. In particular, development teams need to be able to use USAPs while being distributed world-wide. USAPs also must support legacy or already partially-designed architectures, and when using multiple USAPs there could be a potentially overwhelming amount of information given to the software architects. In this paper, we describe the restructuring of USAPs using a pattern language to simplify the development and use of multiple USAPs. We also describe a delivery mechanism that is suitable for industrial-scale adoption of USAPs. The delivery mechanism involves organizing responsibilities into a hierarchy, utilizing a checklist to ensure responsibilities have been considered, and grouping responsibilities in a fashion that both supports use of multiple USAPs simultaneously and also points out reuse possibilities to the architect.

Today the challenge in the mobile industry is User experience (UX), which is starting to affect software engineering processes. A common use or definition of the term UX is still not de facto defined. Industry and academy are both in agreement that UX definitely includes more than the previous usability definition. Our concern in this paper is how industry and manufacturers can manage to successfully get a UX idea into and through the software development cycle? Our discussion includes obvious components from usability and new UX components that are not taken into account by prevailing HCI approaches. We will discuss branding, trends and timing as vital components in that puzzle.

This position paper proposes that event-based stories appear to have the potential to provide a simple, but powerful technique for users and developers to communicate emotional and informational needs, redesign processes, and structure the user interface design within the agile development paradigm. Informal evaluation of the use of event-based stories in several development projects suggest that event-based stories could be useful in integrating software and usability engineering. Controlled experiments, in addition to more formal case analyses are the next steps.

A thorough understanding of the users that interact with the system is necessary to develop usable systems. The Personas technique developed by the human-computer interaction (HCI) discipline gathers data about users, gains an understanding of their characteristics, defines fictitious personas based on this understanding and focuses on these personas throughout the software development process. The aim of our research is to build Personas into systems development following software engineering (SE) guidelines. The benefits to be gained are an understanding of the user which is not traditionally taken into account in SE. To do this, we had to undertake two types of tasks. First, we modified the Personas technique to conform to the levels of systematization common in SE. We have called the modified technique PersonaSE. Second, we incorporated the proposed technique into the software requirements analysis process.

Abstract—User-centered activities related to multimedia include production and organization of multimedia content, filing, retrieval, sharing and multimedia communications. Today, there is a growing body of development teams and companies, that work to enable users to perform these activities in various technological ways. Integrating media functions into handheld devices, mobile phones, set-top boxes, and different “wearable ” consumer electronics products, makes users affected in different ways. This paper emphasizes the effects of multimedia applications, which are always on users ’ disposal, on users ’ habits and their regular activities. We argue that application usability is inversely proportional to its usage interference with regular activities of people as users. We introduce novel metrics to capture the amount of this interference, and likewise introduce a measure for multimedia software usability, contributing to software usability assessment processes (SQA). U

Following up the tradition established in the I-USED (International Workshop on the Interplay between Usability Evaluation and Software Development) series of workshops 1, this workshop is aimed at bringing together Human-Computer Interaction (HCI) and Software Engineering (SE) professionals and researchers interested in discussing recent trends and perspectives of the role of usability in software development. With respect to I-USED, I-UxSED

conclusions, or recommendations expressed in this material are those of the author and should not be interpreted as representing the official opinions, either expressed or implied, of the funding agencies or the U.S. Government. Keywords In spite of the goodwill and best efforts of software engineers and usability professionals, systems continue to be built and released with glaring usability flaws that are costly and difficult to fix after the system has been built. Although user interface (UI) designers, be they usability or design experts, communicate usability requirements to software development teams, seemingly obvious usability features often fail to be implemented as expected. The impact of usability issues becomes increasingly severe in all kinds of software as computer use continues to rise in the home, in the workplace, and in education. If, as seems likely, software developers intend to build what UI designers specify and simply do not know how to interpret the ramifications that usability requirements have for the deep structure of the software (i.e. the “software architecture”), something is needed to help to bridge the gap between UI designers and software