Artifacts

Rational Unified Process: Artifacts

Artifacts are either final or intermediate work products that are produced and used during a project. Artifacts are used to capture and convey project information. An artifact can be any of the following:
  • A document, such as Business Case or Software Architecture Document
  • A model, such as the Use-Case Model or the Design Model
  • A model element; that is, an element within a model, such as a class, or a subsystem

Models and model elements, have reports associated with them. A report extracts information about models and model elements from a tool. A report presents an artifact or a set of artifacts. Most artifacts have guidelines, which describes the artifact in more detail.

To make the development of a complete software system manageable, the artifacts are organized into sets corresponding to the disciplines. Several artifacts are used in a number of disciplines; for example, the Risk List, the Software Architecture Document, and the Iteration Plan. These kinds of artifacts belong to the artifact set where they are primarily produced. 

Artifact Sets

Major artifacts of the Rational Unified Process, and the information flow between them

Copyright  1987 - 2001 Rational Software Corporation


Display Rational Unified Process using frames

Rational Unified Process