Change request

from Wikipedia, the free encyclopedia

A change request (also abbreviated CR or Request for Change abbreviated RfC ) describes in the change management of projects a formalized request to change the properties of a certain product feature . Every change request should be evaluated, decided and communicated in a controlled process.

features

A change request should include the following details:

  • the description of the product property that is to be changed (specifically the status quo )
  • the description of the product property that is to be produced
  • the reason for the change (motivation)
  • the affected product version
  • the date of the desired implementation
  • the date the change request was created
  • the name of the creator of the change request
  • a cost estimate of the change (if necessary, separated into internal and external costs, license costs , personnel costs , etc.)
  • an estimated time required for the required change (possibly separated by conception, development, test, etc.)

A change request can only be approved jointly in existing contractual relationships between the client and the contractor. In this case, it becomes part of the contract.

Synonyms

The following terms are used synonymously in practice:

  • Amendment , abbr
  • engl. Change Request , abbr.CR
  • engl. Request For Change , abbr. RFC; RFC is in ITIL and PRINCE2 used
  • Change Notice
  • Action Request (AR)

Depending on the type of change, different requirements can be distinguished that essentially describe the same concept:

  • Engineering Change (EC)
  • engl. Engineering Change Request (ECR), technical change request
  • Program or process or product change request (PCR)

Engineering Change Order (ECO) is a separate step after the ECR. Once an ECR has been approved, an ECO is created to implement the change.

Examples

Examples from software development , where ticket systems are often used to manage change requests:

  • Change requests of a technical nature: When testing a toll system, it is found that the odometer is running backwards if the vehicle is driving on the opposite lane due to a construction site. The customer therefore sends a change request to the developer.
  • Change requirements of information processing technology: A customer intends to convert the entire IT system of his company from Windows XP to Windows 7 . This is communicated to the software developers who are currently developing an application for this company . The developers need to make changes that will make the application work on Windows 7.

further reading

  • Loch, CH & Terwiesch, C. (1999). Accelerating the Process of Engineering Change Orders: Capacity and Congestion Effects. Journal of Product Innovation Management, 16 (2), 145-159.
  • Pikosz, P. & Malmqvist, J. (1998). A comparative study of engineering change management in three Swedish engineering companies. Proceedings of the DETC98 ASME Design Engineering Technical Conference , 78-85.
  • DiDonato, P. (2001). Oakley Inc, Developing XML systems with (CRF).

See also

Individual evidence

  1. ↑ Lam, W. (1998). Change Analysis and Management in a Reuse-Oriented Software Development Setting. In Pernici, B. & Thanos, C. (Eds.) Proceedings of the Tenth International Conference on Advanced Information Systems Engineering , 219-236.
  2. ↑ Mäkäräinen, M. (2000). Software change management processes in the development of embedded software . PhD dissertation. Espoo: VTT Publications. Available online: http://www.vtt.fi/inf/pdf/publications/2000/P416.pdf .
  3. ↑ Dennis, A., Wixom, BH & Tegarden, D. (2002). System Analysis & Design: An Object-Oriented Approach with UML . Hoboken, New York: John Wiley & Sons, Inc.
  4. ↑ Crnkovic I., Asklund, U. & Persson-Dahlqvist, A. (2003). Implementing and Integrating Product Data Management and Software Configuration Management . London: Artech House.
  5. ↑ a b Kajko-Mattsson, M. (1999). Maintenance at ABB (II): Change Execution Processes (The State of Practice). Proceedings of the International Conference on Software Maintenance , 307-315.
  6. ^ Rajlich, V. (1999). Software change and evolution. In Pavelka, J., Tel, G. & Bartošek, M. (Eds.), SOFSEM'99, Lecture Notes in Computer Science 1725 , 189–202.
  7. ^ Keller, A. (2005). Automating the Change Management Process with Electronic Contracts. Proceedings of the 2005 Seventh IEEE International Conference on E-Commerce Technology Workshops , 99-108.
  8. ↑ Onna, M. van & Koning, A. (2003). The Little Prince 2: A Practical Guide to Project Management , Pink Roccade Educational Services / Ten Hagen Stam
  9. ↑ a b Helms, RW (2002). Product data management as enabler for concurrent engineering . PhD dissertation. Eindhoven: Eindhoven University of Technology press. Available online: http://alexandria.tue.nl/extra2/200211339.pdf .
  10. ↑ Huang, GH & Mak, KL (1999). Current practices of engineering change management in UK manufacturing industries. International Journal of Operations & Production Management , 19 (1), 21–37.
  11. ^ Loch, CH & Terwiesch, C. (1999). Accelerating the Process of Engineering Change Orders: Capacity and Congestion Effects . Journal of Product Innovation Management, 16 (2), 145-159.
  12. ↑ Pikosz, P. & Malmqvist, J. (1998). A comparative study of engineering change management in three Swedish engineering companies . Proceedings of the DETC98 ASME Design Engineering Technical Conference, 78-85.