2001
DOI: 10.21236/ada387874
|View full text |Cite
|
Sign up to set email alerts
|

Achieving Usability Through Software Architecture

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
34
0
3

Year Published

2002
2002
2007
2007

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 46 publications
(40 citation statements)
references
References 0 publications
0
34
0
3
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%
See 2 more Smart Citations
“…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%
See 1 more Smart Citation
“…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%