Hmm, that's weird. I always used "artifact" for "any physically or
virtually tangible item." In fact I just quizzed our devs here and asked
"do you consider a file of source code to be 'an artifact'?" and they all
So not to doubt the all knowing wikipedia, but my experience has been that
"artifacts" are everything from source artifacts (code) to deployable
artifacts like .wars to documentation of various forms... If I told
someone "back up all artifacts relating to that product" I'd expect the
source to be on that DVD too.
In fact I think it's important to have a word for "everything" because it
avoids fringe arguments about "does this count..." "My documentation is in
my code and produced via javadoc" or "My programming language is the
graphical design." (The latter is relevant to us - In LabVIEW, the program
*is* the Visio-looking picture you draw, for example).
UN-altered REPRODUCTION and DISSEMINATION of
this IMPORTANT information is ENCOURAGED.
From: Anthony Shortland <ant...@controltier.com
Date: 05/14/2010 10:57 AM
Subject: Re: Good Source for Definitions
Sent by: devops-t...@googlegroups.com