Artifact: Product

	The packaging of a product for market appeal distinguishes it from a deployment unit. A product can contain multiple deployment units, and may be accessible as a downloadable commodity, in shrink wrap or on any digital storage media formats.
Other Relationships:	Contains Product Artwork Installation Artifacts Deployment Unit Bill of Materials
Role:	Deployment Manager
Optionality/Occurrence:	Required.
Templates and Reports:
Examples:
UML Representation:	Package, stereotyped as a <<product>>.
More Information:

Purpose
Timing
Responsibility
Tailoring

Input to Activities:

Verify Manufactured Product

Output from Activities:

Purpose

The Product is the purpose! The entire project effort is geared to creating a product that provides benefit to the user community. The success of a product lies in its use.

Timing

The Product is defined as a Deployment Unit that has been packaged for sale and distribution. As there is a manufacturing cost associated with mass producing a product, the Deployment Unit will typically be released to manufacturing in the late Transition iterations. By that time the software has under gone internal and beta testing, and is sufficiently mature for mass production.

Responsibility

As with quality, the product is everyone's responsibility, however, it is the Deployment Manager who has to ensure that the product conforms to the Bill of Materials, and is adequately inspected for completeness prior to shipment to the customer.