Towards Pattern-based Generic Interaction Scenarios

Biel, Bettina; Seitz, Stefan; Gruhn, Volker

doi:10.1016/j.procs.2011.07.103

Cited by 2 publications

(1 citation statement)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The changes in how usability has been addressed in SE have led to the proposal and research of solutions that cover the entire software development cycle from requirements elicitation (Juristo, et al, 2007b), through architecture (Biel et al, 2011) (John et al, 2009) ) (Bass and John, 2003) ) and high-level design, to low-level design and implementation (Folmer et al, 2006). John et al (2009) describe a study applying architecture patterns to support business-level usability.…”

Section: Patterns For Se Usabilitymentioning

confidence: 99%

Design and programming patterns for implementing usability functionalities in web applications

Rodríguez

Acuña

Juristo

2015

Journal of Systems and Software

View full text Add to dashboard Cite

Esta es la versión de autor del artículo publicado en: This is an author produced version of a paper published in:Journal of Systems and Software 105 (2015) AbstractUsability is a software system quality attribute. There are usability issues that have an impact not only on the user interface but also on the core functionality of applications. In this paper, three web applications were developed to discover patterns for implementing two usability functionalities with an impact on core functionality: Abort Operation and Progress Feedback. We applied an inductive process in order to identify reusable elements to implement the selected functionalities. For communication purposes, these elements are specified as design and programming patterns (PHP, VB .NET and Java). Another two web applications were developed in order to evaluate the patterns. The evaluation explores several issues such as ease of pattern understanding and ease of pattern use, as well as the final result of the applications. We found that it is feasible to reuse the identified solutions specified as patterns. The results also show that usability functionalities have features, like the level of coupling with the application or the complexity of each component of the solution, that simplify or complicate their implementation. In this case, the Abort Operation functionality turned out to be more feasible to implement than the Progress Feedback functionality.

show abstract