From extreme programming and usability engineering to extreme usability in software engineering education (XP+UE /spl rarr/ XU)

The success of extreme programming (XP) is based, among other things, on an optimal communication in teams of 6-12 persons, simplicity, frequent releases and a reaction to changing demands. Most of all, the customer is integrated into the development process, with constant feedback. This is very similar to usability engineering (UE) which follows a spiral four phase procedure model (analysis, draft, development, test) and a three step (paper mock-up, prototype, final product) production model. In comparison, these phases are extremely shortened in XP; also the ideal team size in UE user-centered development is 4-6 people, including the end-user. The two development approaches have different goals but, at the same time, employ similar methods to achieve them. It seems obvious that there must be synergy in combining them. The authors present ideas in how to combine them in an even more powerful development method called extreme usability (XU). The most important issue of this paper is that the authors have embedded their ideas into software engineering education.

[1]  John L. Bennett,et al.  Visual display terminals: Usability issues and health concerns , 1984 .

[2]  Andreas Holzinger,et al.  Rapid prototyping for a virtual medical campus interface , 2004, IEEE Software.

[3]  Andreas Holzinger,et al.  Usability engineering methods for software developers , 2005, CACM.

[4]  J. Wang,et al.  Proceedings of the 29th Annual International Computer Software and Applications Conference—Workshops and Fast Abstracts COMPSAC 2005 , 2005 .

[5]  Band , 1943 .

[6]  Robert A. Virzi,et al.  Refining the Test Phase of Usability Evaluation: How Many Subjects Is Enough? , 1992 .

[7]  Andreas Holzinger,et al.  User-Centered Interface Design for Disabled and Elderly People: First Experiences with Designing a Patient Communication System (PACOSY) , 2002, ICCHP.

[8]  Carola B. Fellenz Introducing usability into smaller organizations , 1997, INTR.

[9]  Stuart I. Feldman Quality Assurance: Much More than Testing , 2005, ACM Queue.

[10]  Mary Beth Rosson,et al.  Getting around the task-artifact cycle: how to make claims and design by scenario , 1992, TOIS.

[11]  Jakob Nielsen,et al.  User involvement in the design process: why, when & how? , 1993, INTERCHI.

[12]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[13]  Jakob Nielsen,et al.  Usability engineering , 1997, The Computer Science and Engineering Handbook.

[14]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.