Software Development and Reality Construction 1992
DOI: 10.1007/978-3-642-76817-0_15
|View full text |Cite
|
Sign up to set email alerts
|

Artifacts in Software Design

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
3
0
1

Year Published

1993
1993
2014
2014

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 14 publications
(4 citation statements)
references
References 0 publications
0
3
0
1
Order By: Relevance
“…Even if the early knowledge management literature suggested that knowledge was an asset that could be simply externalized, circulated amongst knowledge workers and internalized by them (Nonaka and Takeushi, ), we now know that knowledge cannot be stored in a knowledge management system: it being conceived of as rational capacity held by humans prevents that (Nonaka et al ., ). Without dispute, artifacts can serve as “external memory” (Keil‐Slawik, ), and knowledge workers externalize their individual knowledge in multimedia assets that are shared within a community or organization. The main reason why many authors regarded knowledge as exchangeable asset seems to be based on exactly this necessity of external artifacts for acquiring, storing, and sharing knowledge (Erren, ), (Alavi and Leidner, ), (Carlsson et al ., ) (McQueen, ) (Zack, ).…”
Section: Typology Of Knowledge Worker Rolesmentioning
confidence: 99%
“…Even if the early knowledge management literature suggested that knowledge was an asset that could be simply externalized, circulated amongst knowledge workers and internalized by them (Nonaka and Takeushi, ), we now know that knowledge cannot be stored in a knowledge management system: it being conceived of as rational capacity held by humans prevents that (Nonaka et al ., ). Without dispute, artifacts can serve as “external memory” (Keil‐Slawik, ), and knowledge workers externalize their individual knowledge in multimedia assets that are shared within a community or organization. The main reason why many authors regarded knowledge as exchangeable asset seems to be based on exactly this necessity of external artifacts for acquiring, storing, and sharing knowledge (Erren, ), (Alavi and Leidner, ), (Carlsson et al ., ) (McQueen, ) (Zack, ).…”
Section: Typology Of Knowledge Worker Rolesmentioning
confidence: 99%
“…The other relevant aspect of communication processes is the creation of artifacts as a materialization of knowledge. Artifacts are all kinds of reproducible physical or digital results of an externalization process (e.g., books, digital media or certificates) and serve as an external memory (Keil Slawik, 1992). Creating an artifact often goes along with the abstraction from the subject domain and therefore is equivalent to a de-contextualization of the content.…”
Section: Symbolic Interactionismmentioning
confidence: 99%
“…Of course, that is only possible if the programmer reduced some limited domain of intelligent behavior to algorithmic rules (or heuristic rules that were close enough to mimic human decisions most of the time) and then programmed these into the software. The meaning of the software's behavior is derived from the human software designer's symbolic external representations (Keil-Slawik, 1992) in the programming language. The user notices traces of the designer's intention in the form of the operational software artifact.…”
Section: Embedding Meaning In Softwarementioning
confidence: 99%