Method to Define User Interfaces in the Requirements Analysis Phase

Many requirements for quality in use are elicited in the late development phase. However, if requirements are elicited in the late development phase, the development may return to the previous phase or some requirements cannot be realized due to costs and schedules. To reduce these cases, we propose a method to elicit the requirements in the requirements analysis phase. First, software developers analyze the user characteristics (UCs) of the target users and specify important quality characteristics (QCs) for quality in use and UI design items based on the relationships among UC, QC, and UI design items. Because UI design items are considerations to develop UIs, the specified UI design items are elicited as UI requirements. Thus, when important QCs are specified, UI requirements can be easily elicited by tracing the relationships from QCs to UI design items.

[1]  Mike Kuniavsky,et al.  Observing the User Experience, Second Edition: A Practitioner's Guide to User Research , 2012 .

[2]  Jeff A. Johnson,et al.  Designing with the Mind in Mind, Second Edition: Simple Guide to Understanding User Interface Design Guidelines , 2014 .

[3]  Nammee Moon,et al.  Towards a cultural user interface generation principles , 2012, Multimedia Tools and Applications.

[4]  Giancarlo Guizzardi,et al.  Non-functional requirements as qualities, with a spice of ontology , 2014, 2014 IEEE 22nd International Requirements Engineering Conference (RE).

[5]  I Fernandez Gonzalez,et al.  User Interface Guidelines , 1999 .

[6]  Axel van Lamsweerde,et al.  Goal-oriented requirements enginering: a roundtrip from research to practice [enginering read engineering] , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[7]  Andres Mejia-Figueroa,et al.  Developing Usable Software Applications for Users with Autism: User Analysis, User Interface Design Patterns and Interface Components , 2016, 2016 4th International Conference in Software Engineering Research and Innovation (CONISOFT).

[8]  Toshiki Yamaoka,et al.  A Logical Design Method for User Interface Using GUI Design Patterns , 2013, HCI.

[9]  Alan Cooper,et al.  About Face 3: the essentials of interaction design , 1995 .

[10]  Fanny Andalia,et al.  Implementation of Analytical Hierarchy Process On Airplane Ticket Booking Application Selection With Software Quality Requirements and Evaluation ISO / IEC 25010 : 2011 , 2018 .

[11]  Michio Tsuda,et al.  Towards a Strategic Requirements Elicitation - A Proposal of the PRINCE Model , 2009, ICSOFT.

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

[13]  Mike Kuniavsky,et al.  Observing the User Experience: A Practitioner's Guide to User Research (Second Edition) , 2013, IEEE Transactions on Professional Communication.

[14]  A. Tamhane,et al.  Multiple Comparison Procedures , 2009 .

[15]  Ben Shneiderman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction, 6th Edition , 2016 .

[16]  Jakob Nielsen,et al.  Chapter 6 – Usability Testing , 1993 .

[17]  Carl K. Chang,et al.  Situation-Oriented Requirements Elicitation , 2016, 2016 IEEE 40th Annual Computer Software and Applications Conference (COMPSAC).