86,087 research outputs found
A Conceptual UX-aware Model of Requirements
User eXperience (UX) is becoming increasingly important for success of
software products. Yet, many companies still face various challenges in their
work with UX. Part of these challenges relate to inadequate knowledge and
awareness of UX and that current UX models are commonly not practical nor well
integrated into existing Software Engineering (SE) models and concepts.
Therefore, we present a conceptual UX-aware model of requirements for software
development practitioners. This layered model shows the interrelation between
UX and functional and quality requirements. The model is developed based on
current models of UX and software quality characteristics. Through the model we
highlight the main differences between various requirement types in particular
essentially subjective and accidentally subjective quality requirements. We
also present the result of an initial validation of the model through
interviews with 12 practitioners and researchers. Our results show that the
model can raise practitioners' knowledge and awareness of UX in particular in
relation to requirement and testing activities. It can also facilitate
UX-related communication among stakeholders with different backgrounds.Comment: 6th International Working Conference on Human-Centred Software
Engineerin
Enterprise Experience into the Integration of Human-Centered Design and Kanban
he integration of Human-Centered Design (HCD) and Agile Software Development (ASD) promises the
development of competitive products comprising a good User Experience (UX). This study has investigated
the integration of HCD and Kanban with the aim to gain industrial experiences in a real world context. A
case study showed that requirements flow into the development process in a structured manner by adding a
design board. To this end, the transparency concerning recurring requirements increased. We contribute to
the body of knowledge of software development by providing practical insights into Human-Centered Agile
Development (HCAD). On one hand, it is shown that the integration of HCD and Kanban leads to a product
with a good UX and makes the development process more human-centered. On the other hand, we conclude
that a cross-functional collaboration speeds up product development.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED
Supporting End-User Development through a New Composition Model: An Empirical Study
End-user development (EUD) is much hyped, and its impact has outstripped even the most optimistic forecasts. Even so, the vision of end users programming their own solutions
has not yet materialized. This will continue to be so unless we in both industry and the research community set ourselves the ambitious challenge of devising end to end an end-user application development model for developing a new age of EUD tools. We have embarked on this venture, and this paper presents the main insights and outcomes of our research and development efforts as part of a number of successful EU research projects. Our proposal not only aims to reshape software engineering to meet the needs of EUD but also to refashion its components as solution building blocks instead of programs and software developments. This
way, end users will really be empowered to build solutions based on artefacts akin to their expertise and understanding of ideal solution
Recommended from our members
The role of user requirements research in medical device development
Aims and Objectives: This research aims to suggest a concise framework to help in the better
conceptualisation and integration of users in the medical device development (MDD) process. The
current economic, political and social climate concerning the matter of healthcare delivery has
resulted in the emergence of numerous users and user groups for whom the healthcare system has not
previously catered for. These users have created ambiguity for the designers and manufacturers of
medical devices as the boundaries between their needs and requirements have blurred, outdating
current methods of MDD to meet consumer needs.
Research Design and Methodology: The research methodology begins primarily with conducting a
literature search on the theories relating to user requirements and medical device development. The
paper outlines these findings through initially describing users and user involvement and relating
them to medical devices. The cross-disciplinary nature of healthcare influenced the investigation into
multiple disciplines including; IT, Ergonomics – particularly participatory research, Psychology and
Design. These disciplines expose various methods and processes, which are useful to user
requirements research. These methods were analysed for their compatibility, and then used to
construct a conceptual framework for user involvement in MDD.
Results: The research insinuates the true significance of user involvement and hence resulted in the
formation of a conceptual framework to aid user involvement in the MDD process. The framework is
produced by the amalgamation of relevant methods examined across the disciplines, in a
complimentary fashion.
Conclusion: The originality of this research lies in its use of a multidisciplinary approach. Previous
research claiming multi-methods has dealt with combining two disciplines or methods at a time i.e.
Computer supported cooperative work (CSCW) with participatory research (Scandurra et al, 2008)
for the needs analysis of healthcare professionals only. Collaboration across disciplines has also been
investigated (Johnson et al, 2005), but this was for the purpose of redesign rather than initial designs.
This framework can help medical device designers to fully access all user requirements through more
extensive collaboration right at the start. It reduces the risk of high costs involved in device rejection,
usually associated with belated recognition of user needs in the design cycle
Recommended from our members
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
Systematic development of courseware systems
Various difficulties have been reported in relation to the development of courseware systems. A central problem is to address the needs of not only the learner, but also instructor, developer, and other stakeholders, and to integrate these different needs. Another problem area is courseware architectures, to which much work has been dedicated recently. We present a systematic approach to courseware development – a methodology for courseware engineering – that addresses these problems. This methodology is rooted in the educational domain and is based on methods for software development in this context. We illustrate how this methodology can improve the quality of courseware systems and the development process
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
Why not empower knowledge workers and lifelong learners to develop their own environments?
In industrial and educational practice, learning environments are designed and implemented by experts from many different fields, reaching from traditional software development and product management to pedagogy and didactics. Workplace and lifelong learning, however, implicate that learners are more self-motivated, capable, and self-confident in achieving their goals and, consequently, tempt to consider that certain development tasks can be shifted to end-users in order to facilitate a more flexible, open, and responsive learning environment. With respect to streams like end-user development and opportunistic design, this paper elaborates a methodology for user-driven environment design for action-based activities. Based on a former research approach named 'Mash-Up Personal Learning Environments'(MUPPLE) we demonstrate how workplace and lifelong learners can be empowered to develop their own environment for collaborating in learner networks and which prerequisites and support facilities are necessary for this methodology
- …