A method to elicit architecturally sensitive usability requirements: its integration into a software development process

  • Authors:

  • Tamer Rafla;Pierre N. Robillard;Michel Desmarais

  • Affiliations:

  • Software Engineering Research Lab, Ecole Polytechnique de Montreal, Montreal, Canada H3C 3A7;Software Engineering Research Lab, Ecole Polytechnique de Montreal, Montreal, Canada H3C 3A7;Software Engineering Research Lab, Ecole Polytechnique de Montreal, Montreal, Canada H3C 3A7

  • Venue:
  • Software Quality Control
  • Year:
  • 2007

Quantified Score

Hi-index 0.00

Visualization

Abstract

In the Human-Computer Interaction (HCI) community, software usability has primarily been concerned with the presentation of information, more precisely with the user interface. However, some usability problems can prove costly to fix if the changes require modifications that reach beyond the presentation layer, namely those that cannot be easily accommodated by the software architecture. Taking into account some usability requirements earlier in the software development cycle, specifically prior to the architectural design phase, can reduce the cost of these modifications. There is a scarcity of methods and guidelines with the scope to direct users in eliciting the usability requirements that can impact the software architecture.This paper proposes a usability-driven adaptation of the quality attribute workshop (QAW) to assist software development organizations in discovering and documenting usability requirements. It shows how this method can be integrated into a software development process, by discussing how the existing software framework workflows can be adjusted to take this new activity into consideration. A preliminary exercise was conducted to help discern the utility and the limits of the proposed method. Participants with different levels of knowledge of usability and comprehension of the system being developed found the method constructive, as it guided them in identifying the architecturally relevant usability requirements. It also helped determine the usability aspects that would not necessarily have been defined if this technique had not been employed.