Loading [MathJax]/extensions/tex2jax.js

Prototypes as assets, not toys why and how to extract knowledge from prototypes

Publikation: Beitrag in Buch/Bericht/Sammelwerk/KonferenzbandAufsatz in KonferenzbandForschungPeer-Review

Autorschaft

Externe Organisationen

  • University of Colorado Boulder

Details

OriginalspracheEnglisch
Titel des Sammelwerks1996 Proceedings - International Conference on Software Engineering
Seiten522-531
Seitenumfang10
PublikationsstatusVeröffentlicht - 1996
Extern publiziertJa
Veranstaltung1996 18th International Conference on Software Engineering - Berlin
Dauer: 25 März 199629 März 1996

Publikationsreihe

NameProceedings - International Conference on Software Engineering (Print)
Herausgeber (Verlag)IEEE Computer Society
ISSN (Print)0270-5257

Abstract

Software prototypes are becoming more and more important, as computer applications invade new domains and as personal prototyping environments become more powerful. Although numerous approaches recommend their use, prototypes are sometimes treated like their developers' personal toys, and little effort is made to extract and share the experiences and knowledge that emerged as a by-product of building the prototype. In this paper, a strategy is proposed to extract crucial pieces of knowledge from a prototype and from its developer. The strategy is based on monitoring explanations that developers give, analyzing their structure, and feeding results back to support and to focus explanations. During this process, the prototype turns into the centerpiece of a hyperstructured information base, which can be used to convey concepts, implementation tricks and experiences. If organizations begin to view - and treat - prototypes as executable representations of knowledge, they can fully capitalize on the assets prototypes really are.

ASJC Scopus Sachgebiete

Zitieren

Prototypes as assets, not toys why and how to extract knowledge from prototypes. / Schneider, Kurt.
1996 Proceedings - International Conference on Software Engineering. 1996. S. 522-531 (Proceedings - International Conference on Software Engineering (Print)).

Publikation: Beitrag in Buch/Bericht/Sammelwerk/KonferenzbandAufsatz in KonferenzbandForschungPeer-Review

Schneider, K 1996, Prototypes as assets, not toys why and how to extract knowledge from prototypes. in 1996 Proceedings - International Conference on Software Engineering. Proceedings - International Conference on Software Engineering (Print), S. 522-531, 1996 18th International Conference on Software Engineering, Berlin, 25 März 1996.
Schneider, K. (1996). Prototypes as assets, not toys why and how to extract knowledge from prototypes. In 1996 Proceedings - International Conference on Software Engineering (S. 522-531). (Proceedings - International Conference on Software Engineering (Print)).
Schneider K. Prototypes as assets, not toys why and how to extract knowledge from prototypes. in 1996 Proceedings - International Conference on Software Engineering. 1996. S. 522-531. (Proceedings - International Conference on Software Engineering (Print)).
Schneider, Kurt. / Prototypes as assets, not toys why and how to extract knowledge from prototypes. 1996 Proceedings - International Conference on Software Engineering. 1996. S. 522-531 (Proceedings - International Conference on Software Engineering (Print)).
Download
@inproceedings{3851c12af8f74ce1be3cf8acbb7244be,
title = "Prototypes as assets, not toys why and how to extract knowledge from prototypes",
abstract = "Software prototypes are becoming more and more important, as computer applications invade new domains and as personal prototyping environments become more powerful. Although numerous approaches recommend their use, prototypes are sometimes treated like their developers' personal toys, and little effort is made to extract and share the experiences and knowledge that emerged as a by-product of building the prototype. In this paper, a strategy is proposed to extract crucial pieces of knowledge from a prototype and from its developer. The strategy is based on monitoring explanations that developers give, analyzing their structure, and feeding results back to support and to focus explanations. During this process, the prototype turns into the centerpiece of a hyperstructured information base, which can be used to convey concepts, implementation tricks and experiences. If organizations begin to view - and treat - prototypes as executable representations of knowledge, they can fully capitalize on the assets prototypes really are.",
author = "Kurt Schneider",
year = "1996",
language = "English",
series = "Proceedings - International Conference on Software Engineering (Print)",
publisher = "IEEE Computer Society",
pages = "522--531",
booktitle = "1996 Proceedings - International Conference on Software Engineering",
note = "1996 18th International Conference on Software Engineering ; Conference date: 25-03-1996 Through 29-03-1996",

}

Download

TY - GEN

T1 - Prototypes as assets, not toys why and how to extract knowledge from prototypes

AU - Schneider, Kurt

PY - 1996

Y1 - 1996

N2 - Software prototypes are becoming more and more important, as computer applications invade new domains and as personal prototyping environments become more powerful. Although numerous approaches recommend their use, prototypes are sometimes treated like their developers' personal toys, and little effort is made to extract and share the experiences and knowledge that emerged as a by-product of building the prototype. In this paper, a strategy is proposed to extract crucial pieces of knowledge from a prototype and from its developer. The strategy is based on monitoring explanations that developers give, analyzing their structure, and feeding results back to support and to focus explanations. During this process, the prototype turns into the centerpiece of a hyperstructured information base, which can be used to convey concepts, implementation tricks and experiences. If organizations begin to view - and treat - prototypes as executable representations of knowledge, they can fully capitalize on the assets prototypes really are.

AB - Software prototypes are becoming more and more important, as computer applications invade new domains and as personal prototyping environments become more powerful. Although numerous approaches recommend their use, prototypes are sometimes treated like their developers' personal toys, and little effort is made to extract and share the experiences and knowledge that emerged as a by-product of building the prototype. In this paper, a strategy is proposed to extract crucial pieces of knowledge from a prototype and from its developer. The strategy is based on monitoring explanations that developers give, analyzing their structure, and feeding results back to support and to focus explanations. During this process, the prototype turns into the centerpiece of a hyperstructured information base, which can be used to convey concepts, implementation tricks and experiences. If organizations begin to view - and treat - prototypes as executable representations of knowledge, they can fully capitalize on the assets prototypes really are.

UR - http://www.scopus.com/inward/record.url?scp=0029537756&partnerID=8YFLogxK

UR - https://www.computer.org/csdl/proceedings-article/icse/1996/00493396/12OmNyOq4S5

M3 - Conference contribution

AN - SCOPUS:0029537756

T3 - Proceedings - International Conference on Software Engineering (Print)

SP - 522

EP - 531

BT - 1996 Proceedings - International Conference on Software Engineering

T2 - 1996 18th International Conference on Software Engineering

Y2 - 25 March 1996 through 29 March 1996

ER -

Von denselben Autoren