Guidelines for Eliciting Usability Functionalities

Like any other quality attribute, usability imposes specific constraints on software components. Features that raise the software system's usability have to be considered from the earliest development stages. But, discovering and documenting usability features is likely to be beyond the usability knowledge of most requirements engineers, developers, and users. We propose an approach based on developing specific guidelines that capitalize upon key elements recurrently intervening in the usability features elicitation and specification process. The use of these guidelines provides requirements analysts with a knowledge repository. They can use this repository to ask the right questions and capture precise usability requirements information.

[1]  André Kushniruk,et al.  Reusable knowledge for satisficing usability requirements , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[2]  Alain Abran,et al.  The Guide to the Software Engineering Body of Knowledge , 1999, IEEE Softw..

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

[4]  Ben Shneiderman,et al.  Designing the user interface (2nd ed.): strategies for effective human-computer interaction , 1992 .

[5]  Ben Kovitz Ambiguity and What to Do about It , 2002 .

[6]  B. F. Castro Buschmann, Frank; Meunier, Regine; Rohnert, Hans; Sommerlad, Peter; Stal, Michael. Pattern-oriented software architecture: a system of patterns, John Wiley & Sons Ltd, 1996 , 1997 .

[7]  Lars Hagge,et al.  Sharing requirements engineering experience using patterns , 2005, IEEE Software.

[8]  Leonard J. Bass,et al.  Usability-supporting architectural patterns , 2004, Proceedings. 26th International Conference on Software Engineering.

[9]  Joseph F. Dumas,et al.  A Practical Guide to Usability Testing , 1993 .

[10]  Marc Chrusch The whiteboard: seven great myths of usability , 2000, INTR.

[11]  Ben Kovitz Ambiguity and what to do about it [requirements engineering] , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[12]  H. Rex Hartson,et al.  Developing user interfaces: ensuring usability through product & process , 1993 .

[13]  Jenifer Tidwell Designing Interfaces , 2005 .

[14]  Jakob Nielsen,et al.  Heuristic Evaluation of Prototypes (individual) , 2022 .

[15]  Jenifer Tidwell,et al.  Designing interfaces - patterns for effective interaction design , 2019 .

[16]  Patty Curthoys,et al.  Developing user interfaces: Ensuring usability through product and process , 1997 .

[17]  H. König,et al.  Anforderungsdefinition und -spezifikation für PAC-Systeme (Picture Archiving and Communications System) Ein Leistungsverzeichnis in Anlehnung an den Standard„IEEE Recommended Practice for Software Requirements Specifications” , 1999, Der Radiologe.

[18]  Kyo Chul Kang,et al.  Issues in Requirements Elicitation , 1992 .

[19]  Natalia Juristo Juzgado,et al.  Analysing the impact of usability on software design , 2007, J. Syst. Softw..

[20]  Betty H. C. Cheng,et al.  Requirements patterns for embedded systems , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[21]  Len Bass,et al.  Achieving usability through software architecture , 2001, ICSE 2001.

[22]  Randolph G. Bias,et al.  Cost-Justifying Usability: An Update for the Internet Age , 2005 .

[23]  Timo Jokela Guiding Designers to the World of Usability: Determining Usability Requirements Through Teamwork , 2005 .

[24]  Ben Shneiderman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction , 1998 .

[25]  Søren Lauesen,et al.  Communication gaps in a tender process , 2005, Requirements Engineering.

[26]  Leonard J. Bass,et al.  Linking usability to software architecture patterns through general scenarios , 2003, J. Syst. Softw..

[27]  Jong-Yih Kuo,et al.  Distributed Requirement Elicitation using Patterns , 2003, Modelling, Identification and Control.

[28]  Ahmed Seffah,et al.  The obstacles and myths of usability and software engineering , 2004, CACM.

[29]  Natalia Juristo Juzgado,et al.  Designing software architectures for usability , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[30]  B. J. Ferro Castro,et al.  Pattern-Oriented Software Architecture: A System of Patterns , 2009 .

[31]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[32]  Jan Bosch,et al.  Architecturally Sensitive Usability Patterns , 2003 .

[33]  Peter Sommerlad,et al.  Pattern-Oriented Software Architecture , 1996 .

[34]  Jan Bosch,et al.  Architecting for usability: a survey , 2004, J. Syst. Softw..

[35]  Larry L. Constantine,et al.  Software for Use - A Practical Guide to the Models and Methods of Usage-Centered Design , 1999 .

[36]  Deborah J. Mayhew,et al.  The usability engineering lifecycle , 1998, CHI Conference Summary.

[37]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[38]  Barry Boehm,et al.  Characteristics of software quality , 1978 .

[39]  Daniel M. Berry,et al.  The importance of ignorance in requirements engineering , 1995, J. Syst. Softw..

[40]  Deborah J. Mayhew,et al.  The usability engineering lifecycle , 1999, CHI Extended Abstracts.

[41]  Alexander L. Wolf,et al.  Acm Sigsoft Software Engineering Notes Vol 17 No 4 Foundations for the Study of Software Architecture , 2022 .

[42]  George M. Donahue Usability and the Bottom Line , 2001, IEEE Softw..

[43]  Christof Ebert,et al.  requirements uncertainty: influencing factors and concrete improvements , 2005, ICSE '05.