Key points are not available for this paper at this time.
The article focuses on the role of knowledge in software development. Key concepts have been developed by researchers in the cognitive sciences to account for the various aspects of knowledge processing. Some of them are derived from the content or structure of knowledge, others from its representation. Here, "knowledge" refers to a permanent structure of information stored in memory. There are many ways to define knowledge. Episodic knowledge consists of one's experience with knowledge. Topic knowledge refers to the meaning of words, such as definitions in dictionaries and textbooks. Software development requires topic and episodic knowledge. Difficulties may arise when software developers have only topic knowledge of the application domain may be left out of the software being developed. The quality of the software design derived from a methodology can vary according to the designer's episodic knowledge of the methodology. Some methodologies may require more episodic knowledge than others and the level of episodic knowledge required should be measured or accounted for in some way when evaluating a methodology or the quality of a software design. Software development involves processing a large amount of information distributed over many knowledge domains that are more or less contiguous with fuzzy frontiers that are intertwined most of the time.
Pierre N. Robillard (Fri,) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: