Change management (engineering)

The change request management process in systems engineering is the process of requesting, determining attainability, planning, implementing, and evaluating of changes to a system. Its main goals are to support the processing and traceability of changes to an interconnected set of factors.

Introduction

There is considerable overlap and confusion between change request management, change control and configuration management. The definition below does not yet integrate these areas.

Change request management has been embraced for its ability to deliver benefits by improving the affected system and thereby satisfying "customer needs," but has also been criticized for its potential to confuse and needlessly complicate change administration. In some cases, notably in the Information Technology domain, more funds and work are put into system maintenance (and change request management) than into the initial creation of a system. Typical investment by organizations during initial implementation of large ERP systems is 15 to 20 percent of overall budget.

In the same vein, Hinley describes two of Lehman's laws of software evolution:
* The law of continuing change: Systems that are used must change, or else automatically become less useful.
* The law of increasing complexity: Through changes, the structure of a system becomes ever more complex, and more resources are required to simplify it.

Change request management is also of great importance in the field of manufacturing, which is confronted with many changes due to increasing and worldwide competition, technological advances and demanding customers. Because many systems tend to change and evolve as they are used, the problems of these industries are experienced to some degree in many others.

Notes: In the process below, it is arguable that the change committee should be responsible not only for accept/reject decisions, but also prioritization, which influences how change requests are batched for processing.

The process and its deliverables

For the description of the change request management process, the meta-modeling technique is used. Figure 1 depicts the process-data diagram, which is explained in this section.

Activities

There are six main activities, which jointly form the change request management process. They are: Identify potential change, Analyze change request, Evaluate change, Plan change, Implement change and Review and close change. These activities are executed by four different roles, which are discussed in Table 1. The activities (or their sub-activities, if applicable) themselves are described in Table 2.

Deliverables

Besides activities, the process-data diagram (Figure 1) also shows the deliverables of each activity, i.e. the data. These deliverables or concepts are described in Table 3; in this context, the most important concepts are: CHANGE REQUEST and CHANGE LOG ENTRY.

A few concepts are defined by the author (i.e. lack a reference), because either no (good) definitions could be found, or they are the obvious result of an activity. These concepts are marked with an asterisk (‘*’). Properties of concepts have been left out of the model, because most of them are trivial and the diagram could otherwise quickly become too complex. Furthermore, some concepts (e.g. CHANGE REQUEST, SYSTEM RELEASE) lend themselves for the versioning approach as proposed by Weerd, but this has also been left out due to diagram complexity constraints.

Besides just ‘changes’, one can also distinguish deviations and waivers.Scott & Nisse, 2001. A deviation is an authorization (or a request for it) to depart from a requirement of an item, prior to the creation of it. A waiver is essentially the same, but than during or after creation of the item. These two approaches can be viewed as minimalistic change request management (i.e. no real solution to the problem at hand).

Examples

A good example of the change request management process in action can be found in software development. Often users report bugs or desire new functionality from their software programs, which leads to a change request. The product software company then looks into the technical and economical feasibility of implementing this change and consequently it decides whether the change will actually be realized. If that indeed is the case, the change has to be planned, for example through the usage of function points. The actual execution of the change leads to the creation and/or alteration of software code and when this change is propagated it probably causes other code fragments to change as well. After the initial test results seem satisfactory, the documentation can be brought up to date and be released, together with the software. Finally, the project manager verifies the change and closes this entry in the change log.

Another typical area for change request management in the way it is treated here, is the manufacturing domain. Take for instance the design and production of a car. If for example the vehicle’s air bags are found to automatically fill with air after driving long distances, this will without a doubt lead to customer complaints (or hopefully problem reports during the testing phase). In turn, these produce a change request (see Figure 2 on the right), which will probably justify a change. Nevertheless, a – most likely simplistic – cost and benefit analysis has to be done, after which the change request can be approved. Following an analysis of the impact on the car design and production schedules, the planning for the implementation of the change can be created. According to this planning, the change can actually be realized, after which the new version of the car is hopefully thoroughly tested before it is released to the public.

In industrial plants

Since complex processes can be very sensitive to even small changes, proper management of change to industrial facilities and processes is recognized as critical to safety. In the US, OSHA has regulations that govern how changes are to be made and documented. The main requirement is that a thorough review of a proposed change be performed by a multi-disciplinary team to ensure that as many possible viewpoints are used to minimize the chances of missing a hazard. In this context, change request management is known as Management of Change, or MOC. It is just one of many components of Process Safety Management, section 1910.119(l).1

See also

* Change control
* Change request management
* Engineering Change Order, Change request
* PRINCE2
* ITIL
* Versioning
* Release management
* Software release life cycle
* Application lifecycle management
*Systems engineering
* Issue tracking system

References

Further reading

* Crnković I., Asklund, U. & Persson-Dahlqvist, A. (2003). ''Implementing and Integrating Product Data Management and Software Configuration Management''. London: Artech House.
* Dennis, A., Wixom, B.H. & Tegarden, D. (2002). ''System Analysis & Design: An Object-Oriented Approach with UML''. Hoboken, New York: John Wiley & Sons, Inc.
* Georgetown University (n.d.). ''Data Warehouse: Glossary''. Retrieved April 13, 2006 from: https://web.archive.org/web/20060423164505/http://uis.georgetown.edu/departments/eets/dw/GLOSSARY0816.html.
* Hinley, D.S. (1996). Software evolution management: a process-oriented perspective. ''Information and Software Technology, 38'', 723-730.
* Huang, G.H. & Mak, K.L. (1999). Current practices of engineering change management in UK manufacturing industries. ''International Journal of Operations & Production Management, 19''(1), 21-37.
* IEEE (1991). ''Standard Glossary of Software Engineering Terminology (ANSI)''. The Institute of Electrical and Electronics Engineers Inc. Retrieved April 13, 2006 from: http://www.ee.oulu.fi/research/ouspg/sage/glossary/#reference_6 .
* 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.
* NASA (2005). ''NASA IV&V Facility Metrics Data Program - Glossary and Definitions''. Retrieved March 4, 2006 from: https://web.archive.org/web/20060307232014/http://mdp.ivv.nasa.gov/mdp_glossary.html.
* Pennsylvania State University Libraries (2004). ''CCL Manual: Glossary of Terms and Acronyms''. Retrieved April 13, 2006 from: https://web.archive.org/web/20060615021317/http://www.libraries.psu.edu/tas/ cataloging/ccl/glossary.htm.
* Princeton University (2003). ''WordNet 2.0''. Retrieved April 13, 2006 from: http://dictionary.reference.com/search?q=release.
* 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.
* Rigby, K. (2003). ''Managing Standards: Glossary of Terms''. Retrieved April 1, 2006 from: https://web.archive.org/web/20060412081603/http://sparc.airtime.co.uk/users/wysywig/gloss.htm.
* Scott, J.A. & Nisse, D. (2001). Software Configuration Management, ''Guide to Software Engineering Body of Knowledge'', Chapter 7, IEEE Computer Society Press.
* Vogl, G. (2004). ''Management Information Systems: Glossary of Terms''. Retrieved April 13, 2006 from Uganda Martyrs University website: https://web.archive.org/web/20060411160145/http://www.321site.com/greg/courses/mis1/glossary.htm.
* Weerd, I. van de (2006). ''Meta-modeling Technique: Draft for the course Method Engineering 05/06''. Retrieved March 1, 2006 from: https://bscw.cs.uu.nl/bscw/bscw.cgi/d1009019/Instructions for the process-data diagram.pdf estricted access

{{DEFAULTSORT:Change Management (Engineering)
Change management
Systems engineering