Skip to main content

1984 | Buch

Approaches to Prototyping

herausgegeben von: Reinhard Budde, Karin Kuhlenkamp, Lars Mathiassen, Heinz Züllighoven

Verlag: Springer Berlin Heidelberg

insite
SUCHEN

Über dieses Buch

"This conference will focus on the user-oriented development of information systems. Against a background of recent concepts for the implementation of distributed systems based on workstation computers, various communicational, organizational and social issues gain increasing importance in the construct ion of computer based information systems. There is an urgent need to integrate end-users and other affected groups into the development process. New strategies for system development are thus needed. " This was the beginning of the Call for Papers to the Working Conference on Prototyping. Working in the fields of user-oriented software construct ion and the analysis of communication problems between developers and users we, that is the GMD­ team involved in this conference and in preparing its Proceedings, sooner or later came across various new concepts to overcome the problems sketched above. Concepts focusing on the quick construct ion of an operative system such as "rapid prototyping" or concepts aiming at the human and organizational side of the development process such as "Systemeering". Even on a second look, the multitude of different approaches, terms and tools still caused confusion. But despite the differences every concept seemed to have something to do with "Prototyping". This, however, proved to be of little help to us, because the term "Prototyping" itself turned out to be quite "fuzzy". In this obviously confused situation we decided that it was time for a working con­ ference.

Inhaltsverzeichnis

Frontmatter

Overview Presentations

A Systematic Look at Prototyping
Abstract
This paper originates from a series of discussions between programme committee members during the preparation of the Working Conference on Prototyping. While trying to define the topic of the conference, it became clear to us that we each held our own viewpoint on the subject. Views differed as to the specific use of terminology as well as the application-oriented emphasis on particular strategies, and so did our judgements about the potential usefulness of prototyping. The views did not, however, seem contradictory but rather complementary.
Christiane Floyd
Advancing the State of the Art in Software System Prototyping
Abstract
We discuss what software prototyping is, relate some experiences in prototyping a software engineering environment, and draw some conclusions about advancements critical to improving the state of the art in software prototyping.
William E. Riddle

Working Group “Prototyping: Concepts, Tools, Experiences”

Summary of the Working Group “Concepts, Tools, Experiences”
Abstract
The working group CTE appeared to be the largest group according to contributions and participants. The group consisted of 11 contributions of which six were selected for plenary presentations. In plenary presentations the programme committee wanted ideas of general interest to be presented, or the presentation was expected to be a paradigm for other contributions within the working group.
Karl-Heinz Sylla

Working Group “Prototyping and Database Design”

Papers presented

The BOP Prototyping Concept
Abstract
Prototyping is a well-known technique within engineering disciplines. The paper describes some main advantages by applying this technique to computer systems development, and why this can reduce development time and cost significantly as well as assuring a system better adapted to the users’ demands.
The BOP prototyping tool is designed for prototyping of interactive information systems, especially the user interface and functional characteristics of such systems. It consists of a relational data base, a set of preprogrammed functions, and tools for prototype development. The paper also gives a brief outline of the iterative process of prototyping by BOP.
Jarle Aaram
Database Design Prototyping in a Codasyl Environment
Abstract
An approach is proposed for database design prototyping. Database design currently has a well established structure while prototyping of the process is a quite new subject of research.
In our proposal, prototyping makes it possible for the designer activity to be validated by the end user himself, while the database design is still under development.
Two points are of major importance in this validation process. First, the end user’s active role. This is essential because it is up to the end user to decide whether or not his/her requirements have been well understood by the designer.
As a second point, the validation is done as early as possible. This allows a quick identification of misunderstanding and thus avoids the propagation of design errors.
G. B. Demo, A. DiLeva, P. Giolito
The TUBA-Project: A Set of Tools for Application Development and Prototyping
F. A. van Hoeve, Rolf Engmann
Specification and Prototyping of Data Model Semantics
Abstract
Specification and prototyping semantics aids the design and analysis of complex software systems at a rather early stage of their development. This paper reports on experiences and research in data model semantic specification and specification-based data model interpretation. It presents experiences with using a formal semantic specification method in data base model standardization, applying a computer-based interpreter to data base model specifications, and prototyping the semantics of advanced data models based on the user interface of an existing data base management system.
W. Lamersdorf, J. W. Schmidt
Prototyping for Real-World Applicability Tests
Abstract
In the field of the construction of computer-based information systems various technological, organizational, methodological, and social issues are playing a very important role. The higher aims are “better” information systems and thus more effective information processing. In order to achieve the OPTIMAL SOLUTION of the effectiveness problem an integrated approach (covering the issues mentioned above) is necessary. The approach suggested is to develop flexible software prototypes in order to test the relevance of computer-based information systems to a real-world environment: that is not only the technical characteristics of a particular prototype are being tested but also its functionality, usability, operationality, and usefulness. The purpose of this paper is threefold: first, by way of introduction to give an overview of the methodology applicable to the design of computer-based information systems in heuristic terms; second, to present the managerial framework necessary to apply such a methodology; and third, to demonstrate an application of this methodology by describing a specific project. The project described aims to develop an operational software prototype of an integrated information and communication system for managing information resources at a working place.
Ivan Mistrik
Prototyping in an Environment Using Several Data Management Systems
E. Ortner, K. Wendler
Summary of the Working Group “Prototyping and Database Design”
Abstract
The working group has dealt with ‘concepts, tools and experience’ in the special context of database management systems. In addition to the papers presented to the working group we had a discussion about the paper of Mönckemeyer/Spitta dealing with specific database application.
Klaus-Dieter Kreplin

Working Group “Systems Development and Prototyping”

Papers presented

Prototyping in the Context of Information Systems Design
Abstract
The aim of this paper is to evaluate the prototype approach from a theoretical viewpoint. The paper emphasizes that in order to be able to exploit the potential and evident benefits of prototyping we should understand its limitations and context within information and data systems design. The analysis takes place in four major parts, in which the characteristics, context and limitations of prototyping and research into it are discussed.
Juhani Iivari
On the Psychology of Prototyping
Abstract
This paper relates the concepts underlying prototyping, evaluation and iteration, to properties of human cognition. Prototyping lends itself to humans’ acquisition of real-life experience as opposed to dealing with formalized descriptions. Based hereon the paper first argues that prototyping in the short term will weed inappropriate designs in that users’ say has more weight when based on prototypes than on written specifications. Secondly, as long as user interface design is suffering from lack of appropriate theories and methods, designs will be based on individual designer’s experience and intuition. These must therefore be cultivated in trying to achieve more usable interactive systems. Prototypes provide an efficient means to this end in that the designers are confronted with the consequences of their own decisions.
Anker Helms Jörgensen
Comments on “On the Psychology of Prototyping” by Anker Helms Jörgensen
Abstract
I have found this paper a very valuable contribution to the conference. The interface of software systems to the human users — interface taken in a wide sense — is the concern of at least much of what is called prototyping. It is touched upon in many of the papers. Here it is taken up more systematically.
Peter Naur
Comments on “On the Psychology of Prototyping” by Anker Helms Jörgensen
Abstract
It has been a pleasure to read Mr. Jörgensen’s paper in preparation for these comments. The paper brings together and states interestingly and clearly things that we have observed or suspected elsewhere plus some new insights into the specification problem, in particular its psychological aspects.
George Alexander Tingley
A Discussion of Prototyping within a Conceptual Framework
Summary
In this paper the notion of prototyping is discussed. The first part of the paper contains a presentation of a framework [1] used in this discussion. A discussion of programming viewed as a social activity is complex and requires an elaborated set of concepts by which we can express our opinions. The framework provides us with a set of such concepts.
In the second part of the paper prototyping is viewed through the spectacles introduced by the framework. This is done partly to express more precisely what is meant by the term PROTOTYPING, and partly to point out some problems that might rise if the prototyping-literature is used as a guideline for programming. Finally some relevant ideas and experiences from the UTOPIA-project are presented.
To sum up, the paper contains:
(1)
A presentation of a framework to be used when discussing programming.
 
(2)
A demonstration of the strenght of having a framework when programming is discussed.
 
(3)
A discussion of what is meant by the term prototyping.
 
(4)
A presentation of some problems that might rise if the prototyping-literature is used as a guideline for programming.
 
(5)
A presentation of some ideas and experiences from the UTOPIA-project.
 
John Kammersgaard
Property Determination by Prototyping
Abstract
In our opinion one of the most serious problems in connection with the use of computers in organizations today, is that the properties of computer based systems (CBS) do not meet the requirements raised during the systems development process (SDP).1
Finn Kensing
Organization Design Choices to Facilitate Evolutionary Development of Prototype Information Systems
Abstract
Current development methods which emphasize “getting the requirements right” prior to design and implementation are severely limited when building iterative, decisioncentered support systems. Prototype development by nature is evolutionary and has been advocated as one way to mitigate these limitations.
However, the success of evolutionary development is constrained by technical innovations, designing and programming practices and the organization environment: Organization decision makers should consider these constraints as variables, and given the fiscal and political realities of the organization, attempt an optimum balance among them.
While hardware and software considerations have been previously explored, the organization environment to support evolutionary development, and therefore successful implementation of prototype systems, has not been thoroughly discussed. Organization design choices to relieve the constraints to evolutionary development are discussed and two examples of organization design are presented.
John T. Nosek
Prototypes Versus Pilot Systems: Strategies for Evolutionary Information System Development
Overview
This paper aims to establish a connection between the new, evolutionary approach to the development of information systems, which relies on the use of prototypes or pilot systems, and the epistomology - the body of knowledge about knowledge. This is an important connection because the main purpose of prototypes and pilot systems is to enable designers of systems to learn about user needs and to help users to learn about the facilities that systems can offer.
The paper also aims to contrast the merits and limitations of prototypes versus those of pilot systems, drawing from the experience of well established engineering disciplines, in general, and from the author’s own experience, in particular.
In order to achieve these aims the subject matter is organized as follows. In the introduction consideration is given to problems of the relevance of information systems to the needs of their users and to the difficulties in foreseeing undesirable side effects of the introduction of computer-based systems into an organization. The factors that are pertinent to these two problems are identified and a strategy for controlling them is suggested. The inescapable fact that both the designers and users learn as the system is being developed is then related to theories of growth of knowledge which lead to the conclusion that the only sensible way to bring about an information system is by evolution. The important features of pilot systems and prototypes are then discussed and the attention of the reader is drawn to the different roles which these two tools of evolution play in traditional engineering disciplines. After a brief return to epistemology the author speculates about the future role of the user in information systems design.
George Rzevski
Prototyping: A Methodological Assessment
Abstract
The attractiveness of prototyping for problem-solving, and thus for the development of information systems and decision support systems, can be explained by referring to a specific modelcycle. It is demonstrated that prototyping can be looked upon as a specific instance of the methodology of simulation in a broad sense. Recent experiences with the application of a simulation approach to the development of information systems may be generalized towards prototyping. Emphasis on conceptual modeling and attention to the construction of a simulation model system are also valid for prototyping. This puts specific demands on the activities of verification, validation and experimentation. Prototyping is not only related to concrete model systems, but also to abstract ones. Prototyping is not restricted to the solution of datalogical and technological problems. It is also applicable to systelogical and infological problems as is demonstrated by some examples.
Henk G. Sol
The Development of Integrated Office Information Systems within the Framework of Trialog-Oriented Processes
Abstract
The design of complex information systems increasingly encounters uncertainties and difficulties especially on the part of naive users, i.e. those who are little familiar with data processing-oriented thought patterns. So far it has not been possible to obtain really convincing and complete concepts and to make significant fields of application an integral part of the everyday life of the users.
Stefan Sorg
Summary of the Working Group “Systems Development and Prototyping”
Lars Mathiassen

Working Group “Very High Level Languages for Prototyping”

Summary of the Working Group “Very High Level Languages for Prototyping”
Abstract
The working group dealt with the use of very high level languages for prototyping. The main outcome of the working group was not the personal level. Most of the participants have had experience with at least one VHLL. So after the discussions we all felt that our view was broadered, meanings have been qualified and questions like “which language for what purpose” have been made more conscious than before.
Reinhard Budde
Metadaten
Titel
Approaches to Prototyping
herausgegeben von
Reinhard Budde
Karin Kuhlenkamp
Lars Mathiassen
Heinz Züllighoven
Copyright-Jahr
1984
Verlag
Springer Berlin Heidelberg
Electronic ISBN
978-3-642-69796-8
Print ISBN
978-3-540-13490-9
DOI
https://doi.org/10.1007/978-3-642-69796-8