244:(EA) Program explicitly considers the information needs of the Enterprise Performance Life Cycle (EPLC) processes in developing and enhancing the EA Framework, collecting and populating data in the EA Repository, and developing views, reports, and analytical tools that can be used to facilitate the execution of the EPLC processes. The EPLC conceptual diagram in the figure provides a Departmental perspective of key business functions. The EPLC is also relevant from an individual investment or project perspective, as each new investment passes through each phase of the EPLC. The investment-level perspective is detailed in the Enterprise Performance Life Cycle Framework.
221:
193:
143:
164:
31:
179:
is used to drive the requirements that are evaluated against the
Systems View. Operational deficiencies are derived from the analysis, and viable candidates are identified. These candidates can take the form of either materiel or non- materiel solutions and are modeled back into the Operational and
183:
The architecture is re-analyzed, and the process continues until the operational deficiencies are minimized. The final sets of viable candidates are assessed for operational viability. Based on the results of the assessments, design changes are made and submitted for inclusion into the budgeting
154:
The architecture team also generates a sequencing plan for the transition of systems, applications, and associated business practices predicated upon a detailed gap analysis. The architecture is employed in the CPIC and the enterprise engineering and program management processes via prioritized,
211:
The figure on the right depicts notional activities of an enterprise life cycle methodology. Within the context of this document, Enterprise Life Cycle does not refer to a specific methodology or a specific bureau's approach. Each organization needs to follow a documented
Enterprise Life Cycle
150:
As a prerequisite to the development of every enterprise architecture, each Agency should establish the need to develop an EA and formulate a strategy that includes the definition of a vision, objectives, and principles. The figure shows a representation of the EA process. Executive buy-in and
203:
An enterprise life cycle integrates the management, business, and engineering life cycle processes that span the enterprise to align its business and IT activities. Enterprise life cycle refers generally to an organization's approach for managing activities and making decisions during ongoing
204:
refreshment of business and technical practices to support its enterprise mission. These activities include investment management, project definition, configuration management, accountability, and guidance for systems development according to a system development life cycle (SDLC).
155:
incremental projects and the insertion of emerging new technologies. Lastly, the architectures are maintained through a continuous modification to reflect the Agency's current baseline and target business practices, organizational goals, visions, technology, and infrastructure.
207:
The enterprise life cycle applies to enterprise-wide planning activities and decision making. By contrast, a System
Development Life Cycle generally refers to practices for building individual systems. Determining what systems to build is an enterprise-level decision.
151:
support should be established and an architectural team created within the organization. The team defines an approach and process tailored to Agency needs. The architecture team implements the process to build both the baseline and target EAs.
108:
The concept of enterprise life cycle aids in the implementation of enterprise architecture, and the capital planning and investment control (CPIC) process that selects, controls, and evaluates investments. Overlying these processes are
174:
The figure depicts the life of the architecture as it evolves and shows the process that the architecture description supports in the development, analysis, and evolution of the implemented architecture. In this illustration, the
236:
in the center of the EPLC conceptual diagram, shown in the figure, reflects the supporting and enabling role that enterprise architecture serves for the major business functions in the
Enterprise Performance Life Cycle.
232:(CIO), and in particular, shows at a high level the relationship among the different business functions and both the general order and the iterative nature of their execution. The placement of
125:, systems migrate efficiently from legacy technology environments through evolutionary and incremental developments, and the Agency is able to demonstrate its
408:
541:
259:
114:
289:
98:
338:
129:(ROI). The figure on top illustrates the interaction of the dynamic and interactive cycles as they would occur over time.
284:
274:
435:
228:
The
Enterprise Performance Life Cycle (EPLC) encompasses the major business functions executed under the Office of the
184:
process. This process of developing, analyzing, and modifying continues throughout the architecture’s life cycle.
279:
269:
229:
525:
110:
97:. The Enterprise Architecture process is closely related to similar processes, as program management cycle or
241:
233:
224:
Illustration of the
Enterprise Performance Life Cycle of the U.S. Department of Health & Human Services.
86:
46:
304:
118:
90:
457:
294:
220:
502:
126:
66:
405:
192:
264:
212:
methodology appropriate to its size, the complexity of its enterprise, and the scope of its needs.
142:
94:
102:
254:
163:
176:
58:
50:
439:
412:
342:
299:
122:
121:
as a strategic resource and business process enabler. When these processes are properly
117:. When these processes work together effectively, the enterprise can effectively manage
30:
535:
519:
353:
17:
479:
335:
357:
70:
526:
EA in the
Federal Enterprise Life Cycle EA in the Federal Enterprise Life Cycle
62:
432:
74:
54:
431:
US Department of the
Treasury Chief Information Officer Council (2000).
497:
Handbook of Life Cycle
Engineering: Concepts, Models, and Technologies
360:, and Martin Zelm]. "CIMOSA: enterprise engineering and integration."
191:
167:
141:
507:
Enterprise
Modeling and Integration: Principles and Applications
388:
Methods and Tools for Effective Knowledge Life-Cycle-Management.
375:
Design of Enterprise Systems: Theory, Architecture, and Methods.
196:
474:
Methods and Tools for Effective Knowledge Life-Cycle-Management
495:
Arturo Molina, Jose Manuel Sanchez, Andrew Kusiak (1998).
456:
U.S. Department of Health & Human Services (2007).
336:
A Practical Guide to Federal Enterprise Architecture
101:, and has similar properties to those found in the
458:HHS Enterprise Architecture Governance Plan FY2007
404:DoD Architecture Framework Working Group (2003).
400:
398:
396:
406:DoD Architecture Framework Version 1.0 Deskbook
85:The enterprise life cycle is a key concept in
8:
27:Process of changing an enterprise over time
472:Alain Bernard, Serge Tichkiewitch (2008).
433:Treasury Enterprise Architecture Framework
427:
425:
423:
421:
386:Alain Bernard, Serge Tichkiewitch (2008).
334:Chief Information Officer Council (2001).
34:Illustration of the Enterprise Life Cycle.
330:
328:
326:
324:
322:
320:
219:
162:
77:of existing elements of the enterprise.
29:
482:, Laszlo Nemes, GĂĽnter Schmidt (2003).
452:
450:
448:
316:
7:
280:Service-oriented modeling life cycle
484:Handbook on Enterprise Architecture
180:Systems Views of the architecture.
65:, and new capabilities, as well as
25:
216:Enterprise Performance Life Cycle
520:Enterprise Life Cycle Management
260:Enterprise architecture planning
199:Enterprise Life Cycle activities
188:Enterprise life cycle activities
146:Enterprise Architecture Process.
138:Enterprise architecture process
115:information security management
57:over time by incorporating new
290:Systems development life cycle
99:systems development life cycle
1:
491:System requirements analysis
285:Software lifecycle processes
275:Product lifecycle management
133:Enterprise life cycle topics
373:Ronald E. Giachetti (2011)
558:
49:is the dynamic, iterative
489:Jeffrey O. Grady (2006).
270:Organizational life cycle
230:Chief Information Officer
170:Architecture Life Cycle.
111:human capital management
542:Enterprise architecture
442:. Version 1, July 2000.
242:Enterprise Architecture
234:enterprise architecture
159:Architecture life cycle
87:enterprise architecture
47:enterprise architecture
305:Enterprise integration
225:
200:
171:
147:
119:information technology
91:enterprise engineering
35:
362:Computers in industry
295:Technology life cycle
223:
195:
166:
145:
39:Enterprise life cycle
33:
18:Enterprise Life Cycle
127:return on investment
364:40.2 (1999): 83-97.
265:Enterprise modeling
95:systems engineering
528:presentation 2006.
438:2009-03-18 at the
411:2007-09-27 at the
341:2010-01-07 at the
226:
201:
172:
148:
103:product life cycle
59:business processes
36:
522:presentation 2005
503:François Vernadat
255:Business analysis
16:(Redirected from
549:
461:
454:
443:
429:
416:
402:
391:
384:
378:
371:
365:
351:
345:
332:
177:Operational View
53:of changing the
21:
557:
556:
552:
551:
550:
548:
547:
546:
532:
531:
516:
469:
467:Further reading
464:
455:
446:
440:Wayback Machine
430:
419:
415:15 August 2003.
413:Wayback Machine
403:
394:
385:
381:
372:
368:
352:
348:
343:Wayback Machine
333:
318:
314:
309:
300:Whole-life cost
250:
218:
190:
161:
140:
135:
83:
28:
23:
22:
15:
12:
11:
5:
555:
553:
545:
544:
534:
533:
530:
529:
523:
515:
514:External links
512:
511:
510:
500:
493:
487:
477:
468:
465:
463:
462:
444:
417:
392:
379:
366:
346:
315:
313:
310:
308:
307:
302:
297:
292:
287:
282:
277:
272:
267:
262:
257:
251:
249:
246:
217:
214:
189:
186:
160:
157:
139:
136:
134:
131:
82:
79:
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
554:
543:
540:
539:
537:
527:
524:
521:
518:
517:
513:
508:
504:
501:
498:
494:
492:
488:
485:
481:
478:
475:
471:
470:
466:
459:
453:
451:
449:
445:
441:
437:
434:
428:
426:
424:
422:
418:
414:
410:
407:
401:
399:
397:
393:
389:
383:
380:
376:
370:
367:
363:
359:
355:
354:Kosanke, Kurt
350:
347:
344:
340:
337:
331:
329:
327:
325:
323:
321:
317:
311:
306:
303:
301:
298:
296:
293:
291:
288:
286:
283:
281:
278:
276:
273:
271:
268:
266:
263:
261:
258:
256:
253:
252:
247:
245:
243:
238:
235:
231:
222:
215:
213:
209:
205:
198:
194:
187:
185:
181:
178:
169:
165:
158:
156:
152:
144:
137:
132:
130:
128:
124:
120:
116:
112:
106:
104:
100:
96:
92:
88:
80:
78:
76:
72:
68:
64:
60:
56:
52:
48:
44:
40:
32:
19:
506:
496:
490:
483:
480:Peter Bernus
473:
387:
382:
374:
369:
361:
349:
239:
227:
210:
206:
202:
182:
173:
153:
149:
123:synchronized
107:
84:
42:
38:
37:
358:F. Vernadat
71:disposition
67:maintenance
312:References
63:technology
55:enterprise
536:Category
505:(1996).
436:Archived
409:Archived
339:Archived
248:See also
81:Overview
75:disposal
51:process
390:p. 403
89:(EA),
61:, new
168:DoDAF
45:) in
377:p. 7
240:The
197:TEAF
113:and
93:and
73:and
43:ELC
538::
447:^
420:^
395:^
356:,
319:^
105:.
69:,
509:.
499:.
486:.
476:.
460:.
41:(
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
