Achieving Usability Through Software Architecture

Bass, Len; John, Bonnie E.; Kates, Jesse

doi:10.21236/ada387874

Cited by 46 publications

(40 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…They used a bottom-up approach by Table 1 Providing an undo scenario (adapted from Bass et al (2001))…”

Section: Usability Requirements: Two Different Beliefsmentioning

confidence: 99%

“…For example, the providing feedback property, which discusses the need that the system provide, whenever appropriate, feedback to the users to keep them informed of what is going on, groups together the predicting task duration, observing system state and maintaining device independence scenarios. Bass and his team (Bass et al, 2001) gave an architectural pattern for each identified scenario, which provides a solution to implementing the scenario. Those architectural patterns reflect a possible solution; more specifically, the implementation of a usability pattern.…”

Section: From Uqaw To Architectural Designmentioning

confidence: 99%

“…The most cost-effective way of ensuring the usability of software systems is to consider the integration of usability into the initial discussion of quality requirements. Although few authors (Bass et al, 2001;Bass and John, 2003;Folmer and Bosch, 2004;Rafla et al, 2004Rafla et al, , 2006 have investigated the relationship between usability and software architecture, little is known yet as how to capture and organize the usability requirements that are architecturally significant.…”

mentioning

confidence: 99%

See 2 more Smart Citations

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

2007

View full text Add to dashboard Cite

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.

show abstract

“…They used a bottom-up approach by Table 1 Providing an undo scenario (adapted from Bass et al (2001))…”

Section: Usability Requirements: Two Different Beliefsmentioning

confidence: 99%

Section: From Uqaw To Architectural Designmentioning

confidence: 99%

mentioning

confidence: 99%

See 1 more Smart Citation

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

2007

View full text Add to dashboard Cite

show abstract

“…Some previous work has been done in this area: Traetteberg [28] presents model fragments that can be used for UI patterns. Bass et al [4] identified scenarios that illustrate particular aspects of usability that are architecture-sensitive and suggest architectural patterns for implementing these scenarios. A framework, which expresses the relationship between usability and software architecture consisting of 15 architecture sensitive usability patterns, was presented in [11].…”

Section: Bridging Patternsmentioning

confidence: 99%

“…While both disciplines developed themselves, several gaps have appeared which are now receiving increased attention in research literature. Major gaps of understanding, both between suggested practice and how software is actually developed in industry, but also between the best practices of each of the fields have been identified [3][4][5]. In addition, there are gaps in the fields of differing terminology, concepts, education, and methods [6].…”

Section: Introductionmentioning

confidence: 99%

Bridging patterns: An approach to bridge gaps between SE and HCI

Folmer

Welie

Bosch

2006

Information and Software Technology

View full text Add to dashboard Cite

Software Architecture Modeling for User Interfaces

Coutaz

2002

Encyclopedia of Software Engineering

View full text Add to dashboard Cite

Architectural modeling is becoming a central problem for large, complex systems. With the advent of new technologies and user-centered concerns, the user interface portion of interactive systems is becoming increasingly large and complex. This chapter is a reflection on software architecture modeling for interactive systems. In this domain, a number of architectural frameworks have emerged as canonical references. Although these models provide useful insights about how to partition and organize interactive systems, they do not always address important problems identified by main stream software architecture modeling. We first introduce the notion of software architecture and make explicit the steps and issues that architectural design involves and that most software designers tend to blend in a rather fuzzy way. Building on general concepts, a comparative analysis of the most significant refernce models developed for interactive systems is then presented: the Seeheim and Arch models followed by the more recent agent-based approaches that can be shaped to support multimodal interaction and groupware.

show abstract

Achieving Usability Through Software Architecture

Cited by 46 publications

References 0 publications

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

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

Bridging patterns: An approach to bridge gaps between SE and HCI

Software Architecture Modeling for User Interfaces

Contact Info

Product

Resources

About