276:
the purpose of EA is to create a greater coherency between the various concerns of an enterprise (HR, IT, Operations, etc.), including the link between strategy formulation and execution. Architecture proposals and decisions here encompass all aspects of the enterprise. The
Enterprise Ecosystem Adaption school states that the purpose of EA is to foster and maintain the learning capabilities of enterprises so they may be sustainable. Consequently, a great deal of emphasis is put on improving the capabilities of the enterprise to improve itself, to innovate, and to coevolve with its environment. Typically, proposals and decisions encompass both the enterprise and its environment.
99:
architects focus on solutions for and the impact on the whole organization. Enterprise architects oversee many solution architects and business functions. As practitioners of EA, enterprise architects support an organization's strategic vision by acting to align people, process, and technology decisions with actionable goals and objectives that result in quantifiable improvements toward achieving that vision. The practice of EA "analyzes areas of common activity within or between organizations, where information and other resources are exchanged to guide future states from an integrated viewpoint of strategy, business, and technology."
542:
2169:
530:
2159:
518:
158:, strategy, and the governance framework define all roles, responsibilities, and relationships involved in the anticipated transformation. Changes considered by enterprise architects typically include innovations in the structure or processes of an organization; innovations in the use of information systems or technologies; the integration and/or
119:, or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers. In that sense, the term enterprise covers various types of organizations, regardless of their size, ownership model, operational model, or geographical distribution. It includes those organizations' complete
95:'s EA best practice guidance states that an EA typically "takes the form of a comprehensive set of cohesive models that describe the structure and functions of an enterprise. The individual models in an EA are arranged in a logical manner that provides an ever-increasing level of detail about the enterprise."
275:
capabilities to meet the desired organizational objectives, often by greater alignment between IT/IS and business concerns. Architecture proposals and decisions are limited to the IT/IS aspects of the enterprise and other aspects service only as inputs. The
Enterprise Integrating school believes that
333:
from system failures and security breaches. EA also helps reduce risks of project delivery. Establishing EA as an accepted, recognized, functionally integrated and fully involved concept at operational and tactical levels is one of the biggest challenges facing
Enterprise Architects today and one of
242:
The main difference between these two definitions is that
Zachman's concept was the creation of individual information systems optimized for business, while NIST's described the management of all information systems within a business unit. The definitions in both publications, however, agreed that
98:
Important players within EA include enterprise architects and solutions architects. Enterprise architects are at the top level of the architect hierarchy, meaning they have more responsibilities than solutions architects. While solutions architects focus on their own relevant solutions, enterprise
86:
As a discipline, EA "proactively and holistically lead enterprise responses to disruptive forces by identifying and analyzing the execution of change" towards organizational goals. EA gives business and IT leaders recommendations for policy adjustments and provides best strategies to support and
263:
Within the field of enterprise architecture, there are three overarching schools: Enterprise IT Design, Enterprise
Integrating, and Enterprise Ecosystem Adaption. Which school one subscribes to will impact how they see the EA's purpose and scope, as well as the means of achieving it, the skills
1177:
Engelsman, W.; Iacob, M.E.; Franken, H.M.; Jonkers, J. (2009). "Architecture-driven requirements engineering". Advances in
Enterprise Engineering II (Report). Lecture Notes in Business Information Processing. Vol. 28. Honolulu, Hawaii, USA: Proceedings of the 2009 ACM Symposium on Applied
312:
and efficient resource allocation during system development and testing; enforcement of discipline and standardization of IT planning activities and contribution to a reduction in time for technology-related decision making; reduction of the system's implementation and operational costs, and
284:
The benefits of EA are achieved through its direct and indirect contributions to organizational goals. Notable benefits include support in the areas related to design and re-design of the organizational structures during mergers, acquisitions, or general organizational change; enforcement of
34:
analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and
243:
due to the "increasing size and complexity of the mplementations of nformation systems... logical construct (or architecture) for defining and controlling the interfaces and... ntegration of all the components of a system" is necessary. Zachman in particular urged for a "
433:
techniques provide a way to explore and analyze these hidden, tacit, or implicit areas. In return, EA provides a way of documenting the components of an organization and their interaction in a systemic and holistic way that complements knowledge management.
214:
is the top level and might be a total corporate entity or a sub-unit. It establishes for the whole organization necessary frameworks for "satisfying both internal information needs" as well as the needs of external entities, which include
130:
refers to fundamental concepts or properties of a system in its environment; and embodied in its elements, relationships, and in the principles of its design and evolution. A methodology for developing and using architecture to guide the
1367:
441:(SOA), a particular style of application integration. Research points to EA promoting the use of SOA as an enterprise-wide integration pattern. The broad reach of EA has resulted in this business role being included in the
1059:
Nilsson, Andreas (2008). Management of technochange in an interorganizational E-government project (Report). Proceedings of the 41st Annual Hawaii
International Conference on System Sciences. p. 209.
1225:
Pulkkinen, M.; Luostarinen, K.; Naumenko, A. (2007). "Managing information security in a business network of machinery maintenance services business - Enterprise architecture as a coordination tool".
227:. The lower levels of the EA that provide information to higher levels are more attentive to detail on behalf of their superiors. In addition to this structure, business unit architecture establishes
1371:
373:
According to the
Federation of Enterprise Architecture Professional Organizations (FEAPO), EA interacts with a wide array of other disciplines commonly found in business settings such as
1472:
1405:
1430:
641:
1252:
Obitz, T.; Babu, M.K. (2009). Enterprise architecture expands its role in strategic business transformation: Infosys enterprise architecture survey 2008/2009 (Report). Infosys.
957:
The
Contribution of Enterprise Architecture to the Achievement of Organizational Goals: Establishing the Enterprise Architecture Benefits Framework, Technical Report
313:
minimization of replicate infrastructure services across business units; reduction in IT complexity, consolidation of data and applications, and improvement of
1561:
1386:
510:
30:. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting
26:) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business
996:(2005). "Effects of an architectural approach to the implementation of shared service centers". In Fethi Rabhi; Daniel Veit; Christof Weinhardt (eds.).
39:
necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."
358:
1449:
482:
362:
341:
because of the broad-brush and often opaque nature of EA projects. Additionally, there have been a number of reports, including those written by
365:, that argue that the frequent failure of EA initiatives makes the concept not worth the effort and that the methodology will fade out quickly.
1645:
1580:
1263:
Dedic, N. (2020). "FEAMI: A Methodology to include and to integrate
Enterprise Architecture Processes into Existing Organizational Processes".
477:
210:(NIST) Special Publication on the challenges of information system integration. The NIST article describes EA as consisting of several levels.
207:
571:
546:
1476:
1412:
956:
702:
534:
1348:
1076:
498:
398:
648:
1434:
1519:
1111:
Ross, J.W.; Weill, P. (2005). Understanding the benefits of enterprise architecture (Report). Vol. V. CISR Research Briefings.
522:
472:
608:
386:
47:
1083:
1045:(2006). Enterprise architecture analysis and application: An exploratory study (Report). Hong Kong, China: EDOC Workshop TEAR.
2162:
2028:
1957:
1503:
1330:
1299:
1191:
123:, including people, information, processes, and technologies. Enterprise as a sociotechnical system defines the scope of EA.
1851:
1754:
962:(Report). Utrecht, The Netherlands: Department of Information and Computing Sciences at Utrecht University. Archived from
173:. In practice, an architectural description contains a variety of lists, tables, and diagrams. These are models known as
289:; support for investment decision-making and work prioritization; enhancement of collaboration and communication between
1606:
1638:
453:
are "two sides to the same coin." The Cutter Consortium described EA as an information and knowledge-based discipline.
87:
enable business development and change within the information systems the business depends on. EA provides a guide for
1831:
1698:
1683:
1042:
467:
462:
442:
267:
Under Enterprise IT Design, the main purpose of EA is to guide the process of planning and designing an enterprise's
140:
136:
2193:
1565:
1390:
732:
75:
143:, reference models, and guidance for the production and use of an enterprise-specific architecture description.
1987:
1914:
1904:
1749:
1678:
1124:"Application and project portfolio valuation using enterprise architecture and business requirements modelling"
2172:
2038:
1967:
1909:
1631:
438:
394:
135:
from a baseline state to a target state, sometimes through several transition states, is usually known as an
63:
998:
Financecom05: Second international workshop on Enterprise, applications and services in the finance industry
2203:
2198:
1977:
1836:
1703:
689:
Enterprise Architecture: Understanding the Bigger Picture – A Best Practice Guide for Decision Makers in IT
350:
1899:
1894:
1708:
2094:
1942:
1937:
1889:
1866:
1846:
792:"The theoretical basis of enterprise architecture: A critical review and taxonomy of relevant theories"
294:
1546:
2099:
2089:
1349:"Gartner Enterprise Architecture Summit: Architecting the Agile Organization, 26 – 27 September 2007"
285:
discipline and business process standardization, and enablement of process consolidation, reuse, and
92:
2002:
1801:
1784:
1693:
954:
414:
302:
43:
963:
1952:
710:
665:
604:
390:
374:
132:
51:
1352:
2007:
1764:
1759:
1020:
879:
426:
406:
378:
268:
31:
162:
of business processes; and improvement of the quality and timeliness of business information.
1826:
1779:
1496:
Information First - Integrating Knowledge and Information Architecture for Business Advantage
338:
326:
318:
211:
120:
179:. In the case of EA, these models describe the logical business functions or capabilities,
2124:
1962:
1821:
1811:
1723:
1668:
1654:
1387:"Fixing Enterprise Architecture: Balancing the Forces of Change in the Modern Organization"
1135:
989:
430:
236:
192:
1523:
8:
2144:
2129:
1997:
1861:
1769:
1713:
487:
429:. The EA of an organization is too complex and extensive to document in its entirety, so
410:
382:
290:
286:
272:
112:
67:
1139:
305:
and the accuracy of requirement definitions through publishing of the EA documentation.
2134:
1774:
1450:"Gartner urges more 'design thinking' to break enterprise architecture out of its silo"
1280:
1159:
937:
902:
857:
819:
244:
228:
198:
The first use of the term "enterprise architecture" is often incorrectly attributed to
1301:
Measuring Enterprise Architecture Effectiveness: A Focus on Key Performance Indicators
769:"ISO/IEC/IEEE 42010:2011: Systems and software engineering — Architecture description"
2048:
1806:
1499:
1284:
1187:
1151:
941:
823:
811:
642:"FEA Practice Guidance Federal Enterprise Architecture Program Management Office OMB"
623:
450:
224:
155:
36:
1163:
920:
Lapalme, J. (November 2012). "Three Schools of Thought on Enterprise Architecture".
906:
861:
78:'s reference guide aids federal agencies in the development of their architectures.
2119:
2063:
1841:
1733:
1728:
1547:
The Role of Service Oriented Architecture as an enabler for Enterprise Architecture
1272:
1234:
1179:
1143:
1016:
929:
894:
849:
803:
691:. Manchester, England, United Kingdom: The UK National Computing Centre. p. 9.
446:
422:
314:
180:
1334:
2139:
1992:
1972:
1856:
1718:
1147:
418:
159:
88:
1183:
2043:
1947:
1688:
1602:
1491:
1123:
1082:(Report). 23rd Enterprise Architecture Practitioners Conference. Archived from
955:
Vasilis Boucharas; Marlies van Steenbergen; Slinger Jansen; Sjaak Brinkkemper.
330:
322:
309:
1238:
2187:
2023:
1791:
1326:
1276:
1155:
840:
Zachman, John A. (1999). "A framework for information systems architecture".
815:
807:
402:
342:
166:
59:
2058:
2053:
1982:
791:
492:
329:, and increased transparency of infrastructure changes; and a reduction of
298:
199:
116:
71:
1211:
1021:
Trends in enterprise architecture 2005: How are organizations progressing?
933:
768:
151:
66:
also use EA to improve their business architectures as well as to improve
46:
is an example of an organization that practices EA, in this case with its
1581:"Digital workplace and enterprise architecture -- two sides to same coin"
1023:(Report). Institute For Enterprise Architecture Developments. p. 33.
1000:. Regensburg, Germany: Institute of Electrical and Electronics Engineers.
987:
622:
Austin, Robert D.; Ritchie, Warren; Garrett, Greggory (October 5, 2005).
264:
needed to conduct it, and the locus of responsibility for conducting it.
247:
169:, the product used to describe the architecture of a system is called an
139:. A framework provides a structured collection of processes, techniques,
1545:
Kistasamy, Christopher; van der Merwe, Alta; de la Harpe, Andre (2012).
898:
853:
541:
195:
and platform applications, hardware, and communications infrastructure.
2068:
2033:
1623:
736:
437:
In various venues, EA has been discussed as having a relationship with
354:
188:
175:
1520:"Service Oriented Architecture : SOA and Enterprise Architecture"
1210:
Kappelman, Leon; McGinnis, Tom; Pettite, Alex; Sidorova, Anna (2008).
1122:
Quartel, Dick; Steen, Maarten W.A.; Lankhorst, Marc M. (May 1, 2012).
1212:
Enterprise Architecture: Charting the Territory for Academic Research
993:
220:
216:
184:
1816:
771:. International Organization for Standardization. November 24, 2011
232:
1544:
529:
346:
1209:
1673:
752:
Design of Enterprise Systems, Theory, Architecture, and Methods
517:
183:, human roles and actors, the physical organization structure,
1607:"Dealing with Too Much Data from an Architectural Perspective"
880:"Information management directions: the integration challenge"
735:. International Institute of Business Analysis. Archived from
337:
A key concern about EA has been the difficulty in arriving at
1873:
1040:
55:
1224:
1176:
325:
IT as reflected through increased accessibility of data for
2084:
1549:(Report). Seattle, Washington, USA: AMCIS 2012 Proceedings.
27:
1560:
Rosa, Manuel; de Oliveira Sampaio, André (December 2013).
239:
that either enhance or stymie the organization's mission.
790:
Kotusev, Svyatoslav; Kurnia, Sherah (September 1, 2021).
1559:
1368:
Why Two Thirds of Enterprise Architecture Projects Fail
279:
1121:
297:
and to defining more complete and consistent project
621:
511:
United States Department of Defense definition of EA
368:
1431:"Design Thinking Reshapes EA For Dynamic Business"
877:
873:
871:
449:suggested that EA and the emerging concept of the
1411:(Report). Technology Matters, Inc. Archived from
499:Enterprise Architecture Service Life Cycle - SOMF
483:Architecture of Interoperable Information Systems
2185:
1562:"SOA Governance Through Enterprise Architecture"
1489:
647:. The White House. November 2007. Archived from
572:"Common Perspectives on Enterprise Architecture"
334:the main reasons why many EA initiatives fail.
206:. The first publication to use it was instead a
204:A framework for information systems architecture
868:
624:"Volkswagen of America: Managing IT Priorities"
1498:. Oxford, England, UK: Butterworth-Heinemann.
1473:"Who Owns Information Architecture? All Of Us"
1077:TOGAF 9 enterprise architecture survey results
1011:
1009:
1007:
478:Architecture of Integrated Information Systems
445:processes of many organizations. Analyst firm
1639:
1365:
1074:
878:Fong, E. N.; Goldfine, E.H. (December 1989).
789:
1205:
1203:
1106:
1104:
1102:
1100:
1098:
1096:
1384:
1004:
763:
761:
1646:
1632:
1447:
1428:
1054:
1052:
835:
833:
1251:
1200:
1110:
1093:
1075:Varnus, J.; Panaich, N. (July 20, 2009).
1070:
1068:
1066:
1041:Bucher, T.; Fischer, R.; Kurpjuweit, S.;
1036:
1034:
1032:
1030:
707:Enterprise Architecture Book of Knowledge
1837:Software development process/methodology
1653:
1601:
1325:
758:
749:
743:
473:Architectural pattern (computer science)
1385:Hinchcliffe, Dion (September 3, 2009).
1297:
1058:
1049:
1015:
919:
913:
839:
830:
566:
564:
308:Other benefits include contribution to
301:; and an increase in the timeliness of
48:Capital Planning and Investment Control
2186:
1307:(Master's thesis). Universiteit Leiden
1298:GĂĽnther, Wendy Arianne (August 2014).
1063:
1027:
754:. Boca Raton, Florida, USA: CRC Press.
686:
1627:
1578:
1470:
1403:
1262:
733:"Business Analysis Body of Knowledge"
495:, promoter of enterprise architecture
258:
2158:
1852:Software verification and validation
1755:Component-based software engineering
611:from the original on April 30, 2010.
579:Architecture and Governance Magazine
561:
280:Benefits, challenges, and criticisms
1429:Richardson, Clay (April 12, 2013).
848:(2/3) (reprint ed.): 454–470.
709:. Mitre Corporation. Archived from
13:
1471:Owens, Leslie (February 2, 2010).
1265:IEEE Engineering Management Review
150:the EA is the identification of a
14:
2215:
1832:Software configuration management
1699:Search-based software engineering
1684:Experimental software engineering
1214:(Report). AMCIS 2008 Proceedings.
796:Journal of Information Technology
504:
468:Enterprise architecture framework
463:Enterprise architecture artifacts
443:information technology governance
369:Relationship to other disciplines
137:enterprise architecture framework
2168:
2167:
2157:
1522:. The Open Group. Archived from
1448:McKendrick, Joe (May 19, 2010).
1366:Roeleven, S.; Broer, J. (2010).
540:
528:
516:
44:United States Federal Government
1595:
1572:
1553:
1538:
1512:
1483:
1464:
1441:
1422:
1397:
1378:
1359:
1351:. Gartner. 2007. Archived from
1341:
1319:
1291:
1256:
1245:
1227:Journal of Systems and Software
1218:
1170:
1115:
981:
948:
783:
395:enterprise portfolio management
208:National Institute of Standards
81:
76:Federal Enterprise Architecture
1679:Empirical software engineering
1579:Byrne, Tony (March 19, 2012).
1370:(Report). ARIS. Archived from
1128:Enterprise Information Systems
725:
695:
680:
666:"Enterprise Architecture (EA)"
658:
634:
615:
597:
293:and contribution to efficient
102:
91:towards these objectives. The
1:
1178:Computing. pp. 285–286.
555:
545:The dictionary definition of
439:Service Oriented Architecture
64:InterContinental Hotels Group
50:processes. Companies such as
16:Business function methodology
1704:Site reliability engineering
1148:10.1080/17517575.2011.625571
351:Erasmus University Rotterdam
133:transformation of a business
7:
1709:Social software engineering
1475:. Forrester. Archived from
1433:. Forrester. Archived from
1184:10.1007/978-3-642-01859-6_8
456:
253:
10:
2222:
1847:Software quality assurance
703:"Planning an EA – Purpose"
212:Business unit architecture
165:According to the standard
2153:
2112:
2077:
2016:
1930:
1923:
1882:
1742:
1661:
1406:Why Doesn't the FEA Work?
1239:10.1016/j.jss.2007.01.044
607:. The White House. 2010.
401:, IT strategic planning,
399:governance and compliance
217:cooperating organizations
171:architectural description
93:National Computing Centre
2003:Model-driven engineering
1802:Functional specification
1785:Software incompatibility
1694:Requirements engineering
1564:. Oracle. Archived from
1277:10.1109/EMR.2020.3031968
808:10.1177/0268396220977873
415:organization development
303:requirements elicitation
2194:Enterprise architecture
1797:Enterprise architecture
1404:Gaver, Stanley (2010).
750:Giachett, R.E. (2010).
628:Harvard Business Review
548:enterprise architecture
535:Enterprise architecture
523:Enterprise architecture
375:performance engineering
52:Independence Blue Cross
20:Enterprise architecture
2008:Round-trip engineering
1765:Backward compatibility
1760:Software compatibility
1389:. ebiz. Archived from
533:Quotations related to
427:user experience design
407:information management
310:optimal system designs
1827:Software architecture
1780:Forward compatibility
1605:(November 13, 2012).
1568:on December 19, 2013.
1393:on September 6, 2009.
1374:on November 13, 2013.
934:10.1109/MITP.2011.109
585:(4): 1. November 2013
327:regulatory compliance
317:of the systems; more
193:business applications
141:artifact descriptions
121:sociotechnical system
111:can be defined as an
2125:Computer engineering
1822:Software archaeology
1812:Programming paradigm
1724:Software maintenance
1669:Computer programming
1655:Software engineering
1479:on February 5, 2010.
1331:"EA Failed Big Way!"
1329:(October 18, 2007).
687:Jarvis, Bob (2003).
654:on October 16, 2010.
525:at Wikimedia Commons
431:knowledge management
291:project stakeholders
74:. Additionally, the
68:business performance
2204:Systems engineering
2199:Information science
2145:Systems engineering
2130:Information science
1910:Service orientation
1862:Structured analysis
1770:Compatibility layer
1714:Software deployment
1526:on January 10, 2015
1140:2012EntIS...6..189Q
899:10.1145/74120.74125
854:10.1147/sj.382.0454
842:IBM Systems Journal
488:Architecture domain
411:metadata management
383:process engineering
113:organizational unit
2135:Project management
1900:Object orientation
1867:Essential analysis
1775:Compatibility mode
1583:. Real Story Group
1490:Evernden, Elaine;
1437:on April 19, 2013.
1355:on August 6, 2007.
713:on October 1, 2013
339:metrics of success
259:Schools of thought
245:strategic planning
181:business processes
167:ISO/IEC/IEEE 42010
37:technology changes
2181:
2180:
2108:
2107:
2049:Information model
1953:Incremental model
1807:Modeling language
1505:978-0-7506-5858-4
1418:on June 11, 2016.
1337:on April 1, 2016.
1233:(10): 1607–1620.
1193:978-3-642-01858-9
1089:on July 20, 2009.
1017:Schekkerman, Jaap
990:Martin Op 't Land
739:on June 24, 2017.
521:Media related to
451:digital workplace
154:. Their mission,
2211:
2171:
2170:
2161:
2160:
2120:Computer science
1928:
1927:
1842:Software quality
1734:Systems analysis
1729:Software testing
1648:
1641:
1634:
1625:
1624:
1619:
1618:
1616:
1614:
1599:
1593:
1592:
1590:
1588:
1576:
1570:
1569:
1557:
1551:
1550:
1542:
1536:
1535:
1533:
1531:
1516:
1510:
1509:
1487:
1481:
1480:
1468:
1462:
1461:
1459:
1457:
1445:
1439:
1438:
1426:
1420:
1419:
1417:
1410:
1401:
1395:
1394:
1382:
1376:
1375:
1363:
1357:
1356:
1345:
1339:
1338:
1333:. Archived from
1323:
1317:
1316:
1314:
1312:
1306:
1295:
1289:
1288:
1260:
1254:
1253:
1249:
1243:
1242:
1222:
1216:
1215:
1207:
1198:
1197:
1174:
1168:
1167:
1119:
1113:
1112:
1108:
1091:
1090:
1088:
1081:
1072:
1061:
1060:
1056:
1047:
1046:
1038:
1025:
1024:
1013:
1002:
1001:
985:
979:
978:
976:
974:
968:
961:
952:
946:
945:
917:
911:
910:
884:
875:
866:
865:
837:
828:
827:
787:
781:
780:
778:
776:
765:
756:
755:
747:
741:
740:
729:
723:
722:
720:
718:
699:
693:
692:
684:
678:
677:
675:
673:
662:
656:
655:
653:
646:
638:
632:
631:
619:
613:
612:
601:
595:
594:
592:
590:
576:
568:
544:
532:
520:
447:Real Story Group
423:systems thinking
359:Dion Hinchcliffe
315:interoperability
225:federal agencies
2221:
2220:
2214:
2213:
2212:
2210:
2209:
2208:
2184:
2183:
2182:
2177:
2149:
2140:Risk management
2104:
2073:
2012:
1993:Waterfall model
1963:Prototype model
1958:Iterative model
1919:
1895:Aspect-oriented
1878:
1857:Software system
1738:
1719:Software design
1657:
1652:
1622:
1612:
1610:
1603:Evernden, Roger
1600:
1596:
1586:
1584:
1577:
1573:
1558:
1554:
1543:
1539:
1529:
1527:
1518:
1517:
1513:
1506:
1492:Evernden, Roger
1488:
1484:
1469:
1465:
1455:
1453:
1446:
1442:
1427:
1423:
1415:
1408:
1402:
1398:
1383:
1379:
1364:
1360:
1347:
1346:
1342:
1324:
1320:
1310:
1308:
1304:
1296:
1292:
1261:
1257:
1250:
1246:
1223:
1219:
1208:
1201:
1194:
1175:
1171:
1120:
1116:
1109:
1094:
1086:
1079:
1073:
1064:
1057:
1050:
1039:
1028:
1014:
1005:
986:
982:
972:
970:
969:on July 4, 2022
966:
959:
953:
949:
922:IT Professional
918:
914:
882:
876:
869:
838:
831:
788:
784:
774:
772:
767:
766:
759:
748:
744:
731:
730:
726:
716:
714:
701:
700:
696:
685:
681:
671:
669:
664:
663:
659:
651:
644:
640:
639:
635:
620:
616:
603:
602:
598:
588:
586:
574:
570:
569:
562:
558:
507:
459:
419:design thinking
371:
295:project scoping
282:
261:
256:
160:standardization
105:
89:decision making
84:
17:
12:
11:
5:
2219:
2218:
2207:
2206:
2201:
2196:
2179:
2178:
2176:
2175:
2165:
2154:
2151:
2150:
2148:
2147:
2142:
2137:
2132:
2127:
2122:
2116:
2114:
2113:Related fields
2110:
2109:
2106:
2105:
2103:
2102:
2097:
2092:
2087:
2081:
2079:
2075:
2074:
2072:
2071:
2066:
2061:
2056:
2051:
2046:
2044:Function model
2041:
2036:
2031:
2026:
2020:
2018:
2014:
2013:
2011:
2010:
2005:
2000:
1995:
1990:
1985:
1980:
1975:
1970:
1965:
1960:
1955:
1950:
1948:Executable UML
1945:
1940:
1934:
1932:
1925:
1921:
1920:
1918:
1917:
1912:
1907:
1902:
1897:
1892:
1886:
1884:
1880:
1879:
1877:
1876:
1871:
1870:
1869:
1859:
1854:
1849:
1844:
1839:
1834:
1829:
1824:
1819:
1814:
1809:
1804:
1799:
1794:
1789:
1788:
1787:
1782:
1777:
1772:
1767:
1757:
1752:
1746:
1744:
1740:
1739:
1737:
1736:
1731:
1726:
1721:
1716:
1711:
1706:
1701:
1696:
1691:
1689:Formal methods
1686:
1681:
1676:
1671:
1665:
1663:
1659:
1658:
1651:
1650:
1643:
1636:
1628:
1621:
1620:
1594:
1571:
1552:
1537:
1511:
1504:
1482:
1463:
1440:
1421:
1396:
1377:
1358:
1340:
1327:Jacobson, Ivar
1318:
1290:
1271:(4): 160–166.
1255:
1244:
1217:
1199:
1192:
1169:
1134:(2): 189–213.
1114:
1092:
1062:
1048:
1043:Winter, Robert
1026:
1003:
980:
947:
912:
867:
829:
802:(3): 275–315.
782:
757:
742:
724:
694:
679:
657:
633:
614:
596:
559:
557:
554:
553:
552:
538:
526:
514:
506:
505:External links
503:
502:
501:
496:
490:
485:
480:
475:
470:
465:
458:
455:
370:
367:
331:business risks
281:
278:
260:
257:
255:
252:
104:
101:
83:
80:
15:
9:
6:
4:
3:
2:
2217:
2216:
2205:
2202:
2200:
2197:
2195:
2192:
2191:
2189:
2174:
2166:
2164:
2156:
2155:
2152:
2146:
2143:
2141:
2138:
2136:
2133:
2131:
2128:
2126:
2123:
2121:
2118:
2117:
2115:
2111:
2101:
2098:
2096:
2093:
2091:
2088:
2086:
2083:
2082:
2080:
2076:
2070:
2067:
2065:
2064:Systems model
2062:
2060:
2057:
2055:
2052:
2050:
2047:
2045:
2042:
2040:
2037:
2035:
2032:
2030:
2027:
2025:
2022:
2021:
2019:
2015:
2009:
2006:
2004:
2001:
1999:
1996:
1994:
1991:
1989:
1986:
1984:
1981:
1979:
1976:
1974:
1971:
1969:
1966:
1964:
1961:
1959:
1956:
1954:
1951:
1949:
1946:
1944:
1941:
1939:
1936:
1935:
1933:
1931:Developmental
1929:
1926:
1922:
1916:
1913:
1911:
1908:
1906:
1903:
1901:
1898:
1896:
1893:
1891:
1888:
1887:
1885:
1881:
1875:
1872:
1868:
1865:
1864:
1863:
1860:
1858:
1855:
1853:
1850:
1848:
1845:
1843:
1840:
1838:
1835:
1833:
1830:
1828:
1825:
1823:
1820:
1818:
1815:
1813:
1810:
1808:
1805:
1803:
1800:
1798:
1795:
1793:
1792:Data modeling
1790:
1786:
1783:
1781:
1778:
1776:
1773:
1771:
1768:
1766:
1763:
1762:
1761:
1758:
1756:
1753:
1751:
1748:
1747:
1745:
1741:
1735:
1732:
1730:
1727:
1725:
1722:
1720:
1717:
1715:
1712:
1710:
1707:
1705:
1702:
1700:
1697:
1695:
1692:
1690:
1687:
1685:
1682:
1680:
1677:
1675:
1672:
1670:
1667:
1666:
1664:
1660:
1656:
1649:
1644:
1642:
1637:
1635:
1630:
1629:
1626:
1608:
1604:
1598:
1582:
1575:
1567:
1563:
1556:
1548:
1541:
1525:
1521:
1515:
1507:
1501:
1497:
1493:
1486:
1478:
1474:
1467:
1451:
1444:
1436:
1432:
1425:
1414:
1407:
1400:
1392:
1388:
1381:
1373:
1369:
1362:
1354:
1350:
1344:
1336:
1332:
1328:
1322:
1303:
1302:
1294:
1286:
1282:
1278:
1274:
1270:
1266:
1259:
1248:
1240:
1236:
1232:
1228:
1221:
1213:
1206:
1204:
1195:
1189:
1185:
1181:
1173:
1165:
1161:
1157:
1153:
1149:
1145:
1141:
1137:
1133:
1129:
1125:
1118:
1107:
1105:
1103:
1101:
1099:
1097:
1085:
1078:
1071:
1069:
1067:
1055:
1053:
1044:
1037:
1035:
1033:
1031:
1022:
1018:
1012:
1010:
1008:
999:
995:
991:
988:Bert Arnold;
984:
965:
958:
951:
943:
939:
935:
931:
927:
923:
916:
908:
904:
900:
896:
892:
888:
887:SIGMOD Record
881:
874:
872:
863:
859:
855:
851:
847:
843:
836:
834:
825:
821:
817:
813:
809:
805:
801:
797:
793:
786:
770:
764:
762:
753:
746:
738:
734:
728:
712:
708:
704:
698:
690:
683:
667:
661:
650:
643:
637:
629:
625:
618:
610:
606:
600:
584:
580:
573:
567:
565:
560:
551:at Wiktionary
550:
549:
543:
539:
536:
531:
527:
524:
519:
515:
512:
509:
508:
500:
497:
494:
491:
489:
486:
484:
481:
479:
476:
474:
471:
469:
466:
464:
461:
460:
454:
452:
448:
444:
440:
435:
432:
428:
424:
420:
416:
412:
408:
404:
403:risk analysis
400:
396:
392:
388:
384:
380:
376:
366:
364:
363:Stanley Gaver
360:
356:
352:
348:
344:
343:Ivar Jacobson
340:
335:
332:
328:
324:
320:
316:
311:
306:
304:
300:
299:deliverabless
296:
292:
288:
277:
274:
270:
265:
251:
249:
246:
240:
238:
234:
230:
226:
222:
218:
213:
209:
205:
201:
196:
194:
190:
186:
182:
178:
177:
172:
168:
163:
161:
157:
153:
149:
146:Paramount to
144:
142:
138:
134:
129:
124:
122:
118:
114:
110:
100:
96:
94:
90:
79:
77:
73:
69:
65:
61:
60:Volkswagen AG
57:
53:
49:
45:
40:
38:
33:
29:
25:
21:
2059:Object model
2054:Metamodeling
1983:Spiral model
1883:Orientations
1796:
1611:. Retrieved
1597:
1585:. Retrieved
1574:
1566:the original
1555:
1540:
1530:December 18,
1528:. Retrieved
1524:the original
1514:
1495:
1485:
1477:the original
1466:
1454:. Retrieved
1443:
1435:the original
1424:
1413:the original
1399:
1391:the original
1380:
1372:the original
1361:
1353:the original
1343:
1335:the original
1321:
1309:. Retrieved
1300:
1293:
1268:
1264:
1258:
1247:
1230:
1226:
1220:
1172:
1131:
1127:
1117:
1084:the original
997:
983:
973:November 29,
971:. Retrieved
964:the original
950:
928:(6): 37–43.
925:
921:
915:
893:(4): 40–43.
890:
886:
845:
841:
799:
795:
785:
773:. Retrieved
751:
745:
737:the original
727:
715:. Retrieved
711:the original
706:
697:
688:
682:
670:. Retrieved
660:
649:the original
636:
627:
617:
605:"EA-Success"
599:
587:. Retrieved
582:
578:
547:
537:at Wikiquote
493:John Zachman
436:
372:
336:
307:
283:
266:
262:
241:
203:
200:John Zachman
197:
174:
170:
164:
147:
145:
128:architecture
127:
125:
117:organization
108:
106:
97:
85:
82:Introduction
72:productivity
41:
23:
19:
18:
1750:Abstraction
287:integration
248:methodology
189:data stores
103:Definitions
2188:Categories
2069:View model
2034:Data model
717:October 3,
556:References
387:management
379:management
355:IDS Scheer
323:responsive
237:procedures
185:data flows
109:enterprise
32:enterprise
2078:Languages
1285:226351029
1156:1751-7575
994:Jan Dietz
942:206469705
824:230545944
816:0268-3962
668:. Gartner
513:(archive)
229:standards
221:customers
126:The term
107:The term
2173:Category
2039:ER model
1905:Ontology
1817:Software
1743:Concepts
1613:March 4,
1609:. Cutter
1587:March 4,
1494:(2003).
1456:March 4,
1311:March 4,
1164:28199240
907:23939840
862:12191060
775:March 4,
672:July 29,
609:Archived
589:March 4,
457:See also
254:Overview
233:policies
202:'s 1987
148:changing
2163:Commons
1988:V-model
1452:. ZDNet
1136:Bibcode
347:Gartner
152:sponsor
1924:Models
1674:DevOps
1662:Fields
1502:
1283:
1190:
1162:
1154:
940:
905:
860:
822:
814:
425:, and
361:, and
235:, and
223:, and
156:vision
62:, and
2100:SysML
2024:SPICE
2017:Other
1978:Scrum
1938:Agile
1890:Agile
1874:CI/CD
1416:(PDF)
1409:(PDF)
1305:(PDF)
1281:S2CID
1160:S2CID
1087:(PDF)
1080:(PDF)
967:(PDF)
960:(PDF)
938:S2CID
903:S2CID
883:(PDF)
858:S2CID
820:S2CID
652:(PDF)
645:(PDF)
575:(PDF)
176:views
56:Intel
2085:IDEF
2029:CMMI
1915:SDLC
1615:2023
1589:2023
1532:2014
1500:ISBN
1458:2023
1313:2023
1188:ISBN
1152:ISSN
975:2014
812:ISSN
777:2023
719:2014
674:2013
591:2023
393:and
385:and
377:and
353:and
321:and
319:open
187:and
70:and
42:The
28:data
2095:USL
2090:UML
1968:RAD
1943:EUP
1273:doi
1235:doi
1180:doi
1144:doi
930:doi
895:doi
850:doi
804:doi
250:."
2190::
1998:XP
1973:UP
1279:.
1269:48
1267:.
1231:80
1229:.
1202:^
1186:.
1158:.
1150:.
1142:.
1130:.
1126:.
1095:^
1065:^
1051:^
1029:^
1019:.
1006:^
992:;
936:.
926:14
924:.
901:.
891:18
889:.
885:.
870:^
856:.
846:38
844:.
832:^
818:.
810:.
800:36
798:.
794:.
760:^
705:.
626:.
581:.
577:.
563:^
421:,
417:,
413:,
409:,
405:,
397:,
391:IT
389:,
381:,
357:,
349:,
345:,
273:IS
269:IT
231:,
219:,
191:,
115:,
58:,
54:,
24:EA
1647:e
1640:t
1633:v
1617:.
1591:.
1534:.
1508:.
1460:.
1315:.
1287:.
1275::
1241:.
1237::
1196:.
1182::
1166:.
1146::
1138::
1132:6
977:.
944:.
932::
909:.
897::
864:.
852::
826:.
806::
779:.
721:.
676:.
630:.
593:.
583:9
271:/
22:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.