Reusable knowledge for satisficing usability requirements

Usability is becoming increasingly recognized as being an important factor in the acceptance of systems by end users. There is a basic need for systematic approaches to reason, model and analyze usability from the early stages of software development. Furthermore, it is necessary to develop a usable ontology or classification of measurable aspects that can be used to aid in the specification of usability requirements. These ontologies should be represented in a way that facilitates their use as guidelines for the requirements elicitation process. This work builds on review of literature in the area of human-computer interaction and the emerging field of usability engineering in developing a catalog of aspects of usability that can be considered during requirements gathering. This catalogue is used to guide the requirements engineer through alternatives for achieving usability for information systems. The approach uses i* framework, having usability modeled as a special type of goal.

[1]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[2]  Herbert A. Simon,et al.  The Sciences of the Artificial , 1970 .

[3]  A. Finkelstein,et al.  A comedy of errors: the London Ambulance Service case study , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[4]  Jon Doyle,et al.  Guardian Angel: Patient-Centered Health Information Systems , 1994 .

[5]  Jakob Nielsen,et al.  Designing Web Usability: The Practice of Simplicity , 1999 .

[6]  Ben Shneiderman,et al.  Designing The User Interface , 2013 .

[7]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[8]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[9]  Lawrence Chung,et al.  Dealing with Non-Functional Requirements: Three Experimental Studies of a Process-Oriented Approach , 1995, 1995 17th International Conference on Software Engineering.

[10]  David R. Lindstrom Five Ways to Destroy a Development Project , 1993, IEEE Softw..

[11]  André Kushniruk,et al.  Evaluation in the design of health information systems: application of approaches emerging from usability engineering , 2002, Comput. Biol. Medicine.

[12]  Mary Beth Rosson,et al.  Usability Engineering: Scenario-based Development of Human-Computer Interaction , 2001 .

[13]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[14]  E. Coiera Interaction Design , 2002 .

[15]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[16]  Julio Cesar Sampaio do Prado Leite,et al.  The world?s a stage: a survey on requirements engineering using a real-life case study , 1999, J. Braz. Comput. Soc..

[17]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

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

[19]  Herbert A. Simon,et al.  The Sciences of the Artificial - 3rd Edition , 1981 .