Page modified: Friday, June 23, 2006 20:30:48
A change requirement designates a formalized desire for change of the characteristics of a certain product version in the change department of projects. Each change requirement is evaluated, decided during a controlled process and communicates.
A change requirement must possess the following characteristics:
- the description of the product property, which is to be changed
- the description of the new product property, which is to be converted
- the reason for the change
- the product version concerned
- the date of the expected conversion
- the date of the production of the change requirement
- the creator of the change requirement
Synonymous one
The following designations are in practice equivalently used:
- Request for modification, Abk.
- English CHANGE Request, Abk. CR
- English Request For CHANGE, Abk. RFC
Examples
Examples from the software development:
- Change requirements of technical kind: During the software development of a route planner it was investigated that a road is in a certain place traffic-technically a one-way street. This change is trained into the following software-Version.
- Change requirements of data processing-technical kind: A customer has the intention of changing the complete EDP over of its company from Windows 98 to Windows 2003. That is communicated to the software developers, that develop a straight data base system for this company. The developers must accomplish change requirements, which ensure that the data base system under Windows 2003 functions.
Articles in category "Change requirement"
We found here 3 articles.