Rapid prototyping of interactive information systems

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

doi:10.1145/1006258.1006289

Cited by 53 publications

(8 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Details on prototyping of interactive information systems, and on the USE methodology itself, are discussed elsewhere [1] - [3] .…”

Section: The User Software Engineering Methodologymentioning

confidence: 99%

“…The principal tool used for this process is RAPID/USE (Rapid Application Development), which serves both as a tool for rapid prototyping of the user interface and for the rapid development of interactive systems [1] , [11]. RAPID/USE has two subsystems: the Transition Diagram Interpreter (TDI) and the Action Linker.…”

Section: Interactionmentioning

confidence: 99%

“…The Transition Diagram Interpreter (TDI) [1], [11] then interprets the encoded diagrams, making it possible to allow a user to interact with a "mockup" of the user interface design. This ability to "execute" the dialog, even in the absence of actions, is of tremendous value in application of the methodology because it gives the user at the terminal a good understanding of the expected behavior of the liS, and gives the developer a good understanding of the user's problems with the dialog design.…”

Section: Interactionmentioning

confidence: 99%

See 2 more Smart Citations

Building reliable interactive information systems

Wasserman¹,

Piercher²,

Shewmake³

1986

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

User Software Engineering is a methodology, with supporting tools, for the specification, design, and implementation of interactive information systems. With the USE approach, the user interface is formally specified with augmented state transition diagrams, and the operations may be formally specified with preconditions and postconditions. The USE state transition diagrams may be directly executed, with the application development tool RAPID/USE. RAPID/USE and its associated tool RAPSUM create and analyze logging information that is useful for system testing, and for evaluation and modification of the user interface. We briefly describe the USE transition diagrams and the formal specification approach, and show how these tools and techniques aid in the creation of reliable interactive information systems.

show abstract

“…Details on prototyping of interactive information systems, and on the USE methodology itself, are discussed elsewhere [1] - [3] .…”

Section: The User Software Engineering Methodologymentioning

confidence: 99%

Section: Interactionmentioning

confidence: 99%

Section: Interactionmentioning

confidence: 99%

See 1 more Smart Citation

Building reliable interactive information systems

Wasserman¹,

Piercher²,

Shewmake³

1986

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

show abstract

“…An example of an environment that supports the development of information systems and that includes rapid prototyping tools is USE [Wass82] (See Section 4.3.4).…”

Section: The Documentation Editormentioning

confidence: 99%

Characteristics and functions of software engineering environments

Houghton¹,

Wallace²

1985

View full text Add to dashboard Cite

As part of the program to provide information to Federal agencies on software tools for improving quality and productivity in software development and maintenance, data was collected on software engineering environments. Software engineering environments surround their users with software tools necessary for systematic development and maintenance of software. The purpose of this report is to characterize software engineering environments by type and by their relationship to the software life cycle and by their capabilities, limitations, primary users, and levels of support. This report provides examples of existing software engineering environments that are available commercially or in research laboratories. KEYWORDS framing environments; human factors; life cycle coverage; programming environments; software analysis; software engineering; software engineering environments; software support; software tools. FOREWORD Under the Brooks Act, the National Bureau of Standards Institute for Computer Sciences and Technology (ICST) promotes the cost effective selection, acquisition, and utilization of automatic data processing resources within Federal agencies. ICST efforts include research in computer science and technology, direct technical assistance, and the development of Federal standards for data processing equipment, practices, and software.ICST has published several documents on software tools as part of this responsibility and the growing recognition that the use of software tools and software engineering environments can reduce the effort necessary to develop and maintain computer software. The guidance is designed to assist Federal agencies in automating and standardizing their software development and maintenance projects. This report presents the results of the analysis of data and experience accumulated on software engineering environments. It characterizes environments and describes their features to enable readers to gain an understanding of how environments can aid software development and maintenance process. Future ICST documents will provide guidance in selecting and using software engineering environments.Certain commercial products are identified in this paper for clarification of specific concepts. In no case does such identification imply recommendation or endorsement by the National Bureau of Standards, nor does it imply that the material identified is necessarily the best for the purpose.

show abstract

“…While much work in software engineering in past decade has been directed at narrowing this gap [9,16], it seems prima facie that a focus on detailed narratives of user interaction may widen it anew.…”

Section: Introductionmentioning

confidence: 99%

Integrating task and software development for object-oriented applications

Rosson

Carroll

1995

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

View full text Add to dashboard Cite

We describe an approach to developing object-oriented applications that seeks to integrate the design of user tasks with the design of software implementing these tasks. Using the Scenario Browser -an experimental environment for developing Small talk applications -a designer employs a single set of task scenarios to envision and reason about user needs and concerns and to experiment with and refine object-oriented software abstractions. We argue that the shared context provided by the scenarios promotes rapid feedback between usage and software concerns, so that mutual constraints and opportunities can be recognized and addressed early and continuingly in the development process.

show abstract

Rapid prototyping of interactive information systems

Cited by 53 publications

References 6 publications

Building reliable interactive information systems

Building reliable interactive information systems

Characteristics and functions of software engineering environments

Integrating task and software development for object-oriented applications

Contact Info

Product

Resources

About