Introduction

These classifications can be used to describe how to use work products (and reports) when tailoring the Development Process.  These values can be complemented with a separate classifier to define the review procedures for the work product. For more information on review levels for work products, see Guideline: Review Levels.

This classification scheme can be extended or customized to reflect your organization's individual culture.

An example of when this classification scheme may be adjusted depends on the level of tailoring that is being performed.  For example, when tailoring a process for a specific project, the decision of whether or not a specific work product is to be used is made as part of the tailoring effort. In such cases, the above classification scheme may be reduced to "Required" and "Not Required".  In other cases, say when you are tailoring a process for an organization and further tailoring for individual projects is expected, a more extensive classification scheme as described in the above table becomes important.  For more information on the different levels of tailoring, see Concept: Tailoring RUP.

Impact of Classification

All work products classified as Must have or Should have must have their review procedures, tools, templates and configuration management practices defined.  

The specification of these procedures is optional for work products classified as Could have-these decisions could be left to the developers or projects that decide to produce these work products.

All work products classified as Won't have must have their omission justified.

The major benefit of adopting this classification scheme is that it clearly denotes how the process has been customized, and where there are options for negotiation and local decision making.

Examples of Usage

One way to think about the work product classification scheme is that it sets constraints on how the work products are used.

For example, if you decide that the project could have an Analysis Model, then further customization could adjust these values by deciding that the project will meet one of the following criteria:

• It will have an Analysis Model
• It won't have an Analysis Model
• It will stay in its current state (an Analysis Model is optional)

The classification scheme can even be used dynamically-allowing the status of the work product to change depending upon which phase the project is in.

The following table shows different ways of treating the Analysis Model. The How to use column defines how the work product is used in each of the phases.