Rapid prototyping of interactive information systems

Wasserman, Anthony I.; Shewmake, D. T.

doi:10.1145/1006259.1006289

Cited by 9 publications

(9 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This development provided early and critical motivation and direction for research on user-interface management systems to enable prototyping (Tanner & Buxton, 1985); it encouraged user participation in design (Nygaard, 1979;Gould & Boies, 1983;Pava, 1983); it emphasized user-interface metaphors for presenting novel functionality through familiar concepts (Carroll & Thomas, 1982;Smith, Irby, Kimball, Verplank & Harslem, 1982); and it made ''rapid prototyping'' a standard system development methodology (Wasserman & Shewmake, 1982.…”

Section: Iterative Developmentmentioning

confidence: 99%

Human–computer interaction: psychology as a science of design

Carroll¹

1997

International Journal of Human-Computer Studies

139

View full text Add to dashboard Cite

Section: Iterative Developmentmentioning

confidence: 99%

Human–computer interaction: psychology as a science of design

Carroll¹

1997

International Journal of Human-Computer Studies

139

View full text Add to dashboard Cite

“…Each provides some unique benefits but also has some disadvantages [10]. Only a few are sufficiently formal or complete to be executed directly, and fewer still have interpreters [5,19].…”

Section: Ch1'83 Proceedings December 1983mentioning

confidence: 99%

Executable specifications for a human-computer interface

Jacob

1983

Proceedings of the SIGCHI Conference on Human Factors in Computing Systems - CHI '83

View full text Add to dashboard Cite

It is useful to be able to specify a proposed human-computer interface formally before building it, particularly if a mockup suitable for testing can be obtained directly from the specification. A specification technique for user interfaces, based on state transition diagrams, is introduced and then demonstrated for a secure message system application. An interpreter that executes the resulting specification ~s then described. Some problems that arise in specifying a user interface are addressed by particular features of the technique: To reduce the complexity of the developer's task, a user interface is divided into the semantic, syntactic, and lexical levels, and a separate executable specification is provided for each. A process of stepwise refinement of the syntactic specification, leading from an informal specification to an executable one is also presented. Since the state diagram notation is based on a nondeterministic model, constraints necessary to realize the system with a deterministic interpreter are given.Writing a formal specification of the user interface of a computer system before building it permits the interface designer to consider a variety of possible user interfaces and describe them precisely and compactly without actually having to code them. It also permits the application of human performance models to the specifications to obtain information about the user interfaces they describe before building them [1,15]. The specifications can be checked for certain undesirable properties of the user interface, such as almost-alike states [14], interactive deadlock [4], and character-level ambiguity [18]. Further benefits accrue if a prototype or mockup of the user interface of the proposed system can be constructed directly from the specification. Problems with the proposed user interface can then be identified early in the design process, when they are easier to fix. While many prcspective users will f_nd a formal specification of a proposed system difficult to understand, they will have much less trouble evaluating a mockup system and identifying deficiencies in its user interface, both through informal demonstrations and formal experiPermission to copy without fee all or part of this material is granted provided that the copies are not made or distributed for direct commercial advantage, the ACM copyright notice and the title of the publication and its date appear, and notice is given that copying is by permission of the Association for Computing Machinery. To copy otherwise, or to republish, requires a fee and/or specific permission.© 1983 ACM 0'89791-121-0/83/012/0028 $00.75 ments.This paper describes a specification technique for user-computer interfaces and its use in the development of a secure military message system. The specifications are executed interpretively to provide a working prototype of the system. The paper describes the specification technique by means of an example. Then, it shows the decomposition of both the design process and the specification itself into the semantic, ...

show abstract

“…Em geral, a experimentação no desenvolvimento de software pretende colocar mais esforços no entendimento dos requisitos (Blum & Houghton, 1982), com a expectativa de diminuir os custos das etapas de projeto (Weiser, 1982), de desenvolvimento e testes do sistema, uma vez que ele atenderá as necessidades dos usuários (Wasserman & Shewmake, 1982).…”

Section: Introductionunclassified

Percepão do MVP sob a ótica dos discentes do curso superior de informática

Ramalho¹,

Oliveira²

2022

RSD

View full text Add to dashboard Cite

Produto Mínimo Viável é uma versão enxuta do produto, utilizado também para sintetizar as ideais no momento de construir um software. Esta pesquisa analisa a percepção do MVP dos discentes dos cursos superiores de tecnologia da informação, futuros profissionais desenvolvedores de software. O estudo tem como finalidade demonstrar o conhecimento que é transmitido sobre esse tema nas Instituições de Ensino Superior e as lacunas no entendimento, por intermédio de uma pesquisa quali-quantitativa com 31 estudantes. Esta pesquisa tem objetivo exploratório e o procedimento adotado foi o survey. O primeiro resultado quantitativo demonstrou que grande parte dos estudantes já tinham experiência no mercado de trabalho e ou estágio, no entanto, quando foram questionados sobre o MVP e seus conceitos, uma parcela considerável não souberam expor suas ideias. Esses resultados podem evidenciar como o ensino de Engenharia de Software pode estar defasado, mesmo sendo um conhecimento essencial no dia a dia dos profissionais e na formação de estudantes da área de Tecnologia da Informação.

show abstract

Rapid prototyping of interactive information systems

Cited by 9 publications

References 0 publications

Human–computer interaction: psychology as a science of design

Human–computer interaction: psychology as a science of design

Executable specifications for a human-computer interface

Percepão do MVP sob a ótica dos discentes do curso superior de informática

Contact Info

Product

Resources

About