Integrating usability techniques into software development

Now merged into Siemens Medical Solutions Health Services, our company, formerly called Shared Medical Systems, creates clinical, financial, and administrative software for the healthcare industry. Like other medium to large companies, SMS had reached a scale and maturity level that required the development process to be documented, predictable, repeatable, measurable, and usable by the development groups. After much study and consideration, senior management committed to implementing a universal OO development methodology. Senior management recognized the need to improve customer satisfaction, which had always been high but needed to he better in an increasingly competitive market. Management saw the introduction of usability practices as a prime means to achieve this objective. So they began to place greater emphasis on usability-even to the point of building and staffing dual state-of-the-art usability labs. Our goal throughout the projects we describe was to combine the best OO analysis and design practices and usability techniques to create a powerful, unified way to develop software     

Integration of usability evaluation and model-based software development

Model-based software development is carried out as a well defined process. Depending on the applied approach, different phases can be distinguished, e.g. requirements specification, design, prototyping, implementation and usability evaluation. During this iterative process manifold artifacts are developed and modified, including, e.g. models, source code and usability evaluation data. CASE tools support the development stages well, but lack a seamless integration of usability evaluation methods. We aim at bridging the gap between development and usability evaluation, through enabling the cooperative use of artifacts with the particular tools. As a result of integration usability experts save time to prepare an evaluation and evaluation results can be easier incorporated back into the development process. We show exemplary our work on enhancing the Eclipse framework to support usability evaluation for task model-based software development.     

Supporting usability through software architecture

Software engineers should consider usability as a quality attribute in their architectural a designs. Usability determines how effectively and comfortably an end-user can achieve the goals that gave rise to an interactive system. It is an important attribute to consider during all phases of software design, but especially during architectural design because of the expense involved in adding usability aspects after users have tested the system. Since the 1980s, ongoing work on supporting usability through software architectural constructs has focused on the iterative design process for the user interface, which involves initial design, user testing, re-design to correct detected flaws, re-testing, and so on. The traditional software architectural response to repeated and expected modifications to the user interface is to use separation, encapsulation and information hiding to localize the user interface     

Toward a hybrid model for usability resource allocation in industrial software product development

The organizational aspects of user‐centered software development in a financial services company are presented. The financial services industry sector is one of the industrial sectors to embark on the development of computer software as a consumer product. The nature of business in the service sector predisposes it to encounter difficulties in developing software aimed at meeting customer demands. Lack of familiarity and experience with the product design and implementation processes, as well as reliance on usability for acceptance, are major obstacles encountered. Difficulties, insights, and lessons learned regarding organizational ergonomics issues faced by a user‐centered design group are provided, and a hybrid resource distribution model is proposed to guide other service sector companies in their future software development efforts. © 2007 Wiley Periodicals, Inc. Hum Factors Man 17: 245–262, 2007.     

Software development methods and usability: Perspectives from a survey in the software industry in Norway

This paper investigates the relationship between software development methodologies and usability. The point of departure is the assumption that two important disciplines in software development, one of software development methods (SDMs) and one of usability work, are not integrated in industrial software projects.

Building on previous research we investigate two questions; (1) Will software companies generally acknowledge the importance of usability, but not prioritise it in industrial projects? and (2) To what degree are software development methods and usability perceived by practitioners as being integrated? To this end a survey in the Norwegian IT industry was conducted. From a sample of 259 companies we received responses from 78 companies.

In response to our first research question, our findings show that although there is a positive bias towards usability, the importance of usability testing is perceived to be much less than that of usability requirements. Given the strong time and cost pressures associated with the software industry, we believe that these results highlight that there is a gap between intention and reality. Regarding our second research question our survey revealed that companies perceive usability and software development methods to be integrated. This is in contrast to earlier research, which, somewhat pessimistically, has argued for the existence of two different cultures, one of software development and one of usability. The findings give hope for the future, in particular because the general use of system development methods are pragmatic and adaptable.     

基于投影的软件易用性评价方法

随着IT行业的不断发展,软件的易用性越来越受到用户和专家的关注与重视。如何科学地量化软件产品的易用性,进而对产品质量进行综合地测评,决定了软件产品的竞争力和用户的满意度。针对软件的易用性,提出了一种基于投影和直觉模糊理论的评价方法。首先,依据用户调查得到的信息,给出评价软件易用性的直觉模糊评价矩阵,并在此基础上建立了评价矩阵的理想决策。其次,借助群决策的框架,给出评价矩阵到理想决策上的投影。然后,基于投影给出测评软件的优劣序。最后,用一个测评实例展示出本方法的有效性和实用性。结果表明,本文提出的模型是一种软件质量综合评价的有效方法。     

‘Representing the User’ in software development—a cultural analysis of usability work in the product development context

It is widely accepted that users should be involved in the development of interactive systems. However, involving users in interactive systems development is challenging, especially in product development. The organizational culture is a key factor affecting the successes and failures of organizational change and development efforts. This paper shows how user involvement is intertwined with the organizational cultures in a case study of five software development organizations. User involvement is indirect in the case organizations, and labeled as usability work. Using cross case analysis, four ‘cultures of usability work’ are identified. The cultures have distinct cultural characteristics, employ different approaches to usability work, and have different preferences and strategies for the prospective facilitation of usability work. Sensitivity to the cultural context is identified as an important consideration in the facilitation of usability work, and culturally compatible strategies for usability work in different cultural settings are identified. The paper concludes that there might not be one ‘best, universally valid, context free way’ of introducing and carrying out usability work in software product development organizations.     

Why and how can human-related measures support software development processes?

In this paper we discuss why and how measures related to human aspects should be incorporated into software development processes. This perspective is based on the vast evidence that human aspects are the source of the majority of problems associated with software development projects. Having said that, we do not blame the humans involved in software development processes; rather, we suggest that human-related measures might be one means by which human aspects of software development processes can be supported.     

Observations on meeting usability goals for software products

Making software products more usable has been stated as an industrial, national, and even international goal. Constructive exchanges between those working in universities to build theory and those working in industry to build products have been identified as one way to speed the achievement of this goal. Programmes within IBM have encouraged such exchanges. Drawing on my experience in IBM, I outline some of the problems in setting and meeting software usability goals, discuss briefly the nature of collaborative work, and suggest ways to facilitate working together for mutual benefit despite possible differences in culture and purpose.     

面向教师的教育软件可用性模糊评测模型及应用

教育软件的可用性作为教师满意度的主要因素成为共识。为了支持以教师为核心的教育软件开发模式,促进教育软件的可用性质量,依据软件可用性属性指标的特性,通过教师满意度模糊综合评测,确定教育软件属性对于教师可用性的权重评测和满意度评测隶属矩阵,计算教育软件评测向量集,通过坐标分布进一步分析提高教育软件可用性质量改善的因素优先顺序以及全因素改进策略。最后以教育软件ESClassLab可用性评测分析相应的软件质量改进顺序和策略因素。     

Why does site visit matter in global software development: A knowledge-based perspective

ContextFace-to-Face (F2F) interaction is a strong means to foster social relationships and effective knowledge sharing within a team. However, communication in Global Software Development (GSD) teams is usually restricted to computer-mediated conversation that is perceived to be less effective and interpersonal. Temporary collocation of dispersed members of a software development team is a well-known practice in GSD. Despite broad realization of the benefits of visits, there is lack of empirical evidence that explores how temporary F2F interactions are organized in practice and how they can impact knowledge sharing between sites.ObjectiveThis study aimed at empirically investigating activities that take place during temporary collocation of dispersed members and analyzing the outcomes of the visit for supporting and improving knowledge sharing.MethodWe report a longitudinal case study of a GSD team distributed between Denmark and Pakistan. We have explored a particular visit organized for a group of offshore team members visiting onshore site for two weeks. Our findings are based on a systematic and rigorous analysis of the calendar entries of the visitors during the studied visit, several observations of a selected set of the team members’ activities during the visit and 13 semi-structured interviews.ResultsLooking through the lens of knowledge-based theory of the firm, we have found that social and professional activities organized during the visit, facilitated knowledge sharing between team members from both sites. The findings are expected to contribute to building a common knowledge and understanding about the role and usefulness of the site visits for supporting and improving knowledge sharing in GSD teams by establishing and sustaining social and professional ties.     

A method to elicit architecturally sensitive usability requirements: its integration into a software development process

In the Human-Computer Interaction (HCI) community, software usability has primarily been concerned with the presentation of information, more precisely with the user interface. However, some usability problems can prove costly to fix if the changes require modifications that reach beyond the presentation layer, namely those that cannot be easily accommodated by the software architecture. Taking into account some usability requirements earlier in the software development cycle, specifically prior to the architectural design phase, can reduce the cost of these modifications. There is a scarcity of methods and guidelines with the scope to direct users in eliciting the usability requirements that can impact the software architecture. This paper proposes a usability-driven adaptation of the quality attribute workshop (QAW) to assist software development organizations in discovering and documenting usability requirements. It shows how this method can be integrated into a software development process, by discussing how the existing software framework workflows can be adjusted to take this new activity into consideration. A preliminary exercise was conducted to help discern the utility and the limits of the proposed method. Participants with different levels of knowledge of usability and comprehension of the system being developed found the method constructive, as it guided them in identifying the architecturally relevant usability requirements. It also helped determine the usability aspects that would not necessarily have been defined if this technique had not been employed.     

Training software developers and designers to conduct usability evaluations

Many efforts to improve the interplay between usability evaluation and software development rely either on better methods for conducting usability evaluations or on better formats for presenting evaluation results in ways that are useful for software designers and developers. Both of these approaches depend on a complete division of work between developers and evaluators. This article takes a different approach by exploring whether software developers and designers can be trained to conduct their own usability evaluations. The article is based on an empirical study where 36 teams with a total of 234 first-year university students on software development and design educations were trained through an introductory course in user-based website usability testing that was taught in 40 h. They used the techniques from this course for planning, conducting, and interpreting the results of a usability evaluation of an interactive website. They gained good competence in conducting the evaluation, defining user tasks and producing a usability report, while they were less successful in acquiring skills for identifying and describing usability problems.     

Why software jewels are rare

A software jewel is a well structured program written in a consistent style, developed so that each component is simple and organized, and designed so that the product is easy to change. Despite helpful articles and many textbooks on software design, software jewels remain rare. Most of the software we see or buy is ugly, unreliable, hard to change. I discuss why the recipes of the masters have not led to more elegant commercial software and then provide some advice for those who would like to produce better software     

Why software reliability predictions fail

Software reliability reflects a customer's view of the products we build and test, as it is usually measured in terms of failures experienced during regular system use. But our testing strategy is often based on early product measures, since we cannot measure failures until the software is placed in the field. The author shows us that such measurement is not effective at predicting the likely reliability of the delivered software.     

A proposed index of usability: a method for comparing the relative usability of different software systems

. Usability is becoming a more and more important software criterion, but the present usability measurement methods are either difficult to apply, or overly dependent upon evaluators' expertise. Based on human information processing theory, this study identified eight human factors considerations which are relevant to software usability. These considerations as well as the three stages of human information processing theory formed the framework from which our Purdue Usability Testing Questionnaire (PUTQ) is derived. An experiment was conducted to test the validity of PUTQ. The experiment result showed high correlation between PUTQ and the Questionnaire for User Interaction Satisfaction (QUIS version 5.5). In addition, PUTQ detected the differences in user performance between two experimental interface systems, but QUIS failed to do so.