This is the English version rather than the American version, but does contain a nuance that the American version does not. When the word was originally used, as he says by the three amigos, I believe it was the word artefact rather than artifact. You'll likely want to use more specific terminology at the coal face of software development! "Please could you write an artifact for our next test case" you'll get blank stares if you use terminology such as: Nowadays, the word artifact might be regarded in the same light as pretentious management speak, and the term is usually too vague and generic to be used frequently by the actual software development team, e.g. a claim form, an EDI document, or a report output. The term artifact also crops up in business process modelling, usually referring to a physical or electronic document produced by a process, e.g. Code artifacts, including source files, binary outputs, and test or support code.Īrtifacts could be brought into Software Configuration Management (identified, versioned, change could be managed, etc).A Model generated during design, usually one of the UML available diagrams, e.g.Documents, such as Project Plan, Requirements Document, Specifications etc.The word Artifact in RUP software engineering was a generic term to refer to any 'deliverable' which could be produced by any 'role' in the software development lifecycle, including: The term artifact (or artefact) seems to have been popularized around the time that Booch, Rumbaugh and Jacobsen (the 3 amigos) described the Rational Unified Process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |