This paper describes an approach to specifying the page formats presented on a Control display Unit (CDU) for a navigation system. Traditionally, such displays, and the transitions between them, have been specified on paper, which the crew is asked to review before the system is built. The crew members cannot get a good feel for a system until very close to actual flight test, at which point it is extremely expensive to change the page formats and transitions. To circumvent these problems, we have implemented a system for building mockups of the entire CDU, both displays and keys. The systems engineer designs the page formats and transitions, using high resolution bit map displays and a mouse. The crew is then allowed to 'fly' the simulation, to get a feel for the proposed system. Any changes suggested can quickly be incorporated into the model. This paper discusses different approaches for building/acquiring a tool to create these user interface prototypes, with the advantages and drawbacks to each. Results of using the tool on several actual programs are given, including reactions from crew makers and effect on requirements.
Rapid prototyping of pilot interfaces as an aid to defining software requirements
Schnelle Erstellung von Prototypen fuer Piloten-Interfaces als Hilfsmittel zur Definition von Software-Anforderungen
1986
8 Seiten, 12 Bilder, 8 Quellen
Conference paper
English
Requirements for Rapid Prototyping of Crew Station Displays
SAE Technical Papers | 1988
|Defining Software Requirements for Safety Critical Functions
British Library Conference Proceedings | 1994
|Formation of a software rapid prototyping platform
Tema Archive | 1999
|Cubital's efficient response to automotive rapid prototyping and tooling requirements
Automotive engineering | 1994
|Cubital's Efficient Response to Automotive Rapid Prototyping and Tooling Requirements
British Library Conference Proceedings | 1994
|