Change reasons

Collection Explorer ◢ Changes group ◢ Change Reasons collection

Purpose §

Classifies the rationale for making a change, so that managers can assess design and development procedures.

A Change Reason tells why you need to make a change. A Problem Source tells how an issue was discovered.

Where used §

Change form

Data fields §

Name §

This is the complete name for the change reason.

Description §

This gives the change reason in more detail.

Reason code §

Specifies the required change reason database code for EIA-649 environments. In other environments, this field may be ignored or used for another purpose.

Active: users can select
Default member of collection
Permanent member of collection §

See the Managing collections: Common attributes help topic.

Setup §

This collection may need to reflect aerospace/military contractor or regulatory requirements.

Without crisp definitions and clear categories, this collection can become confusingly similar to the Problem Sources collection. Ensure that your users can easily distinguish between a problem source and its change reason, or simply use only one of these collections.

This collection can grow large and unwieldy. Try to limit the number of members to get "big picture" trends that can help your product management procedure. It's easier to spot trends using several broad categories, rather than offering users many detailed reasons with only a few instances of each.

2011