Engineering Change Notification Form

No: 

Submitted by:

Date Submitted:

Product: 

Version:

Type of Change Notification (check one):

Critical Error (software is brought down, machine locked up, data integrity)

Error (problem with logic, presentation of information, function not working at all)

Usability/Interface Error (function does not meet principles of good GUI design)

Logic Changes (product functions as designed, but design should change)

Enhancements (new feature or change to feature that would be 'nice to have')

Methodology Change (change to the actual RADPath methodology text)

Documentation Change (change to the actual product documentation or on-line help)

Description of Change Notification:

It is crucial that the problem be described as thoroughly as possible. Describe the function entered, the field or widget acted upon, the message received, the change to data, etc. Also state whether the problem could be reproduced.

Status (to be completed by Administrator):

Accepted (change will be made, is targeted for next version)

Completed (change is made, will be included in next version)

Deferred (change will be made, is not targeted for next version)

In Process (change is currently being made)

Rejected  (change does not match the direction of the product)