A study about HCI in practice of interactive system development using CMMI-DEV

Abstract

Human-Computer Interaction (HCI) community has proposed many methods, techniques and standards for the development of interactive systems. Despite the great recognition of many of these approaches in academia, little is known about the state of practice in industry. To what extent are they known and used, while using a defined software process, to develop interactive systems? What is their level of use compared to software engineering approaches? This paper presents a study that we have conducted to answer these questions. This study is developed on top ___________________________ 169Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page.

HCI in practice: An empirical study with software process capability maturity model consultants in Brazil

“…This survey is also being applied in a worldwide context for CMMI‐DEV model consultants . Our ongoing works include (i) the definition of a methodological guide to support SPCM model consultants in their choice of the adequate HCI approach at the right moment and (ii) the definition of a software development process for interactive systems, which can be classical or innovative, such as interactive applications on tabletop (s) with tangible objects (see for instance Kubicki et al and Bouabid et al), integrating HCI approaches to support each activity.…”

Untitled

“…Unal et al [41] concentrated their research study on ISO and CMMI process models to be adopted for standard software development. Gonçalves et al [11] also worked on CMMI standard and concluded that it is the commonly used evaluation means in software production. CMMI DEV provides best practices for developers to advance and innovate their processes according to the will of customers.…”

“…Still, the results display that it is a uni-directional methodology for trace. Gonçalves et al [11] concerted on following HCI codes in handling requirements, but it is confined to the user interface of application. Keshta et al [18] has analyzed the performance of systems after several alterations are made and proposed a traceability framework for processing change in requirements.…”