Computer aided design (CAD) systems, or more generally interactive software, are today being developed for various application areas like VLSI-design, mechanical structure design, avionics design, cartographic design, architectual design, office automation, publishing, etc. Such tools are becoming more and more important in order to be productive and to be able to design quality products. One important part of CAD-software development is the man-machine interface (MMI) design.
Johan H. Aas, Karsten Brathen, Erik Nordo, and Ole Ø. Ørpen
Modeling, Identification and Control, Vol 10, Iss 1, Pp 53-63 (1989)
Subjects
Man-machine systems, human factors, underseas systems, prototyping, system analysis, guidance systems, Electronic computers. Computer science, and QA75.5-76.95
Abstract
Important man-machine interface (MMI) issues concerning a submarine command and weapon control system (CWCS) such as crew organization, automation level and decision support are discussed in this paper. Generic submarine CWCS functions and operating conditions are outlined. Detailed, dynamic and real-time prototypes were used to support the MMI design. The prototypes are described and experience with detailed prototyping is discussed. Some of the main interaction principles are summarized and a restricted example of the resulting design is given. Our design experience and current work have been used to outline future perspectives of MMI design in naval CWCSs. The need for both formal and experimental approaches is emphasized.
Australasian Journal of Information Systems, Vol 2, Iss 2 (1995)
Subjects
evolutionary prototyping, Information technology, T58.5-58.64, Electronic computers. Computer science, and QA75.5-76.95
Abstract
The failure of many Information Systems (IS) designed for use by managers may be due to the fact that traditional IS methodologies were used in their development. In this paper we describe an organisation's efforts, over a period of four years, to develop an IS for use by senior management and show how traditional methodologies have impeded the involvement of the intended users of the system from the development process resulting in poor specification of user requirements and inflexible systems. From this experience we verify the superiority of an evolutionary prototyping methodology for the development of these types of systems.
