Case studies on analyzing software architectures for usability

Studies of software engineering projects reveal that a large number of usability related change requests are made after its deployment. Fixing certain usability problems during the later stages of development has proven to be costly, since some of these changes require changes to the software architecture i.e. this often requires large parts of code to be completely rewritten. Explicit evaluation of usability during architectural design may reduce the risk of building a system that fails to meet its usability requirements and may prevent high costs incurring adaptive maintenance activities once the system has been implemented. In this paper, we demonstrate the use of a scenario based architecture analysis technique for usability we developed, at two case studies.

[1]  John Edgar Tidwell,et al.  Common ground: a pattern language for human-computer interface design , 1997 .

[2]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[3]  Jan Bosch,et al.  A framework for capturing the relationship between usability and software architecture , 2003, Softw. Process. Improv. Pract..

[4]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[5]  Rick Kazman,et al.  An approach to software architecture analysis for evolution and reusability , 1997, CASCON.

[6]  Leonard J. Bass,et al.  SAAM: a method for analyzing the properties of software architectures , 1994, Proceedings of 16th International Conference on Software Engineering.

[7]  Rick Kazman,et al.  The architecture tradeoff analysis method , 1998, Proceedings. Fourth IEEE International Conference on Engineering of Complex Computer Systems (Cat. No.98EX193).

[8]  Søren Lauesen,et al.  Six Styles for Usability Requirements , 1998, REFSQ.

[9]  Jan Bosch,et al.  Architecture level prediction of software maintenance , 1999, Proceedings of the Third European Conference on Software Maintenance and Reengineering (Cat. No. PR00090).

[10]  Ergonomic requirements for office work with visual display terminals ( VDTs ) — Part 11 : Guidance on usability , 1998 .

[11]  Jan Bosch,et al.  Design erosion: problems and causes , 2002, J. Syst. Softw..

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

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

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

[15]  W. Buxton.  Human-Computer Interaction , 1988, Springer Berlin Heidelberg.

[16]  Hallvard Trætteberg,et al.  Interaction Patterns in User Interfaces. , 2000 .

[17]  Jan Bosch,et al.  Experiences with ALMA: Architecture-Level Modifiability Analysis , 2002, J. Syst. Softw..

[18]  Jan Bosch,et al.  Software Architecture Analysis of Usability , 2004, EHCI/DS-VIS.