Details
| Original language | English |
|---|---|
| Title of host publication | 1996 Proceedings - International Conference on Software Engineering |
| Pages | 522-531 |
| Number of pages | 10 |
| Publication status | Published - 1996 |
| Externally published | Yes |
| Event | 1996 18th International Conference on Software Engineering - Berlin Duration: 25 Mar 1996 → 29 Mar 1996 |
Publication series
| Name | Proceedings - International Conference on Software Engineering (Print) |
|---|---|
| Publisher | 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 subject areas
- Computer Science(all)
- Software
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
1996 Proceedings - International Conference on Software Engineering. 1996. p. 522-531 (Proceedings - International Conference on Software Engineering (Print)).
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
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 -