2001
DOI: 10.1007/3-540-44675-3_11
|View full text |Cite
|
Sign up to set email alerts
|

Formal Interactive Systems Analysis and Usability Inspection Methods: Two Incompatible Worlds?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2002
2002
2017
2017

Publication Types

Select...
4
1

Relationship

1
4

Authors

Journals

citations
Cited by 10 publications
(10 citation statements)
references
References 16 publications
0
10
0
Order By: Relevance
“…This similarity is discussed in more detail in Loer and Harrison (2001). Both analysis techniques focus on the systematic application of properties or heuristics to explore unforeseen consequences of the design.…”
Section: Bringing the Communities Togethermentioning
confidence: 98%
See 1 more Smart Citation
“…This similarity is discussed in more detail in Loer and Harrison (2001). Both analysis techniques focus on the systematic application of properties or heuristics to explore unforeseen consequences of the design.…”
Section: Bringing the Communities Togethermentioning
confidence: 98%
“…A number of approaches including (Abowd et al, 1995;d'Ausbourg, 1998;Campos and Harrison, 2001;Paternò, 1996;Loer, 2003), have developed usability requirements formally. Furthermore, (Loer and Harrison, 2001) describes how usability heuristics may be be translated into formal property specifications. While these activities illustrate technical feasibility they do not demonstrate that the techniques used are acceptable for use by the target audience of usability and system engineers.…”
Section: Development and Representation Of Property Specificationsmentioning
confidence: 99%
“…Following this view of user interface structure, the authors develop a formal specification of a research reactor used in the University of Virginia Reactor (UVAR) for training nuclear engineering students, radiation damage studies, and other studies (Loer and Harrison 2000). In order to illustrate the specification layers, the authors focus on the safety control rod system, one of the reactor subsystems.…”
Section: Knight Et Al (Usa 1992-2010)mentioning
confidence: 99%
“…A third reason for the effectiveness of IW is that the assessor can choose any programming language or approach to construct the simulation -thus allowing them to work in a much more suitable programming environment than perhaps the implementors of the actual target system were able to. For example, the implementors of the target system may have had to use assembler or PIC code, whereas the IW assessor can use Java, SMV [9,10], or Promela -or any special purpuse GUI languages, such as VEG [1] -as they wish. Using a 'nice' language with powerful abstraction features, particularly one with model checking, appropriate for the interactive simulation will highlight inconsistencies in the target design in a way that cannot be done on the target system.…”
Section: Discussionmentioning
confidence: 99%
“…Fifth, the assessor can use a full range of modern model checking and theorem proving techniques to check the interface against desirable interaction properties. Loer and Harrison give persuasive examples [9,10] of the effectiveness of this approach -indeed, their work is essentially IW, as they had to reverse engineer systems (though their approach is suited to early use in software production, on the assumption that formal specifications are available), and their systems do not have the performance to be production systems.…”
Section: Discussionmentioning
confidence: 99%