Talk:Artifact (software development)
|Sources for development of this article may be located at|
Please, it seems that everything is an artifact ; specs, plans, source code, executables, applications, documentation ...
What is NOT an artifact ? Which is the differentiation criteria ?
I think that, even in software-development area, this word should be used with a meaning close to its "root" meaning, i.e. (from Wikipedia) "An artifact or artefact is any object made or modified by a human"
This article is horrible
The language seems to be intentionally obscured. Or maybe translated through English-German-Klingon-Russian-English machine translation.
For example the paragraph talking about Illuminated Manuscripts does not make any sense whatsoever.
Are there any references for the narrow meaning "byproduct"? AFAIK, an artifact can be any output of a development process (source code, documentation, requirements documents, design, executables, test results, etc.). -- 220.127.116.11 (talk) 10:56, 26 August 2011 (UTC)
"An artifact or artefact is any object made or modified by a human". Is a file an object? No it is changes in a magnetic field on a hard drive. I don't like the use of the word artifact when it comes to files. — Preceding unsigned comment added by 18.104.22.168 (talk) 08:34, 1 June 2012 (UTC)
- Indeed; I would also take issue with the use of the word "tangible", too. It seems to me that most (all?) of the artefacts mentioned are intangible (well, as documents they could be printed out). Something like a walkthrough would seem to be an event, so not even something which can be printed out (unless "walkthrough" refers to a document produced while doing a walkthrough). Pippin (talk) 13:25, 1 April 2014 (UTC)