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 Software Requirements Specification
- 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 (See: Software Development Templates). 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.
Most artifacts are also linked to a specific template and case study so you can have
a better view on how to use and understand the artifact itself. See Software Development Templates
for more detail regarding the templates.
To make the development of a complete software system
manageable, the artifacts are organized into sets corresponding to the disciplines. .
These kinds of artifacts belong to the artifact set where they are
primarily produced. |
Artifact Sets
- Requirements
- Analysis and Design
- Implementation
- Test
- Conf./Change Management
- Project Management
|
Artifacts
