The phrase "artifact concept" is correct and usable in written English.
It can be used in contexts related to design, software development, or any field where the idea of an artifact is discussed, particularly in relation to its conceptual framework.
Example: "In our project, we need to clarify the artifact concept to ensure all team members understand its significance in the development process."
Alternatives: "artifact model" or "artifact idea".
Judging function and assigning category are thus cognitive tasks that draw on different information across development, a fact that should be captured by theories of developing artifact concept structure.
(iii) This effect on problem solving is not caused by differences in the amount of knowledge that children have about the typical use of a particular tool; it is mediated by the structure of the child's artifact concept (which organizes and deploys the child's knowledge).
We argue that the older children were slower to solve the problem when the typical function was primed because (i) their artifact concept plays a role in problem solving, and (ii) intended purpose is central to their concept of artifact function, but not to that of the younger children.
In four experiments, we tested conditions under which artifact concepts support inference and coherence in causal categorization.
Usually, a methodology based on experimentation is suggested in order to avoid wasted effort and to minimize problems when assessing the use of an artifact (concepts, tools, techniques, methods or methodologies) (Shull et al. 2001).
More recent work that shows promise is that of Moldovan and Rus (2001), aimed at interpreting WordNet glosses for nominal artifact concepts, and that of Allen et al. (2013), aimed at forming logical theories of small clusters of related verbs (e.g., sleeping, waking up, etc).
As Lakoff and Johnson point out, this framework is a cultural artifact, grounding concepts in a familiar, concrete context.
With the improvement of three-dimensional reconstruction techniques [ 4– 7] and reduction of artifacts, the concept of applying flat detectors for X-ray computed tomography had been investigated for several years.
In the following "detailed design phase," Prometheus provides an approach on how to transform the design artifacts into concepts of the JACK agent programming language [26].
As a result, software engineering is dealing with a wider range of artifacts and concepts (i.e., in the context of this paper: services and business processes) than ever before.
For more on the concept of artifacts see the entry Artifacts.
