22:
106:
202:
Engineering Change Order (ECO) by Loch and
Terwiesch (1999) and Pikosz and Malmqvist (1998). Engineering Change Order is a separate step after ECR. After ECR is approved by Engineering Department then an ECO is made for making the
121:
A change request is declarative, i.e. it states what needs to be accomplished, but leaves out how the change should be carried out. Important elements of a change request are an ID, the customer (ID), the
212:
Change
Request (CR) is, among others, used by Lam (1998), Mäkäräinen (2000), Dennis, et al. (2002), Crnkovic, Asklund and Persson-Dahlqvist (2003) and at ABB Automation Products AB (Kajko-Mattsson, 1999).
105:
43:
329:
Lam, W. (1998). Change
Analysis and Management in a Reuse-Oriented Software Development Setting. In Pernici, B. & Thanos, C. (Eds.)
361:
Pikosz, P. & Malmqvist, J. (1998). A comparative study of engineering change management in three
Swedish engineering companies.
65:
126:(if applicable), an indication whether the change is required or optional, the change type (often chosen from a domain-specific
336:
Loch, C.H. & Terwiesch, C. (1999). Accelerating the
Process of Engineering Change Orders: Capacity and Congestion Effects.
228:
388:
308:
Huang, G.H. & Mak, K.L. (1999). Current practices of engineering change management in UK manufacturing industries.
134:, which is a piece of narrative (Keller, 2005). An example of a change request can be found in Figure 1 on the right.
127:
36:
30:
162:
changes in underlying structure and or standards (e.g. in software development this could be a new operating system)
173:, change requests may also originate from an unclear understanding of the goals and the objectives of the project.
99:
47:
243:
393:
315:
Kajko-Mattsson, M. (1999). Maintenance at ABB (II): Change
Execution Processes (The State of Practice).
123:
368:
Rajlich, V. (1999). Software Change and
Evolution. In Pavelka, J., Tel, G. & Bartošek, M. (Eds.),
170:
131:
324:
Proceedings of the 2005 Seventh IEEE International
Conference on E-Commerce Technology Workshops
331:
Proceedings of the Tenth
International Conference on Advanced Information Systems Engineering
154:
301:. PhD dissertation. Eindhoven: Eindhoven University of Technology press. Available online:
285:
Implementing and
Integrating Product Data Management and Software Configuration Management
181:
Change requests have many different names, which essentially describe the same concept:
348:
322:
Keller, A. (2005). Automating the Change Management Process with Electronic Contracts.
233:
263:
382:
238:
147:
302:
345:
Software change management processes in the development of embedded software
185:
Request For Change (RFC) by Rajlich (1999); RFC is also a common term in
91:
190:
363:
Proceedings of the DETC98 ASME Design Engineering Technical Conference
95:
165:
demands from senior management (Dennis, Wixom & Tegarden, 2002).
375:
DiDonato, P. (2001). Oakley Inc, Developing XML systems with (CRF).
317:
Proceedings of the International Conference on Software Maintenance
292:
System Analysis & Design: An Object-Oriented Approach with UML
186:
347:. PhD dissertation. Espoo: VTT Publications. Available online:
310:
International Journal of Operations & Production Management
142:
Change requests typically originate from one of five sources:
15:
299:
Product Data Management as enabler for Concurrent Engineering
283:
Crnkovic I., Asklund, U. & Persson-Dahlqvist, A. (2003).
209:
Action Request (AR) at ABB Robotics AB (Kajko-Mattson, 1999);
356:
The Little Prince 2: A Practical Guide to Project Management
104:
199:
Engineering Change Request (ECR) at Aero (Helms, 2002);
150:
that must be fixed, which forms the most common source
349:
http://www.vtt.fi/inf/pdf/publications/2000/P416.pdf
358:, Pink Roccade Educational Services/Ten Hagen Stam.
290:Dennis, A., Wixom, B.H. & Tegarden, D. (2002).
370:SOFSEM'99, Lecture Notes in Computer Science 1725
294:. Hoboken, New York: John Wiley & Sons, Inc.
270:, November 15, 2009. Retrieved on March 2, 2010.
196:Engineering Change (EC) by Huang and Mak (1999);
303:http://alexandria.tue.nl/extra2/200211339.pdf
112:: Example change request for the car industry
8:
338:Journal of Product Innovation Management, 16
159:events in the development of other systems
94:containing a call for an adjustment of a
66:Learn how and when to remove this message
206:Change Notice at Chemical (Helms, 2002);
29:This article includes a list of general
255:
354:Onna, M. van & Koning, A. (2003).
7:
98:; it is of great importance in the
35:it lacks sufficient corresponding
14:
215:Operational Change Request (OCR).
153:system enhancement requests from
264:"How to Control Change Requests"
218:Enterprise Change Request (ECR).
20:
229:Change management (engineering)
146:problem reports that identify
1:
410:
193:(Onna & Koning, 2003).
100:change management process
244:Engineering Change Order
343:Mäkäräinen, M. (2000).
287:. London: Artech House.
50:more precise citations.
113:
84:change control request
108:
297:Helms, R.W. (2002).
117:Purpose and elements
389:Systems engineering
189:(Keller, 2005) and
82:, sometimes called
171:Project Management
114:
169:Additionally, in
76:
75:
68:
401:
271:
260:
71:
64:
60:
57:
51:
46:this article by
37:inline citations
24:
23:
16:
409:
408:
404:
403:
402:
400:
399:
398:
379:
378:
312:, 19(1), 21–37.
280:
278:Further reading
275:
274:
262:Nielsen, Dave.
261:
257:
252:
225:
179:
140:
130:) and a change
119:
72:
61:
55:
52:
42:Please help to
41:
25:
21:
12:
11:
5:
407:
405:
397:
396:
394:Business terms
391:
381:
380:
377:
376:
373:
366:
359:
352:
341:
334:
327:
320:
313:
306:
295:
288:
279:
276:
273:
272:
254:
253:
251:
248:
247:
246:
241:
236:
234:Change control
231:
224:
221:
220:
219:
216:
213:
210:
207:
204:
200:
197:
194:
178:
175:
167:
166:
163:
160:
157:
151:
139:
136:
118:
115:
80:change request
74:
73:
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
406:
395:
392:
390:
387:
386:
384:
374:
371:
367:
364:
360:
357:
353:
350:
346:
342:
340:(2), 145–159.
339:
335:
332:
328:
325:
321:
318:
314:
311:
307:
304:
300:
296:
293:
289:
286:
282:
281:
277:
269:
265:
259:
256:
249:
245:
242:
240:
237:
235:
232:
230:
227:
226:
222:
217:
214:
211:
208:
205:
201:
198:
195:
192:
188:
184:
183:
182:
176:
174:
172:
164:
161:
158:
156:
152:
149:
145:
144:
143:
137:
135:
133:
129:
125:
116:
111:
107:
103:
101:
97:
93:
89:
85:
81:
70:
67:
59:
49:
45:
39:
38:
32:
27:
18:
17:
369:
362:
355:
344:
337:
330:
323:
316:
309:
298:
291:
284:
267:
258:
239:Change order
180:
168:
141:
120:
109:
87:
83:
79:
77:
62:
56:October 2014
53:
34:
48:introducing
383:Categories
372:, 189–202.
333:, 219–236.
319:, 307–315.
250:References
31:references
326:, 99–108.
365:, 78–85.
223:See also
177:Synonyms
132:abstract
128:ontology
124:deadline
110:Figure 1
92:document
90:), is a
203:change;
191:PRINCE2
138:Sources
44:improve
268:PM Hut
96:system
33:, but
155:users
187:ITIL
148:bugs
88:CCR
385::
266:,
102:.
78:A
351:.
305:.
86:(
69:)
63:(
58:)
54:(
40:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
